From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Chu Guangqing <chuguangqing@inspur.com>,
alain.volmat@foss.st.com, maarten.lankhorst@linux.intel.com,
mripard@kernel.org, tzimmermann@suse.de, airlied@gmail.com,
simona@ffwll.ch
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] drm/sti: call drm_edid_connector_update when edit is NULL
Date: Sat, 18 Oct 2025 14:25:43 +0200 [thread overview]
Message-ID: <e303c2f5-0868-445b-ab1f-dbb81dd173d9@gmail.com> (raw)
In-Reply-To: <20251014065406.4017-1-chuguangqing@inspur.com>
Hi,
Thanks for this patch.
Please change the commit subject to "drm/sti: hdmi: xxx".
Le 14/10/2025 à 08:54, Chu Guangqing a écrit :
> call drm_edid_connector_update to reset the information when edit is NULL.
> We can see the following comments in drm_edid.c
> If EDID is NULL, reset the information.
>
> Signed-off-by: Chu Guangqing <chuguangqing@inspur.com>
> ---
> drivers/gpu/drm/sti/sti_hdmi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/sti/sti_hdmi.c b/drivers/gpu/drm/sti/sti_hdmi.c
> index 4e7c3d78b2b9..31a72f7f4d43 100644
> --- a/drivers/gpu/drm/sti/sti_hdmi.c
> +++ b/drivers/gpu/drm/sti/sti_hdmi.c
> @@ -1008,6 +1008,7 @@ static int sti_hdmi_connector_get_modes(struct drm_connector *connector)
> return count;
>
> fail:
> + drm_edid_connector_update(connector, NULL);
> DRM_ERROR("Can't read HDMI EDID\n");
Now that empty EDID has been properly updated, the DRM_ERROR can be
removed IMO. In our use case HDMI is not systematically plugged, so
this ERROR is quite noisy when we do not expect it.
Best regards,
Raphaël> return 0;
> }
prev parent reply other threads:[~2025-10-18 12:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 6:54 Chu Guangqing
2025-10-18 12:25 ` Raphaël Gallais-Pou [this message]
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=e303c2f5-0868-445b-ab1f-dbb81dd173d9@gmail.com \
--to=rgallaispou@gmail.com \
--cc=airlied@gmail.com \
--cc=alain.volmat@foss.st.com \
--cc=chuguangqing@inspur.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--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®