From: Mark Zhang <nvmarkzhang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Cc: linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Thierry Reding
<thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Subject: Re: [PATCH] drm: tegra: check HDMI sink capability
Date: Tue, 18 Dec 2012 16:21:39 +0800 [thread overview]
Message-ID: <50D02793.2020900@gmail.com> (raw)
In-Reply-To: <1355767163-5423-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
Thanks. Honestly don't know drm has this function...
Mark
On 12/18/2012 01:59 AM, Lucas Stach wrote:
> Check if sink is HDMI capable when enabling an output. This disables
> HDMI audio/infoframes if we are talking to a plain DVI sink. All things
> except this check are already in place.
>
> Signed-off-by: Lucas Stach <dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
> ---
> drivers/gpu/drm/tegra/hdmi.c | 3 +++
> 1 Datei geändert, 3 Zeilen hinzugefügt(+)
>
> diff --git a/drivers/gpu/drm/tegra/hdmi.c b/drivers/gpu/drm/tegra/hdmi.c
> index ab40164..32ea7d4 100644
> --- a/drivers/gpu/drm/tegra/hdmi.c
> +++ b/drivers/gpu/drm/tegra/hdmi.c
> @@ -673,6 +673,9 @@ static int tegra_output_hdmi_enable(struct tegra_output *output)
> usleep_range(1000, 2000);
> tegra_periph_reset_deassert(hdmi->clk);
>
> + /* if the connected sink is not HDMI capable fall back to plain DVI */
> + hdmi->dvi = !drm_detect_hdmi_monitor((struct edid *)output->edid);
> +
> tegra_dc_writel(dc, VSYNC_H_POSITION(1),
> DC_DISP_DISP_TIMING_OPTIONS);
> tegra_dc_writel(dc, DITHER_CONTROL_DISABLE | BASE_COLOR_SIZE888,
>
prev parent reply other threads:[~2012-12-18 8:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 17:59 [PATCH] drm: tegra: check HDMI sink capability Lucas Stach
[not found] ` <1355767163-5423-1-git-send-email-dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org>
2012-12-18 6:50 ` Thierry Reding
[not found] ` <20121218065056.GA4909-RM9K5IK7kjIyiCvfTdI0JKcOhU4Rzj621B7CTYaBSLdn68oJJulU0Q@public.gmane.org>
2012-12-18 9:23 ` Lucas Stach
2012-12-18 8:21 ` Mark Zhang [this message]
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=50D02793.2020900@gmail.com \
--to=nvmarkzhang-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=dev-8ppwABl0HbeELgA04lAiVw@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org \
--cc=thierry.reding-RM9K5IK7kjKj5M59NBduVrNAH6kLmebB@public.gmane.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;
as well as URLs for NNTP newsgroup(s).