From: Lee Shawn C <shawn.c.lee@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: cooper.chiou@intel.com, william.tseng@intel.com,
jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [v6 0/5] enhanced edid driver compatibility
Date: Fri, 11 Mar 2022 09:22:13 +0800 [thread overview]
Message-ID: <20220311012218.19025-1-shawn.c.lee@intel.com> (raw)
Support to parse multiple CEA extension blocks and HF-EEODB to
extend drm edid driver's capability.
v4: add one more patch to support HF-SCDB
v5: HF-SCDB and HF-VSDBS carry the same SCDS data. Reuse
drm_parse_hdmi_forum_vsdb() to parse this packet.
v6: save proper extension block index if CTA data information
was found in DispalyID block.
Lee Shawn C (5):
drm/edid: seek for available CEA block from specific EDID block index
drm/edid: parse multiple CEA extension block
drm/edid: read HF-EEODB ext block
drm/edid: parse HF-EEODB CEA extension block
drm/edid: check for HF-SCDB block
drivers/gpu/drm/drm_connector.c | 8 +-
drivers/gpu/drm/drm_displayid.c | 5 +-
drivers/gpu/drm/drm_edid.c | 173 ++++++++++++++++++++++++--------
include/drm/drm_edid.h | 4 +-
4 files changed, 143 insertions(+), 47 deletions(-)
--
2.17.1
next reply other threads:[~2022-03-11 1:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 1:22 Lee Shawn C [this message]
2022-03-11 1:22 ` [Intel-gfx] [v6 1/5] drm/edid: seek for available CEA block from specific EDID block index Lee Shawn C
2022-03-11 23:41 ` Drew Davenport
2022-03-12 13:33 ` Lee, Shawn C
2022-03-11 1:22 ` [Intel-gfx] [v6 2/5] drm/edid: parse multiple CEA extension block Lee Shawn C
2022-03-11 1:22 ` [Intel-gfx] [v6 3/5] drm/edid: read HF-EEODB ext block Lee Shawn C
2022-03-11 1:22 ` [Intel-gfx] [v6 4/5] drm/edid: parse HF-EEODB CEA extension block Lee Shawn C
2022-03-11 1:22 ` [Intel-gfx] [v6 5/5] drm/edid: check for HF-SCDB block Lee Shawn C
2022-03-11 2:11 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for enhanced edid driver compatibility (rev2) Patchwork
2022-03-11 2:13 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-11 2:38 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-11 4:44 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=20220311012218.19025-1-shawn.c.lee@intel.com \
--to=shawn.c.lee@intel.com \
--cc=cooper.chiou@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=william.tseng@intel.com \
/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