From: David Henningsson <david.henningsson@canonical.com>
To: "Alexander E. Patrakov" <patrakov@gmail.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
Takashi Iwai <tiwai@suse.de>
Cc: Anssi Hannula <anssi.hannula@iki.fi>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: Radeon unconnected HDMI eats samples at 280 kHz
Date: Sat, 20 Sep 2014 01:35:12 +0200 [thread overview]
Message-ID: <541CBDB0.4020408@canonical.com> (raw)
In-Reply-To: <541C73C8.3040606@gmail.com>
On 2014-09-19 20:19, Alexander E. Patrakov wrote:
> 19.09.2014 23:47, David Henningsson wrote:
>> If audio_enabled quickly changes to off and then on when there is a mode
>> change, it might make sense to *not* wake up the audio driver in this
>> case, as I assume that the audio capabilities on the HDMI TV will not
>> change just because the video mode changes.
>
> Unfortunately, they will. Some low-resolution video modes just don't
> have enough pixel clock to transfer the 7.1 audio signal at 192 kHz. See
> the table on page 105 (shown as 121 in some readers) of
> http://www.microprocessor.org/HDMISpecification13a.pdf , section "7.3.3
> Video Dependency".
Ok, I stand corrected. I wonder what the least ugly thing to do would be
if the user is currently running audio when this happens, e g, if the
user is running a game with background music, and goes to "video
settings" and switches mode.
But if such thing would audio glitch anyhow, like it seems maybe we
should let the audio_enabled signal pass through to the audio side to
indicate a short disconnection. It's just not going to be that fun
if/when we implement reprobing the HDMI device on plug in. And also the
risk of the audio stream switching to somewhere else, like going from
HDMI to analog.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2014-09-19 23:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-17 13:40 Radeon unconnected HDMI eats samples at 280 kHz David Henningsson
2014-09-17 21:26 ` Anssi Hannula
2014-09-18 4:13 ` David Henningsson
2014-09-18 7:33 ` Takashi Iwai
2014-09-18 7:54 ` David Henningsson
2014-09-18 22:29 ` Deucher, Alexander
2014-09-19 13:38 ` David Henningsson
2014-09-19 14:14 ` Deucher, Alexander
2014-09-19 17:47 ` David Henningsson
2014-09-19 18:19 ` Alexander E. Patrakov
2014-09-19 23:35 ` David Henningsson [this message]
2014-09-20 9:37 ` Anssi Hannula
2014-09-20 9:39 ` Alexander E. Patrakov
2014-09-19 23:32 ` Deucher, Alexander
2014-09-20 0:06 ` David Henningsson
2014-09-20 9:31 ` Alexander E. Patrakov
2014-09-22 12:46 ` Deucher, Alexander
2014-09-22 14:39 ` David Henningsson
2014-09-22 14:52 ` Deucher, Alexander
2014-09-23 9:47 ` David Henningsson
2014-09-23 14:07 ` Deucher, Alexander
2014-09-24 9:27 ` David Henningsson
2014-09-24 21:37 ` Deucher, Alexander
2014-09-30 12:24 ` David Henningsson
2014-09-30 12:45 ` Deucher, Alexander
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=541CBDB0.4020408@canonical.com \
--to=david.henningsson@canonical.com \
--cc=Alexander.Deucher@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=anssi.hannula@iki.fi \
--cc=patrakov@gmail.com \
--cc=tiwai@suse.de \
/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