From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Dylan Reid <dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
Cc: Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Peter De Schrijver
<pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>,
"linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 1/2] ARM: tegra: Add Tegra124 HDA support
Date: Wed, 04 Jun 2014 11:13:31 -0600 [thread overview]
Message-ID: <538F53BB.7060903@wwwdotorg.org> (raw)
In-Reply-To: <CAEUnVG63BCgpGuo+qcYkvpnVSSguBy9xwSC_AoZqCt1RgBqm7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 05/23/2014 02:34 PM, Dylan Reid wrote:
...
> I also ran the HDMI audio compliance test suite. It failed the ACR
> (clock regeneration packet) test and the audio packet timing jitter
> test, I could see that upsetting some monitors. It looks like ACR
> packets are generated for 44.1 even when playing 48k.
That's because the only thing that sets hdmi->audio_freq is
tegra_hdmi_probe(). There needs to be a callback from the sound/HDA
driver to the display driver telling it what audio frequency is in use.
next prev parent reply other threads:[~2014-06-04 17:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 20:37 [PATCH 1/2] ARM: tegra: Add Tegra124 HDA support Dylan Reid
[not found] ` <CAEUnVG7+=1ko8NL1Z3ovSpGveUADUidy4sBhU_dTUe1zbe-bMA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-20 21:55 ` Stephen Warren
[not found] ` <537BCF39.6050909-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-20 23:28 ` Dylan Reid
[not found] ` <CAEUnVG7CRWx5Y3RsgPzrHgYRGAx=bS4WY=w1xBUw0Ukt0DTdUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-20 23:42 ` Stephen Warren
2014-05-21 20:55 ` Thierry Reding
2014-05-21 21:10 ` Dylan Reid
[not found] ` <CAEUnVG7tDjw_6wHc=FN0KsOKsSS1u8H8SzYdxt9VCwUsARRTeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-22 9:50 ` Thierry Reding
2014-05-22 17:48 ` Dylan Reid
[not found] ` <CAEUnVG5pNMzDoXGso+UiAWPpD0hNPhBPyGr8KfV587AuU70QPQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-22 17:54 ` Stephen Warren
[not found] ` <537E39D9.2000304-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-22 18:05 ` Dylan Reid
[not found] ` <CAEUnVG4UettOj0xDy+f6qEhUbhNs=u-wgyCf_Prsd2JpnmFfLw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-23 3:55 ` Dylan Reid
2014-05-23 19:05 ` Stephen Warren
[not found] ` <537F9BEB.5020102-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-23 20:34 ` Dylan Reid
[not found] ` <CAEUnVG63BCgpGuo+qcYkvpnVSSguBy9xwSC_AoZqCt1RgBqm7w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-31 1:45 ` Dylan Reid
[not found] ` <CAEUnVG52fJhd9213fdydoUW11N0yZ31T2MZ2BPmd5Q2xkZ8XeQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-04 17:32 ` Stephen Warren
[not found] ` <538F5848.1050803-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-06-04 17:51 ` Dylan Reid
[not found] ` <CAEUnVG7bbcPjRcGxn_GAJ7rKJy4g_5veEsRnU 2yCDVWFY3ncUQ@mail.gmail.com>
[not found] ` <CAEUnVG7bbcPjRcGxn_GAJ7rKJy4g_5veEsRnU2yCDVWFY3ncUQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-04 19:04 ` Stephen Warren
[not found] ` <538F6DA5.9040608-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-06-04 20:43 ` Thierry Reding
2014-06-04 17:13 ` Stephen Warren [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-05-20 2:35 Dylan Reid
[not found] ` <1400553346-23238-1-git-send-email-dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-05-20 18:24 ` Stephen Warren
[not found] ` <537B9DE3.5020807-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-05-20 18:31 ` Stephen Warren
2014-06-16 19:10 ` Stephen Warren
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=538F53BB.7060903@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dgreid-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pdeschrijver-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@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 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.