From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: <jani.nikula@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
<freedreno@lists.freedesktop.org>, <andersson@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
<linux-kernel@vger.kernel.org>,
"Maxime Ripard" <mripard@kernel.org>, <quic_parellan@quicinc.com>,
<dri-devel@lists.freedesktop.org>,
Daniel Vetter <daniel@ffwll.ch>, <quic_jesszhan@quicinc.com>,
David Airlie <airlied@gmail.com>
Subject: Re: [Freedreno] [PATCH] drm: improve the documentation of connector hpd ops
Date: Mon, 4 Dec 2023 09:45:19 -0800 [thread overview]
Message-ID: <4a2d6fb2-e3b5-dd5d-7a66-d514e091eb41@quicinc.com> (raw)
In-Reply-To: <CAA8EJpoykwsMWX+msDAB3TZaBmwE4iA4fiDiA-iOELmWd50s-w@mail.gmail.com>
On 12/3/2023 10:14 AM, Dmitry Baryshkov wrote:
> On Sun, 3 Dec 2023 at 16:24, Laurent Pinchart
> <laurent.pinchart@ideasonboard.com> wrote:
>>
>> Hi Abhinav,
>>
>> Thank you for the patch (and thank to Dmitry for pinging me on IRC, this
>> patch got burried in my inbox).
>>
>> On Wed, Sep 20, 2023 at 01:13:58PM -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.
>>
>> s/attempt to //
>
> I can probably fix this while applying the patch.
>
Thank you Laurent and Dmitry.
>>
>>>
>>> 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.
>>>
>>> [1]: https://patchwork.freedesktop.org/patch/558387/
>>>
>>
>> You could add a
>>
>> Suggested-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>
>>> Signed-off-by: Abhinav Kumar <quic_abhinavk@quicinc.com>
>>
>> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
>>
>>> ---
>>> include/drm/drm_modeset_helper_vtables.h | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/include/drm/drm_modeset_helper_vtables.h b/include/drm/drm_modeset_helper_vtables.h
>>> index e3c3ac615909..a33cf7488737 100644
>>> --- a/include/drm/drm_modeset_helper_vtables.h
>>> +++ b/include/drm/drm_modeset_helper_vtables.h
>>> @@ -1154,6 +1154,11 @@ struct drm_connector_helper_funcs {
>>> * This operation is optional.
>>> *
>>> * This callback is used by the drm_kms_helper_poll_enable() helpers.
>>> + *
>>> + * This operation does not need to perform any hpd state tracking as
>>> + * the DRM core handles that maintenance and ensures the calls to enable
>>> + * and disable hpd are balanced.
>>> + *
>>> */
>>> void (*enable_hpd)(struct drm_connector *connector);
>>>
>>> @@ -1165,6 +1170,11 @@ struct drm_connector_helper_funcs {
>>> * This operation is optional.
>>> *
>>> * This callback is used by the drm_kms_helper_poll_disable() helpers.
>>> + *
>>> + * This operation does not need to perform any hpd state tracking as
>>> + * the DRM core handles that maintenance and ensures the calls to enable
>>> + * and disable hpd are balanced.
>>> + *
>>> */
>>> void (*disable_hpd)(struct drm_connector *connector);
>>> };
>>
>> --
>> Regards,
>>
>> Laurent Pinchart
>
>
>
next prev parent reply other threads:[~2023-12-04 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 20:13 Abhinav Kumar
2023-12-03 14:24 ` Laurent Pinchart
2023-12-03 18:14 ` [Freedreno] " Dmitry Baryshkov
2023-12-04 17:45 ` Abhinav Kumar [this message]
2023-12-04 14:16 ` Dmitry Baryshkov
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=4a2d6fb2-e3b5-dd5d-7a66-d514e091eb41@quicinc.com \
--to=quic_abhinavk@quicinc.com \
--cc=airlied@gmail.com \
--cc=andersson@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=quic_jesszhan@quicinc.com \
--cc=quic_parellan@quicinc.com \
--cc=tzimmermann@suse.de \
/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®