From: Jani Nikula <jani.nikula@linux.intel.com>
To: feijuan.li@samsung.com,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"maarten.lankhorst@linux.intel.com"
<maarten.lankhorst@linux.intel.com>,
"mripard@kernel.org" <mripard@kernel.org>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"airlied@gmail.com" <airlied@gmail.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: 唐红飞 <hongfei.tang@samsung.com>, 严明贵 <minggui.yan@samsung.com>
Subject: Re: [PATCH] drm/edid: fixed the bug that hdr metadata was not cleared
Date: Thu, 17 Apr 2025 11:17:23 +0300 [thread overview]
Message-ID: <87cydbp5gs.fsf@intel.com> (raw)
In-Reply-To: <20250416093607epcms5p344bcffd7430fe5e30ef9b73db73f7388@epcms5p3>
On Wed, 16 Apr 2025, 李飞娟 <feijuan.li@samsung.com> wrote:
> From a34a1e2dd7aacd45f18775564fce12b03ae4009c Mon Sep 17 00:00:00 2001
> From: "feijuan.li" <feijuan.li@samsung.com>
> Date: Wed, 16 Apr 2025 11:07:39 +0000
> Subject: [PATCH] drm/edid: fixed the bug that hdr metadata was not cleared
>
> When DP connected to a device with HDR capability,
> the hdr structure was filled.Then connected to another
> sink device without hdr capability, but the hdr info
> still exist.
>
> Signed-off-by: feijuan.li <feijuan.li@samsung.com>
> ---
> drivers/gpu/drm/drm_edid.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index 13bc4c290b17..5cf5d30321b6 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -5607,6 +5607,7 @@ static void clear_eld(struct drm_connector *connector)
> {
> mutex_lock(&connector->eld_mutex);
> memset(connector->eld, 0, sizeof(connector->eld));
> + memset(&connector->hdr_sink_metadata, 0, sizeof(connector->hdr_sink_metadata));
hdr_sink_metadata is not related to ELD, and should not be cleared
within clear_eld().
I think this should be cleared in drm_reset_display_info(), and
long-term fields like this should be moved within display info.
BR,
Jani.
> mutex_unlock(&connector->eld_mutex);
>
> connector->latency_present[0] = false;
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-04-17 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250416093607epcms5p344bcffd7430fe5e30ef9b73db73f7388@epcms5p3>
2025-04-16 9:36 ` [PATCH] drm/edid: fixed the bug that hdr metadata was not cleared 李飞娟
2025-04-17 8:17 ` Jani Nikula [this message]
2025-04-21 6:49 ` 李飞娟
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=87cydbp5gs.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=feijuan.li@samsung.com \
--cc=hongfei.tang@samsung.com \
--cc=jingoohan1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=minggui.yan@samsung.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;
as well as URLs for NNTP newsgroup(s).