From: Claudio Suarez <cssk@net-c.es>
To: Harry Wentland <harry.wentland@amd.com>
Cc: amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/3] drm/amdgpu replace drm_detect_hdmi_monitor() with drm_display_info.is_hdmi
Date: Mon, 18 Oct 2021 17:16:32 +0200 [thread overview]
Message-ID: <YW2P0EvHDAxXJbFO@gineta.localdomain> (raw)
In-Reply-To: <4217d1f5-e189-e3a5-547a-9ae205c3d539@amd.com>
On Mon, Oct 18, 2021 at 09:37:13AM -0400, Harry Wentland wrote:
> On 2021-10-17 07:34, Claudio Suarez wrote:
> >
> > From the TODO list Documentation/gpu/todo.rst
> > -----------------------
> > Once EDID is parsed, the monitor HDMI support information is available through
> > drm_display_info.is_hdmi. Many drivers still call drm_detect_hdmi_monitor() to
> > retrieve the same information, which is less efficient.
> >
> > Audit each individual driver calling drm_detect_hdmi_monitor() and switch to
> > drm_display_info.is_hdmi if applicable.
> > -----------------------
> > The task is divided in three small patches. The last patch depends on the
> > first one.
> >
>
> Thanks.
>
> This series is
> Reviewed-by: Harry Wentland <harry.wentland@amd.com>
>
> Harry
>
Thanks a lot for your comments and your review, Harry!
BR
Claudio Suarez.
next prev parent reply other threads:[~2021-10-18 15:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 11:34 [PATCH 0/3] drm/amdgpu replace drm_detect_hdmi_monitor() with drm_display_info.is_hdmi Claudio Suarez
2021-10-17 11:34 ` [PATCH 1/3] drm/amdgpu: update drm_display_info correctly when the edid is read Claudio Suarez
2021-10-17 11:34 ` [PATCH 2/3] drm/amdgpu: use drm_edid_get_monitor_name() instead of duplicating the code Claudio Suarez
2021-10-17 11:35 ` [PATCH 3/3] drm/amdgpu: replace drm_detect_hdmi_monitor() with drm_display_info.is_hdmi Claudio Suarez
2021-10-18 13:37 ` [PATCH 0/3] drm/amdgpu " Harry Wentland
2021-10-18 15:16 ` Claudio Suarez [this message]
2021-12-04 11:09 ` Claudio Suarez
2021-12-06 22:15 ` Alex Deucher
2021-12-06 23:13 ` Claudio Suarez
2021-12-07 13:45 ` Claudio Suarez
2021-12-07 17:47 ` Alex Deucher
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=YW2P0EvHDAxXJbFO@gineta.localdomain \
--to=cssk@net-c.es \
--cc=amd-gfx@lists.freedesktop.org \
--cc=harry.wentland@amd.com \
/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