You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
HDMI output only works on single channel on Up2 #226
@ranj063 I am unable to reproduce it currently as my patch doesn't appear to be working anymore and therefore I am getting no devices populated. It will take me some time to debug.
I can't play to HDMI: aplay: set_params:1363: Unable to install hw params:
Even though I try to set the pins with alsamixer (?)
kernel: a5ddc3d
sof: 43da169
tplg: sof-apl-pcm512x.tplg
@lgirdwood yep, it is not pulseaudio. This can be reproduced by renaming also alsactl. I was trying to disable it "nicely" by fiddling with systemd, but this is the easiest way. So with "first boot" all our pga volumes
are indeed 0 on the left channel (and right channel is max).
actually I see this in firmware log:
0 2 unknown 74888.697917 4.166667 volume.c:387 value 0
0 2 unknown 74890.989583 2.291667 volume.c:388 value 0
0 2 unknown 74893.333333 2.343750 volume.c:387 value 1
0 2 unknown 74895.625000 2.291667 volume.c:388 value 65536
and that means it is coming from kernel side with ipc ... so someone is setting it to 0 but with empty data-> as a consequence only other channel is set. And that means that default pga value is max (which is correct).
Activity
keyonjie commentedon Oct 30, 2018
this should be PGA default value issue, the volume of Left channel is set to 0 by default wrongly.
plbossart commentedon Oct 30, 2018
@keyonjie what do you mean? Is this a known topology issue? or a driver issue?
cujomalainey commentedon Oct 30, 2018
I noticed this in chrome is as well. I assumed it was a ucm issue
ranj063 commentedon Oct 31, 2018
@cujomalainey do you still have this issue on chrome? I ran into this issue earlier but couldnt reproduce it after I used the updated ucm
cujomalainey commentedon Oct 31, 2018
I'll try and reproduce it if I have time tomorrow, I usually trigger it when I'm building the 4.18 kernel
keyonjie commentedon Oct 31, 2018
I believe there is bug here, on Yorp, ucm file may hide this bug.
plbossart commentedon Oct 31, 2018
@mengdonglin can you please assign someone to look into this and check on the validation side? Looks like a blocking P1 to me?
cujomalainey commentedon Nov 1, 2018
@ranj063 I am unable to reproduce it currently as my patch doesn't appear to be working anymore and therefore I am getting no devices populated. It will take me some time to debug.
markyang commentedon Nov 2, 2018
Summary:
This issue cannot be reproduced using the mixer configuration as follows:
pin5-port0 : cvt2
pin6-port0 : cvt3
pin7-port0 : cvt4
Test Steps:
Test env:
sof master: 43da169
sof tool: 937032f
kernel sof-dev: a5ddc3d
tplg: sof-apl-pcm512x.tplg-937032f
juimonen commentedon Nov 2, 2018
I can't play to HDMI: aplay: set_params:1363: Unable to install hw params:
Even though I try to set the pins with alsamixer (?)
kernel: a5ddc3d
sof: 43da169
tplg: sof-apl-pcm512x.tplg
plbossart commentedon Nov 6, 2018
I think it's a topology issue, all the HDAudio streams have the left channel muted:
I absolutely didn't make this selection so it's coming from the topology or the driver. @ranj063 does this ring a bell?
4 remaining items
juimonen commentedon Nov 8, 2018
@lgirdwood yep, it is not pulseaudio. This can be reproduced by renaming also alsactl. I was trying to disable it "nicely" by fiddling with systemd, but this is the easiest way. So with "first boot" all our pga volumes
are indeed 0 on the left channel (and right channel is max).
juimonen commentedon Nov 8, 2018
actually I see this in firmware log:
0 2 unknown 74888.697917 4.166667 volume.c:387 value 0
0 2 unknown 74890.989583 2.291667 volume.c:388 value 0
0 2 unknown 74893.333333 2.343750 volume.c:387 value 1
0 2 unknown 74895.625000 2.291667 volume.c:388 value 65536
So channel 0 -> 0 volume and channel 1 -> max
lgirdwood commentedon Nov 8, 2018
@juimonen ok, looks like bug in volume.c
juimonen commentedon Nov 8, 2018
yep, this is the set before get:
0 2 unknown 73280.885417 2.864583 volume.c:320 value 0
0 2 unknown 73283.645833 2.760417 volume.c:321 value 0
0 2 unknown 73286.562500 2.916667 volume.c:320 value 0
0 2 unknown 73289.114583 2.552083 volume.c:321 value 0
so same channel 0 is set twice to 0. channel 1 is left untouched so it has max.
juimonen commentedon Nov 8, 2018
and that means it is coming from kernel side with ipc ... so someone is setting it to 0 but with empty data-> as a consequence only other channel is set. And that means that default pga value is max (which is correct).
juimonen commentedon Nov 8, 2018
and it seams it is the restore of controls that sets the value incorrectly.
sorry for dumping the debug status every minute, will stop now.
juimonen commentedon Nov 8, 2018
#258
plbossart commentedon Nov 8, 2018
@juimonen it's ok to share your findings live, it helps the rest of the team follow what might be happening. Thanks for looking into this!
plbossart commentedon Nov 12, 2018
closed with PR258
Merge pull request thesofproject#226 from Kloenk/RUST_LIB_SRC
xen/netfront: destroy queues before real_num_tx_queues is zeroed
selftests/bpf: Add mprog API tests for BPF tcx links
media: i2c: tc358743: Fix crash in the probe error path when using po…