From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
To: Harikrishna Shenoy <h-shenoy@ti.com>
Cc: jonas@kwiboo.se, jernej.skrabec@gmail.com,
maarten.lankhorst@linux.intel.com, tzimmermann@suse.de,
airlied@gmail.com, simona@ffwll.ch, lyude@redhat.com,
luca.ceresoli@bootlin.com, viro@zeniv.linux.org.uk,
andy.yan@rock-chips.com, linux@treblig.org, javierm@redhat.com,
linux-kernel@vger.kernel.org, devarsht@ti.com,
j-choudhary@ti.com, u-kumar1@ti.com, s-jain1@ti.com,
andrzej.hajda@intel.com, neil.armstrong@linaro.org,
rfoss@kernel.org, Laurent.pinchart@ideasonboard.com,
mripard@kernel.org, lumag@kernel.org, dianders@chromium.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v5 3/6] drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable()
Date: Mon, 1 Sep 2025 13:05:02 +0300 [thread overview]
Message-ID: <6fa1a8d5-149e-437d-aef0-587c49957197@ideasonboard.com> (raw)
In-Reply-To: <20250811075904.1613519-4-h-shenoy@ti.com>
Hi,
On 11/08/2025 10:59, Harikrishna Shenoy wrote:
> From: Jayesh Choudhary <j-choudhary@ti.com>
>
> In case if we get errors in cdns_mhdp_link_up() or cdns_mhdp_reg_read()
> in atomic_enable, we will go to cdns_mhdp_modeset_retry_fn() and will hit
> NULL pointer while trying to access the mutex. We need the connector to
> be set before that. Unlike in legacy !(DBANC) cases, we do not have
> connector initialised in bridge_attach(). So set the mhdp->connector
> in atomic_enable() earlier to avoid possible NULL pointer.
>
> Fixes: c932ced6b585 ("drm/tidss: Update encoder/bridge chain connect model")
> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
> ---
> .../drm/bridge/cadence/cdns-mhdp8546-core.c | 20 +++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c b/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c
> index c2ce3d6e5a88..b2f5a48cac2d 100644
> --- a/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c
> +++ b/drivers/gpu/drm/bridge/cadence/cdns-mhdp8546-core.c
> @@ -1759,12 +1759,21 @@ static void cdns_mhdp_atomic_enable(struct drm_bridge *bridge,
> struct drm_bridge_state *new_state;
> const struct drm_display_mode *mode;
> u32 resp;
> - int ret;
> + int ret = 0;
>
> dev_dbg(mhdp->dev, "bridge enable\n");
>
> mutex_lock(&mhdp->link_mutex);
>
> + mhdp->connector = drm_atomic_get_new_connector_for_encoder(state,
> + bridge->encoder);
> + if (WARN_ON(!mhdp->connector))
> + goto out;
> +
> + conn_state = drm_atomic_get_new_connector_state(state, mhdp->connector);
> + if (WARN_ON(!conn_state))
> + goto out;
You are just moving code here, but... Shouldn't these be errors? If I
read this right, ret is 0 here, and thus if we hit either of those
issues above, we'll return 0.
Tomi
> +
> if (mhdp->plugged && !mhdp->link_up) {
> ret = cdns_mhdp_link_up(mhdp);
> if (ret < 0)
> @@ -1784,15 +1793,6 @@ static void cdns_mhdp_atomic_enable(struct drm_bridge *bridge,
> cdns_mhdp_reg_write(mhdp, CDNS_DPTX_CAR,
> resp | CDNS_VIF_CLK_EN | CDNS_VIF_CLK_RSTN);
>
> - mhdp->connector = drm_atomic_get_new_connector_for_encoder(state,
> - bridge->encoder);
> - if (WARN_ON(!mhdp->connector))
> - goto out;
> -
> - conn_state = drm_atomic_get_new_connector_state(state, mhdp->connector);
> - if (WARN_ON(!conn_state))
> - goto out;
> -
> if (mhdp->hdcp_supported &&
> mhdp->hw_state == MHDP_HW_READY &&
> conn_state->content_protection ==
next prev parent reply other threads:[~2025-09-01 10:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 7:58 [PATCH v5 0/6] MHDP8546 fixes related to DBANC usecase Harikrishna Shenoy
2025-08-11 7:58 ` [PATCH v5 1/6] drm/bridge: cadence: cdns-mhdp8546-core: Remove legacy support for connector initialisation in bridge Harikrishna Shenoy
2025-09-01 9:52 ` Tomi Valkeinen
2025-09-02 8:28 ` Harikrishna Shenoy
2025-08-11 7:59 ` [PATCH v5 2/6] drm/bridge: cadence: cdns-mhdp8546*: Change drm_connector from structure to pointer Harikrishna Shenoy
2025-09-01 10:00 ` Tomi Valkeinen
2025-09-02 8:32 ` Harikrishna Shenoy
2025-08-11 7:59 ` [PATCH v5 3/6] drm/bridge: cadence: cdns-mhdp8546-core: Set the mhdp connector earlier in atomic_enable() Harikrishna Shenoy
2025-09-01 10:05 ` Tomi Valkeinen [this message]
2025-09-02 9:27 ` Harikrishna Shenoy
2025-08-11 7:59 ` [PATCH v5 4/6] drm/bridge: cadence: cdns-mhdp8546-core: Add mode_valid hook to drm_bridge_funcs Harikrishna Shenoy
2025-09-01 10:07 ` Tomi Valkeinen
2025-08-11 7:59 ` [PATCH v5 5/6] drm/bridge: cadence: cdns-mhdp8546-core: Reduce log level for DPCD read/write Harikrishna Shenoy
2025-09-01 10:08 ` Tomi Valkeinen
2025-08-11 7:59 ` [PATCH v5 6/6] drm/bridge: cadence: cdns-mhdp8546-core: Handle HDCP state in bridge atomic check Harikrishna Shenoy
2025-09-01 10:18 ` Tomi Valkeinen
2025-09-02 11:34 ` Harikrishna Shenoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fa1a8d5-149e-437d-aef0-587c49957197@ideasonboard.com \
--to=tomi.valkeinen@ideasonboard.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=andy.yan@rock-chips.com \
--cc=devarsht@ti.com \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=h-shenoy@ti.com \
--cc=j-choudhary@ti.com \
--cc=javierm@redhat.com \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=luca.ceresoli@bootlin.com \
--cc=lumag@kernel.org \
--cc=lyude@redhat.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=s-jain1@ti.com \
--cc=simona@ffwll.ch \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.com \
--cc=viro@zeniv.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®