From: Stephen Warren <swarren@wwwdotorg.org>
To: Mikko Perttunen <mperttunen@nvidia.com>
Cc: thierry.reding@gmail.com, tbergstrom@nvidia.com,
dri-devel@lists.freedesktop.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/6] host1x: hdmi: Detect whether display is connected with HDMI or DVI
Date: Wed, 04 Sep 2013 12:40:58 -0600 [thread overview]
Message-ID: <52277EBA.6030105@wwwdotorg.org> (raw)
In-Reply-To: <1377704922-2824-3-git-send-email-mperttunen@nvidia.com>
On 08/28/2013 09:48 AM, Mikko Perttunen wrote:
> Use EDID data to determine whether the display supports HDMI or just DVI.
> This used to be hardcoded to be HDMI, which broke support for DVI displays
> that couldn't understand the interspersed audio/other data.
>
> If the EDID data isn't available, default to DVI, which should be a safer
> choice.
This seems like a bug-fix that might even be worth CC: stable?
next prev parent reply other threads:[~2013-09-04 18:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-28 15:48 [PATCH v2 0/6] HDMI support for Tegra114 Dalmore Mikko Perttunen
2013-08-28 15:48 ` [PATCH v2 1/6] host1x: hdmi: Add Tegra114 support Mikko Perttunen
2013-09-04 18:39 ` Stephen Warren
2013-09-04 21:55 ` Thierry Reding
2013-08-28 15:48 ` [PATCH v2 2/6] host1x: hdmi: Detect whether display is connected with HDMI or DVI Mikko Perttunen
2013-09-04 18:40 ` Stephen Warren [this message]
2013-09-04 21:59 ` Thierry Reding
2013-08-28 15:48 ` [PATCH v2 3/6] host1x: hdmi: Enable Vdd earlier for hotplug/DDC Mikko Perttunen
2013-09-04 18:44 ` Stephen Warren
2013-09-04 22:03 ` Mikko Perttunen
2013-09-04 22:24 ` Stephen Warren
2013-08-28 15:48 ` [PATCH v2 4/6] clk: tegra114: Initialize clocks needed for HDMI Mikko Perttunen
2013-09-04 18:45 ` Stephen Warren
2013-08-28 15:48 ` [PATCH v2 5/6] ARM: tegra: Add host1x, DC and HDMI to Tegra114 device tree Mikko Perttunen
2013-09-04 18:46 ` Stephen Warren
2013-08-28 15:48 ` [PATCH v2 6/6] ARM: tegra: Add HDMI to Tegra114 Dalmore " Mikko Perttunen
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=52277EBA.6030105@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@nvidia.com \
--cc=tbergstrom@nvidia.com \
--cc=thierry.reding@gmail.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