[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <170169936702.76859.2850036545937110756.b4-ty@linaro.org>
Date: Mon, 4 Dec 2023 16:16:33 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
To: dri-devel@...ts.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@...ux.intel.com>,
Maxime Ripard <mripard@...nel.org>,
Thomas Zimmermann <tzimmermann@...e.de>,
David Airlie <airlied@...il.com>,
Daniel Vetter <daniel@...ll.ch>,
Abhinav Kumar <quic_abhinavk@...cinc.com>
Cc: freedreno@...ts.freedesktop.org, quic_jesszhan@...cinc.com,
quic_parellan@...cinc.com, laurent.pinchart@...asonboard.com,
andersson@...nel.org, jani.nikula@...ux.intel.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] drm: remove drm_bridge_hpd_disable() from drm_bridge_connector_destroy()
On Tue, 19 Sep 2023 10:48:12 -0700, Abhinav Kumar wrote:
> drm_bridge_hpd_enable()/drm_bridge_hpd_disable() callbacks call into
> the respective driver's hpd_enable()/hpd_disable() ops. These ops control
> the HPD enable/disable logic which in some cases like MSM can be a
> dedicate hardware block to control the HPD.
>
> During probe_defer cases, a connector can be initialized and then later
> destroyed till the probe is retried. During connector destroy in these
> cases, the hpd_disable() callback gets called without a corresponding
> hpd_enable() leading to an unbalanced state potentially causing even
> a crash.
>
> [...]
Applied to drm-misc-next, thanks!
[1/1] drm: remove drm_bridge_hpd_disable() from drm_bridge_connector_destroy()
commit: f730e7adfd69d7ac859d8fe4d67e980cbad1e445
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Powered by blists - more mailing lists