From: Shashank Sharma <shashank.sharma@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v3 0/7] YCBCR 4:2:0/4:4:4 output support for LSPCON
Date: Fri, 5 Jan 2018 15:15:28 +0530 [thread overview]
Message-ID: <1515145535-11228-1-git-send-email-shashank.sharma@intel.com> (raw)
This patch series adds YCBCR 4:2:0 output support for LSPCON displays.
In order to indicate the color format of output, to the LSPCON device,
a source has to set and send proper AVI infoframes to LSPCON. So this
patch series:
- first adds AVI infoframes support for LSPCON
- then adds YCBCR 4:2:0 output support for LSPCON
Previous versions of this series and its review can be found here:
https://patchwork.freedesktop.org/series/28536/
https://patchwork.freedesktop.org/series/33794/
In order to address review comment from V2, I have added 2 new patches
in this series, hence sending V3.
Shashank Sharma (7):
drm/i915: Add CRTC output format YCBCR 4:2:0
drm/i915: Add CRTC output format YCBCR 4:4:4
drm/i915: Check LSPCON vendor OUI
drm/i915: Add AVI infoframe support for LSPCON
drm/i915: Write AVI infoframes for MCA LSPCON
drm/i915: Write AVI infoframes for Parade LSPCON
drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON
drivers/gpu/drm/i915/i915_reg.h | 2 +
drivers/gpu/drm/i915/intel_color.c | 3 +-
drivers/gpu/drm/i915/intel_ddi.c | 28 ++-
drivers/gpu/drm/i915/intel_display.c | 73 +++++---
drivers/gpu/drm/i915/intel_dp.c | 10 +
drivers/gpu/drm/i915/intel_drv.h | 37 +++-
drivers/gpu/drm/i915/intel_hdmi.c | 23 ++-
drivers/gpu/drm/i915/intel_lspcon.c | 343 +++++++++++++++++++++++++++++++++--
drivers/gpu/drm/i915/intel_panel.c | 2 +-
9 files changed, 469 insertions(+), 52 deletions(-)
--
2.7.4
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2018-01-05 9:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 9:45 Shashank Sharma [this message]
2018-01-05 9:45 ` [PATCH v3 1/7] drm/i915: Add CRTC output format YCBCR 4:2:0 Shashank Sharma
2018-01-05 11:21 ` Maarten Lankhorst
2018-01-17 18:27 ` Ville Syrjälä
2018-01-18 6:21 ` Sharma, Shashank
2018-01-05 9:45 ` [PATCH v3 2/7] drm/i915: Add CRTC output format YCBCR 4:4:4 Shashank Sharma
2018-01-17 18:27 ` Ville Syrjälä
2018-01-18 6:23 ` Sharma, Shashank
2018-01-05 9:45 ` [PATCH v3 3/7] drm/i915: Check LSPCON vendor OUI Shashank Sharma
2018-01-05 9:45 ` [PATCH v3 4/7] drm/i915: Add AVI infoframe support for LSPCON Shashank Sharma
2018-01-05 9:45 ` [PATCH v3 5/7] drm/i915: Write AVI infoframes for MCA LSPCON Shashank Sharma
2018-01-05 9:45 ` [PATCH v3 6/7] drm/i915: Write AVI infoframes for Parade LSPCON Shashank Sharma
2018-01-05 9:45 ` [PATCH v3 7/7] drm/i915: Add YCBCR 4:2:0/4:4:4 support for LSPCON Shashank Sharma
2018-01-17 18:27 ` Ville Syrjälä
2018-01-18 6:27 ` Sharma, Shashank
2018-01-18 9:30 ` Maarten Lankhorst
2018-01-18 16:16 ` Sharma, Shashank
2018-01-18 14:03 ` Ville Syrjälä
2018-01-18 15:30 ` Sharma, Shashank
2018-01-18 15:35 ` Ville Syrjälä
2018-01-18 15:52 ` Sharma, Shashank
2018-01-05 10:15 ` ✗ Fi.CI.BAT: warning for YCBCR 4:2:0/4:4:4 output " 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=1515145535-11228-1-git-send-email-shashank.sharma@intel.com \
--to=shashank.sharma@intel.com \
--cc=intel-gfx@lists.freedesktop.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