Hi,
On Thu, Feb 10, 2022 at 3:58 AM Sankeerth Billakanti quic_sbillaka@quicinc.com wrote:
Add support in the DP driver to utilize the custom eDP panels from drm/panels.
An eDP panel is always connected to the platform. So, the eDP connector can be reported as always connected. The display mode will be sourced from the panel. The panel mode will be set after the link training is completed.
Signed-off-by: Sankeerth Billakanti quic_sbillaka@quicinc.com
Changes in v4:
- Remove obvious comments
- Define separate connector_ops for eDP
- Remove unnecessary checks
Changes in v3: None
drivers/gpu/drm/msm/dp/dp_display.c | 6 ++++ drivers/gpu/drm/msm/dp/dp_drm.c | 62 +++++++++++++++++++++++++++++++------ drivers/gpu/drm/msm/dp/dp_parser.h | 3 ++ 3 files changed, 61 insertions(+), 10 deletions(-)
diff --git a/drivers/gpu/drm/msm/dp/dp_display.c b/drivers/gpu/drm/msm/dp/dp_display.c index 7cc4d21..5d314e6 100644 --- a/drivers/gpu/drm/msm/dp/dp_display.c +++ b/drivers/gpu/drm/msm/dp/dp_display.c @@ -1513,6 +1513,9 @@ int msm_dp_display_enable(struct msm_dp *dp, struct drm_encoder *encoder) return -EINVAL; }
if (dp->connector_type == DRM_MODE_CONNECTOR_eDP)dp_hpd_plug_handle(dp_display, 0);
I'm really not so sure here. You're just totally ignoring the HPD signal here which isn't right at all. The HPD signal is important for knowing if an edp panel is ready yet so you can't just ignore it. The only way this could work is if something else turns the panel on w/ plenty of time before your code runs so it has had time to get ready...
It feels like we just need to work to get this all plumbed up properly with the right power sequencing. That'll also allow us to enable the generic edp-panel stuff...
+static int edp_connector_get_modes(struct drm_connector *connector) +{
struct msm_dp *dp;dp = to_dp_connector(connector)->dp_display;return drm_bridge_get_modes(dp->panel_bridge, connector);+}
+static enum drm_mode_status edp_connector_mode_valid(
struct drm_connector *connector,struct drm_display_mode *mode)+{
if (mode->clock > EDP_MAX_PIXEL_CLK_KHZ)return MODE_CLOCK_HIGH;return MODE_OK;+}
static const struct drm_connector_funcs dp_connector_funcs = { .detect = dp_connector_detect, .fill_modes = drm_helper_probe_single_connector_modes, @@ -132,11 +151,24 @@ static const struct drm_connector_funcs dp_connector_funcs = { .atomic_destroy_state = drm_atomic_helper_connector_destroy_state, };
+static const struct drm_connector_funcs edp_connector_funcs = {
.fill_modes = drm_helper_probe_single_connector_modes,.destroy = drm_connector_cleanup,.reset = drm_atomic_helper_connector_reset,.atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state,.atomic_destroy_state = drm_atomic_helper_connector_destroy_state,+};
static const struct drm_connector_helper_funcs dp_connector_helper_funcs = { .get_modes = dp_connector_get_modes, .mode_valid = dp_connector_mode_valid, };
+static const struct drm_connector_helper_funcs edp_connector_helper_funcs = {
.get_modes = edp_connector_get_modes,.mode_valid = edp_connector_mode_valid,+};
/* connector initialization */ struct drm_connector *dp_drm_connector_init(struct msm_dp *dp_display) { @@ -154,18 +186,28 @@ struct drm_connector *dp_drm_connector_init(struct msm_dp *dp_display)
connector = &dp_connector->base;
ret = drm_connector_init(dp_display->drm_dev, connector,&dp_connector_funcs,dp_display->connector_type);if (ret)return ERR_PTR(ret);
if (dp_display->connector_type == DRM_MODE_CONNECTOR_eDP) {ret = drm_connector_init(dp_display->drm_dev, connector,&edp_connector_funcs, DRM_MODE_CONNECTOR_eDP);if (ret)return ERR_PTR(ret);drm_connector_helper_add(connector,&edp_connector_helper_funcs);} else {ret = drm_connector_init(dp_display->drm_dev, connector,&dp_connector_funcs,DRM_MODE_CONNECTOR_DisplayPort);if (ret)return ERR_PTR(ret);
drm_connector_helper_add(connector, &dp_connector_helper_funcs);
drm_connector_helper_add(connector, &dp_connector_helper_funcs);
This is probably not the correct way to do this. Drivers like this should really be moving _away_ from creating their own connectors. The idea is that you should just be creating bridges and then someone creates a "bridge connector" that implements the connector functions atop the bridge.
This is what Dmitry is working on [1]. Speaking of which, he really ought to be CCed on all your patches.
/** Enable HPD to let hpd event is handled when cable is connected.*/connector->polled = DRM_CONNECTOR_POLL_HPD;
/** Enable HPD to let hpd event is handled when cable is connected.*/connector->polled = DRM_CONNECTOR_POLL_HPD;} drm_connector_attach_encoder(connector, dp_display->encoder);diff --git a/drivers/gpu/drm/msm/dp/dp_parser.h b/drivers/gpu/drm/msm/dp/dp_parser.h index 3172da0..58c4f27 100644 --- a/drivers/gpu/drm/msm/dp/dp_parser.h +++ b/drivers/gpu/drm/msm/dp/dp_parser.h @@ -17,6 +17,9 @@ #define DP_MAX_PIXEL_CLK_KHZ 675000 #define DP_MAX_NUM_DP_LANES 4
+/* Maximum validated clock */ +#define EDP_MAX_PIXEL_CLK_KHZ 285550
As discussed out-of-band, this isn't my favorite define. The datasheet for sc7280, which is what you're testing on / targeting, claims to support higher rates. Other users of this driver also ought to support higher rates. It might be OK short term, but it's definitely not a good long term solution.
[1] https://lore.kernel.org/all/20220211224006.1797846-5-dmitry.baryshkov@linaro...