All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Christian König" <deathsimple@vodafone.de>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: Re: [PATCH 1/2] drm/radeon/kms: use drm_detect_hdmi_monitor for picking encoder mode
Date: Fri, 27 Jan 2012 13:48:21 +0100	[thread overview]
Message-ID: <4F229D15.2000300@vodafone.de> (raw)
In-Reply-To: <CACna6ryYaW-VQnhK_9N9Y-w7NgrRYvjQk33vAfGiCEtBvrCHhw@mail.gmail.com>

On -10.01.-28163 20:59, Rafał Miłecki wrote:
> 2012/1/20<alexdeucher@gmail.com>:
>> From: Alex Deucher<alexander.deucher@amd.com>
>>
>> We were previously just checking for audio.
> So... Does every hdmi_monitor supports audio? Or should it rather be
> if (drm_detect_monitor_audio(radeon_connector->edid)&&
> drm_detect_hdmi_monitor(radeon_connector->edid))
> ?
>
> Sorry, I'm not familiar enough with EDID.

IIRC HDMI is more than just Audio, so it is possible for a TV to 
announce support for HDMI but not Audio.

So setting the decoder moder should depend on whether or not a TV 
announces HDMI support, but actually sending audio should depend on the 
supported audio capabilities.

Christian.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

      reply	other threads:[~2012-01-27 12:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-20 20:03 [PATCH 1/2] drm/radeon/kms: use drm_detect_hdmi_monitor for picking encoder mode alexdeucher
2012-01-20 20:03 ` [PATCH 2/2] drm/radeon/kms: refine TMDS dual link checks alexdeucher
2012-01-27  8:26 ` [PATCH 1/2] drm/radeon/kms: use drm_detect_hdmi_monitor for picking encoder mode Rafał Miłecki
2012-01-27 12:48   ` Christian König [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=4F229D15.2000300@vodafone.de \
    --to=deathsimple@vodafone.de \
    --cc=alexander.deucher@amd.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=zajec5@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 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.