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] [v8 0/5] enhanced edid driver compatibility
Date: Thu, 17 Mar 2022 20:41:57 +0800 [thread overview]
Message-ID: <20220317124202.14189-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.
v7: using different parameters to store CEA and DisplayID block index.
configure DisplayID extansion block index before search available
DisplayID block.
v8: revert patch [v7 2/5] change.
And check cea pointer return from drm_find_cea_extension().
If drvier got the same cea pointer then exit this routine.
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 | 174 ++++++++++++++++++++++++--------
include/drm/drm_edid.h | 4 +-
4 files changed, 144 insertions(+), 47 deletions(-)
--
2.17.1
next reply other threads:[~2022-03-17 12:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-17 12:41 Lee Shawn C [this message]
2022-03-17 12:41 ` [Intel-gfx] [v8 1/5] drm/edid: seek for available CEA block from specific EDID block index Lee Shawn C
2022-03-17 12:41 ` [Intel-gfx] [v8 2/5] drm/edid: parse multiple CEA extension block Lee Shawn C
2022-03-17 12:42 ` [Intel-gfx] [v8 3/5] drm/edid: read HF-EEODB ext block Lee Shawn C
2022-03-23 10:11 ` Jani Nikula
2022-03-23 12:02 ` Jani Nikula
2022-03-23 12:04 ` Simon Ser
2022-03-23 12:14 ` Jani Nikula
2022-03-23 14:26 ` Ville Syrjälä
2022-03-17 12:42 ` [Intel-gfx] [v8 4/5] drm/edid: parse HF-EEODB CEA extension block Lee Shawn C
2022-03-17 12:42 ` [Intel-gfx] [v8 5/5] drm/edid: check for HF-SCDB block Lee Shawn C
2022-03-17 12:53 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for enhanced edid driver compatibility (rev4) Patchwork
2022-03-17 12:55 ` [Intel-gfx] ✗ Fi.CI.SPARSE: " Patchwork
2022-03-17 13:28 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-17 15:05 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=20220317124202.14189-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