On Fri, May 23, 2014 at 12:05 PM, Stephen Warren [off-list ref] wrote:

On 05/22/2014 09:55 PM, Dylan Reid wrote:
...

quoted

quoted

quoted

quoted

quoted

quoted

quoted

quoted

On Tue, May 20, 2014 at 2:55 PM, Stephen Warren [off-list ref] wrote:

...

quoted

quoted

quoted

quoted

quoted

quoted

quoted

quoted

quoted

Now I have the same results as Thierry; speaker-test looks like it
should be working, yet I don't hear any audio from the monitor. I know
the monitor works, since I've used it extensively for testing GeForce
GPU HDMI audio.

...

quoted

Took all day, but I did get to try this.

on U-Boot commit d7782d0, flashed with Stephen's u-boot flasher from github.

And kernel at 81d0207 - ARM: tegra: enable HD-Audio controller in defconfig
plus the addition of the hda node "okay"  to the jetson-tk1 DT.

I can hear the jetson's audio on the TV.  This is currently a sample
size of one TV, I'll set up the Quantum Data tomorrow and check that
it works there as well.

I tried that same U-Boot commit (with a few device-mode USB patches on
top that shouldn't affect anything since I didn't use USB device mode)
and have the same results.

My monitor is a Dell U2410 with sound bar.

I did notice one strange thing: /proc/asound/card0/eld#3.0 said:

monitor_present         0
eld_valid               0

This is odd, since ELD information really should be present. Perhaps
tegradrm simply doesn't have the code to set up an eld yet though?
Anyway, I thought that in the absence of ELD information, ALSA core fell
back to allowing arbitrary audio formats to be used in the hope they'd
work anyway, so perhaps this isn't an issue.

I see the same thing.  I wouldn't be surprised if the ELD isn't yet
configured by tegradrm.

I tried one other monitor that also worked.

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.  I'm not sure
why the jitter test wouldn't run, the QD didn't give a reason for
failure on that one.