[alsa-devel] [PATCH v3 0/5] ALSA: hda - hdmi: ATI/AMD multi-channel and HBR support

[Anssi Hannula]

10.11.2013 07:42, Olivier Langlois kirjoitti:
> Hi Anssi,
> 
> On Sat, 2013-11-09 at 00:03 +0200, Anssi Hannula wrote:
> 
>>
>> You mean you just downloaded the files and put them in-tree, right?
> 
> Right. Here are the files that I have replaced in 3.11.7 tree:
> 
> lano1106 at whippet2 ~/dev/linux-ck/src/linux-3.11/sound/pci/hda $ ls
> *.orig
> hda_codec.c.orig  hda_codec.h.orig  hda_eld.c.orig  hda_jack.c.orig
> hda_jack.h.orig  hda_local.h.orig  patch_hdmi.c.orig
> 
> 
>>
>> If it built without warnings, it is probably OK...
> 
> It has built flawlessly.
> 
>>
>> OK, this is pretty weird indeed. Could you apply the attached debugging
>> prints and then provide dmesg?
>>
>>
> Sure, here is the output:
> 
> [   78.384821] ALSA sound/pci/hda/patch_hdmi.c:1167 HDMI hot plug event:
> Codec=0 Pin=3 Device=0 Inactive=0 Presence_Detect=0 ELD_Valid=1
> [   78.384834] ALSA sound/pci/hda/patch_hdmi.c:1512 HDMI status: Codec=0
> Pin=3 Presence_Detect=1 ELD_Valid=1
> [  128.437676] ALSA sound/pci/hda/patch_hdmi.c:678 HDMI: select CA 0x13
> for 8-channel allocation:  FL/FR LFE FC RL/RR RLC/RRC
> [  128.437797] CA XX 19 => 8
> [  128.437799] XX hdmi_map 00
> [  128.437801] XX hdmi_map 11
> [  128.437802] XX hdmi_map 26
> [  128.437804] XX hdmi_map 37
> [  128.437806] XX hdmi_map 43
> [  128.437807] XX hdmi_map 52
> [  128.437809] XX hdmi_map 64
> [  128.437810] XX hdmi_map 75
> [  128.437957] ALSA sound/pci/hda/patch_hdmi.c:3108
> atihdmi_pin_hbr_setup: NID=0x3, hbr-ctl=0x1
> 
> This is looking good. Maybe this is coming from how the channel mapping
> is communicated to speaker-test through ALSA API but I don't know much
> about that.
> 
> I'll try to understand as well on my side what is going on.

Hmm seems I can reproduce this issue just fine on my side now on
non-AMD, so I'm going to look into this myself as well. Looks a bit like
a speaker-test bug to me (since the printed channel numbers are
duplicated, and amixer shows proper chmap), though if that is the case I
wonder why I didn't see this before... I'll take a look.

-- 
Anssi Hannula