From: Christopher Freeman <cfreeman@nvidia.com>
To: linux-fbdev@vger.kernel.org
Subject: Re: [PATCH] video: Check EDID for HDMI connection
Date: Tue, 08 Apr 2014 21:43:56 +0000 [thread overview]
Message-ID: <CF69BB5D.3C9E7%cfreeman@nvidia.com> (raw)
In-Reply-To: <1395873337-41305-1-git-send-email-cfreeman@nvidia.com>
On 4/8/14 2:19 AM, "Tomi Valkeinen" <tomi.valkeinen@ti.com> wrote:
>* PGP Signed by an unknown key
>
>Hi,
>
>On 27/03/14 00:35, cfreeman@nvidia.com wrote:
>> From: David Ung <davidu@nvidia.com>
>>
>> Check EDID Vendor Specific Data Block bytes to see if the connection
>> is HDMI and set FB_MISC_HDMI.
>>
>> Signed-off-by: David Ung <davidu@nvidia.com>
>> Signed-off-by: Christopher Freeman<cfreeman@nvidia.com>
>> ---
>
>Patch looks fine, but how do you use the flag? Shouldn't things like
>detecting if the monitor supports audio be done with some more detailed
>bits in the EDID data (not that I remember much from the HDMI spec).
The Tegra HDMI driver uses FB_MISC_HDMI to select the type of connection
it has hdmi/dvi and setup the avi info frames.
agree that we could use the EDID data to determine the audio format
support and sampling rates, but currently that's not being used.
I think determining the audio format and sample rate support could be
added in a separate and future patch.
>
> Tomi
>
>
>
>* Unknown Key
>* 0xBC961EF5
-----------------------------------------------------------------------------------
This email message is for the sole use of the intended recipient(s) and may contain
confidential information. Any unauthorized review, use, disclosure or distribution
is prohibited. If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.
-----------------------------------------------------------------------------------
next prev parent reply other threads:[~2014-04-08 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 22:35 [PATCH] video: Check EDID for HDMI connection cfreeman
2014-04-08 9:19 ` Tomi Valkeinen
2014-04-08 21:43 ` Christopher Freeman [this message]
2014-04-14 12:53 ` Tomi Valkeinen
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=CF69BB5D.3C9E7%cfreeman@nvidia.com \
--to=cfreeman@nvidia.com \
--cc=linux-fbdev@vger.kernel.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).