All of lore.kernel.org
 help / color / mirror / Atom feed
From: Uma Shankar <uma.shankar@intel.com>
To: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Cc: dcastagna@chromium.org, jonas@kwiboo.se, seanpaul@chromium.org,
	ville.syrjala@intel.com, maarten.lankhorst@intel.com
Subject: [v8 10/10] drm/i915: Added DRM Infoframe handling for BYT/CHT
Date: Tue,  9 Apr 2019 22:14:44 +0530	[thread overview]
Message-ID: <1554828284-17776-11-git-send-email-uma.shankar@intel.com> (raw)
In-Reply-To: <1554828284-17776-1-git-send-email-uma.shankar@intel.com>

BYT/CHT doesn't support DRM Infoframe. This caused
a WARN_ON due to a missing CASE while executing
intel_hdmi_infoframes_enabled function. This patch
fixes the same.

Signed-off-by: Uma Shankar <uma.shankar@intel.com>
---
 drivers/gpu/drm/i915/intel_hdmi.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
index 56a36b5..34f9805 100644
--- a/drivers/gpu/drm/i915/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/intel_hdmi.c
@@ -122,6 +122,8 @@ static u32 g4x_infoframe_enable(unsigned int type)
 		return VIDEO_DIP_ENABLE_SPD;
 	case HDMI_INFOFRAME_TYPE_VENDOR:
 		return VIDEO_DIP_ENABLE_VENDOR;
+	case HDMI_INFOFRAME_TYPE_DRM:
+		return 0;
 	default:
 		MISSING_CASE(type);
 		return 0;
-- 
1.9.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-04-09 16:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 16:44 [v8 00/10] Add HDR Metadata Parsing and handling in DRM layer Uma Shankar
2019-04-09 16:44 ` [v8 01/10] drm: Add HDR source metadata property Uma Shankar
2019-05-04 10:17   ` Jonas Karlman
2019-05-07  9:03     ` Shankar, Uma
2019-05-07 10:25       ` Ville Syrjälä
2019-05-07 12:10         ` Ville Syrjälä
2019-05-08  9:03           ` Shankar, Uma
2019-05-07 12:07   ` Ville Syrjälä
2019-04-09 16:44 ` [v8 02/10] drm: Parse HDR metadata info from EDID Uma Shankar
2019-05-07 13:32   ` Kazlauskas, Nicholas
2019-04-09 16:44 ` [v8 03/10] drm: Enable HDR infoframe support Uma Shankar
2019-04-09 16:44 ` [v8 04/10] drm/i915: Attach HDR metadata property to connector Uma Shankar
2019-04-09 16:44 ` [v8 05/10] drm/i915: Write HDR infoframe and send to panel Uma Shankar
2019-04-09 16:44 ` [v8 06/10] drm/i915: Add HLG EOTF Uma Shankar
2019-04-09 16:44 ` [v8 07/10] drm/i915: Enable infoframes on GLK+ for HDR Uma Shankar
2019-04-09 16:44 ` [v8 08/10] drm/i915:Enabled Modeset when HDR Infoframe changes Uma Shankar
2019-05-07 12:01   ` Ville Syrjälä
2019-05-08  9:58     ` Shankar, Uma
2019-04-09 16:44 ` [v8 09/10] drm/i915: Set Infoframe for non modeset case for HDR Uma Shankar
2019-04-09 16:44 ` Uma Shankar [this message]
2019-04-09 18:08 ` ✗ Fi.CI.CHECKPATCH: warning for Add HDR Metadata Parsing and handling in DRM layer (rev8) Patchwork
2019-04-09 18:30 ` ✓ Fi.CI.BAT: success " Patchwork
2019-04-10  7:44 ` ✓ 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=1554828284-17776-11-git-send-email-uma.shankar@intel.com \
    --to=uma.shankar@intel.com \
    --cc=dcastagna@chromium.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jonas@kwiboo.se \
    --cc=maarten.lankhorst@intel.com \
    --cc=seanpaul@chromium.org \
    --cc=ville.syrjala@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.