public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
To: Jani Nikula <jani.nikula@linux.intel.com>
Cc: 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, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] drm/sti: hdmi: call drm_edid_connector_update when edid is NULL
Date: Fri, 24 Oct 2025 00:51:57 +0200	[thread overview]
Message-ID: <aPqxjUh91I4G4bOm@thinkstation> (raw)
In-Reply-To: <4cf3050675a7090a87c80d525601b226e5e70f06@intel.com>

Le Tue, Oct 21, 2025 at 11:55:01AM +0300, Jani Nikula a écrit :
> On Mon, 20 Oct 2025, Chu Guangqing <chuguangqing@inspur.com> wrote:
> > call drm_edid_connector_update to reset the information when edid 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 | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/sti/sti_hdmi.c b/drivers/gpu/drm/sti/sti_hdmi.c
> > index 4e7c3d78b2b9..e0be1be8bcdd 100644
> > --- a/drivers/gpu/drm/sti/sti_hdmi.c
> > +++ b/drivers/gpu/drm/sti/sti_hdmi.c
> > @@ -1008,7 +1008,7 @@ static int sti_hdmi_connector_get_modes(struct drm_connector *connector)
> >  	return count;
> >  
> >  fail:
> > -	DRM_ERROR("Can't read HDMI EDID\n");
> > +	drm_edid_connector_update(connector, NULL);
> 
> The context above has:
> 
> 	drm_edid = drm_edid_read(connector);
> 
> 	drm_edid_connector_update(connector, drm_edid);
> 
> 	cec_notifier_set_phys_addr(hdmi->notifier,
> 				   connector->display_info.source_physical_address);
> 
> 	if (!drm_edid)
> 		goto fail;
> 
> i.e. drm_edid_connector_update() already gets called regardless of
> whether drm_edid is NULL or not. Precisely as intended in commit
> f7945d9fa8b7 ("drm/sti/sti_hdmi: convert to struct drm_edid").

Woops indeed you are right.  Looks like I was distracted during the
review.

Sorry but looking at it again this patch has no mean to be.  Regarding
the noisy message, I'll send one removing it, but it is not pressing
IMHO.  It only appears if the driver probe with connector plugged.

Thanks for your reply Jani,

Best regards,
Raphaël
> 
> 
> BR,
> Jani.
> 
> 
> >  	return 0;
> >  }
> 
> -- 
> Jani Nikula, Intel

      reply	other threads:[~2025-10-23 22:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20  1:30 [PATCH v2 0/1] drm/sti: hdmi: call drm_edid_connector_update when edid is NULL Chu Guangqing
2025-10-20  1:30 ` [PATCH v2 1/1] " Chu Guangqing
2025-10-20 14:21   ` Raphaël Gallais-Pou
2025-10-21  8:55   ` Jani Nikula
2025-10-23 22:51     ` 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=aPqxjUh91I4G4bOm@thinkstation \
    --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=jani.nikula@linux.intel.com \
    --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