From: narmstrong@baylibre.com (Neil Armstrong)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 3/4] drm: bridge: dw-hdmi: Enable CSC even for DVI
Date: Mon, 30 Jan 2017 12:05:17 +0100 [thread overview]
Message-ID: <1485774318-21916-4-git-send-email-narmstrong@baylibre.com> (raw)
In-Reply-To: <1485774318-21916-1-git-send-email-narmstrong@baylibre.com>
If the input pixel format is not RGB, the CSC must be enabled in order to
provide valid pixel to DVI sinks.
This patch removes the hdmi only dependency on the CSC enabling.
Reviewed-by: Jose Abreu <joabreu@synopsys.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Signed-off-by: Neil Armstrong <narmstrong@baylibre.com>
---
drivers/gpu/drm/bridge/dw-hdmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/bridge/dw-hdmi.c b/drivers/gpu/drm/bridge/dw-hdmi.c
index a8083f4..f75e5f9 100644
--- a/drivers/gpu/drm/bridge/dw-hdmi.c
+++ b/drivers/gpu/drm/bridge/dw-hdmi.c
@@ -1317,8 +1317,8 @@ static void dw_hdmi_enable_video_path(struct dw_hdmi *hdmi)
hdmi_writeb(hdmi, clkdis, HDMI_MC_CLKDIS);
}
- /* Enable color space conversion if needed (for HDMI sinks only). */
- if (hdmi->sink_is_hdmi && is_color_space_conversion(hdmi))
+ /* Enable color space conversion if needed */
+ if (is_color_space_conversion(hdmi))
hdmi_writeb(hdmi, HDMI_MC_FLOWCTRL_FEED_THROUGH_OFF_CSC_IN_PATH,
HDMI_MC_FLOWCTRL);
else
--
1.9.1
next prev parent reply other threads:[~2017-01-30 11:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 11:05 [PATCH 0/4] drm: bridge: dw-hdmi: Add support for Custom PHYs Neil Armstrong
2017-01-30 11:05 ` [PATCH 1/4] drm: bridge: dw-hdmi: Switch to regmap for register access Neil Armstrong
2017-01-30 11:05 ` [PATCH 2/4] drm: bridge: dw-hdmi: Add support for custom PHY handling Neil Armstrong
2017-01-30 11:05 ` Neil Armstrong [this message]
2017-01-30 11:05 ` [PATCH 4/4] drm: bridge: dw-hdmi: Take input format from plat_data Neil Armstrong
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=1485774318-21916-4-git-send-email-narmstrong@baylibre.com \
--to=narmstrong@baylibre.com \
--cc=linus-amlogic@lists.infradead.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
all inboxes | Powered by JetHome®