From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Maxime Ripard <mripard@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
kernel@collabora.com, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/display: hdmi: Do not read EDID on disconnected connectors
Date: Mon, 13 Jan 2025 14:13:10 +0200 [thread overview]
Message-ID: <78046727-0d2a-4ada-b75c-ec2e80e1f560@collabora.com> (raw)
In-Reply-To: <CAA8EJpqzGZx0PdPKZMEwf3iv9pfb+Cr6Mrjt+p21rUwN-RiNvQ@mail.gmail.com>
On 1/13/25 2:06 PM, Dmitry Baryshkov wrote:
> On Mon, 13 Jan 2025 at 14:00, Cristian Ciocaltea
> <cristian.ciocaltea@collabora.com> wrote:
>>
>> Hi Maxime,
>>
>> On 1/13/25 11:35 AM, Maxime Ripard wrote:
>>> On Sat, Jan 11, 2025 at 12:04:09AM +0200, Cristian Ciocaltea wrote:
>>>> The recently introduced hotplug event handler in the HDMI Connector
>>>> framework attempts to unconditionally read the EDID data, leading to a
>>>> bunch of non-harmful, yet quite annoying DDC/I2C related errors being
>>>> reported.
>>>>
>>>> Ensure the operation is performed only for connectors having the status
>>>> connected or unknown.
>>>>
>>>> Fixes: ab716b74dc9d ("drm/display/hdmi: implement hotplug functions")
>>>> Signed-off-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
>>>> ---
>>>> drivers/gpu/drm/display/drm_hdmi_state_helper.c | 2 ++
>>>> 1 file changed, 2 insertions(+)
>>>>
>>>> diff --git a/drivers/gpu/drm/display/drm_hdmi_state_helper.c b/drivers/gpu/drm/display/drm_hdmi_state_helper.c
>>>> index 2691e8b3e480131ac6e4e4b74b24947be55694bd..8e4b30e09b53b84cfd36199d56db3221a00085b0 100644
>>>> --- a/drivers/gpu/drm/display/drm_hdmi_state_helper.c
>>>> +++ b/drivers/gpu/drm/display/drm_hdmi_state_helper.c
>>>> @@ -786,8 +786,10 @@ drm_atomic_helper_connector_hdmi_update(struct drm_connector *connector,
>>>> const struct drm_edid *drm_edid;
>>>>
>>>> if (status == connector_status_disconnected) {
>>>> + drm_edid_connector_update(connector, NULL);
>>>
>>> Why is this needed? It's not mentionned in your commit log.
>>
>> The original implementation has it after reading the EDID, but I'm not
>> sure if we need the explicit reset in this case.
>>
>> I was going to submit a new revision switching the order, as Dmitry
>> suggested, or should we simply drop it?
>
> If the EDID is not available, it needs to be reset.
Thanks for the confirmation - I will mention this in the commit description.
Regards,
Cristian
prev parent reply other threads:[~2025-01-13 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 22:04 Cristian Ciocaltea
2025-01-13 9:16 ` Dmitry Baryshkov
2025-01-13 11:39 ` Cristian Ciocaltea
2025-01-13 9:35 ` Maxime Ripard
2025-01-13 12:00 ` Cristian Ciocaltea
2025-01-13 12:06 ` Dmitry Baryshkov
2025-01-13 12:13 ` Cristian Ciocaltea [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=78046727-0d2a-4ada-b75c-ec2e80e1f560@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=airlied@gmail.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kernel@collabora.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
all inboxes | Powered by JetHome®