[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <170169936702.76859.18234919578150833329.b4-ty@linaro.org>
Date: Mon, 4 Dec 2023 16:16:32 +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: improve the documentation of connector hpd ops
On Wed, 20 Sep 2023 13:13:58 -0700, Abhinav Kumar wrote:
> While making the changes in [1], it was noted that the documentation
> of the enable_hpd() and disable_hpd() does not make it clear that
> these ops should not try to do hpd state maintenance and should only
> attempt to enable/disable hpd related hardware for the connector.
>
> The state management of these calls to make sure these calls are
> balanced is handled by the DRM core and we should keep it that way
> to minimize the overhead in the drivers which implement these ops.
>
> [...]
Applied to drm-misc-next, thanks!
[1/1] drm: improve the documentation of connector hpd ops
commit: a5b2dcb96d6acb286459612a142371b0d74543bf
Best regards,
--
Dmitry Baryshkov <dmitry.baryshkov@...aro.org>
Powered by blists - more mailing lists