From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
stable@vger.kernel.org, Shawn C Lee <shawn.c.lee@intel.com>
Subject: Re: [PATCH] drm/edid: fix CEA extension byte #3 parsing
Date: Wed, 23 Mar 2022 17:09:07 +0200 [thread overview]
Message-ID: <Yjs4E5gl3KZoUOBR@intel.com> (raw)
In-Reply-To: <20220323100438.1757295-1-jani.nikula@intel.com>
On Wed, Mar 23, 2022 at 12:04:38PM +0200, Jani Nikula wrote:
> Only an EDID CEA extension has byte #3, while the CTA DisplayID Data
> Block does not. Don't interpret bogus data for color formats.
I think what we might want eventually is a cleaner split between
the CTA data blocks vs. the rest of the EDID CTA ext block. Only
the former is relevant for DisplayID.
But for a bugfix we want to keep it simple.
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> For most displays it's probably an unlikely scenario you'd have a CTA
> DisplayID Data Block without a CEA extension, but they do exist.
>
> Fixes: e28ad544f462 ("drm/edid: parse CEA blocks embedded in DisplayID")
> Cc: <stable@vger.kernel.org> # v4.15
> Cc: Shawn C Lee <shawn.c.lee@intel.com>
> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
>
> ---
>
> commit e28ad544f462 was merged in v5.3, but it has Cc: stable for v4.15.
>
> This is also fixed in my CEA data block iteration series [1], but we'll
> want the simple fix for stable first.
>
> Hum, CTA is formerly CEA, I and the code seem to use both, should we use
> only one or the other?
And before CEA it was called EIA (IIRC). Dunno if we also use that name
somewhere.
If someone cares enough I guess we could rename everything to "cta".
>
> [1] https://patchwork.freedesktop.org/series/101659/
> ---
> drivers/gpu/drm/drm_edid.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
> index 561f53831e29..ccf7031a6797 100644
> --- a/drivers/gpu/drm/drm_edid.c
> +++ b/drivers/gpu/drm/drm_edid.c
> @@ -5187,10 +5187,14 @@ static void drm_parse_cea_ext(struct drm_connector *connector,
>
> /* The existence of a CEA block should imply RGB support */
> info->color_formats = DRM_COLOR_FORMAT_RGB444;
> - if (edid_ext[3] & EDID_CEA_YCRCB444)
> - info->color_formats |= DRM_COLOR_FORMAT_YCBCR444;
> - if (edid_ext[3] & EDID_CEA_YCRCB422)
> - info->color_formats |= DRM_COLOR_FORMAT_YCBCR422;
> +
> + /* CTA DisplayID Data Block does not have byte #3 */
> + if (edid_ext[0] == CEA_EXT) {
> + if (edid_ext[3] & EDID_CEA_YCRCB444)
> + info->color_formats |= DRM_COLOR_FORMAT_YCBCR444;
> + if (edid_ext[3] & EDID_CEA_YCRCB422)
> + info->color_formats |= DRM_COLOR_FORMAT_YCBCR422;
> + }
>
> if (cea_db_offsets(edid_ext, &start, &end))
> return;
> --
> 2.30.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2022-03-23 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-23 10:04 [PATCH] drm/edid: fix CEA extension byte #3 parsing Jani Nikula
2022-03-23 15:09 ` Ville Syrjälä [this message]
2022-03-23 15:19 ` Jani Nikula
2022-03-24 9:58 ` Jani Nikula
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=Yjs4E5gl3KZoUOBR@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=shawn.c.lee@intel.com \
--cc=stable@vger.kernel.org \
/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