Skip to content

HDMI output only works on single channel on Up2 #226

Closed

Description

@plbossart

When trying the latest kernel code (topic/sof-dev) along with sof/soft master, I only get sound on a single channel.

The mixer configuration is this (need to use pin6-port0 with cvt2)
amixer -Dhw:0 cset numid=28 1

and command line
speaker-test -Dhw:0,1 -c2 -r48000 -t sine

Adding as a kernel bug for now until it's sorted out.

Activity

  1. added
    bugSomething isn't working
    APLApplies to ApolloLake platform
    on Oct 30, 2018
  2. keyonjie commented on Oct 30, 2018

    @keyonjie

    this should be PGA default value issue, the volume of Left channel is set to 0 by default wrongly.

  3. plbossart commented on Oct 30, 2018

    @plbossart
    MemberAuthor

    @keyonjie what do you mean? Is this a known topology issue? or a driver issue?

  4. cujomalainey commented on Oct 30, 2018

    @cujomalainey

    I noticed this in chrome is as well. I assumed it was a ucm issue

  5. ranj063 commented on Oct 31, 2018

    @ranj063
    Collaborator

    @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

  6. cujomalainey commented on Oct 31, 2018

    @cujomalainey

    I'll try and reproduce it if I have time tomorrow, I usually trigger it when I'm building the 4.18 kernel

  7. keyonjie commented on Oct 31, 2018

    @keyonjie

    @keyonjie what do you mean? Is this a known topology issue? or a driver issue?

    I believe there is bug here, on Yorp, ucm file may hide this bug.

  8. plbossart commented on Oct 31, 2018

    @plbossart
    MemberAuthor

    @mengdonglin can you please assign someone to look into this and check on the validation side? Looks like a blocking P1 to me?

  9. cujomalainey commented on Nov 1, 2018

    @cujomalainey

    @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.

  10. added
    P1Blocker bugs or important features
    on Nov 2, 2018
  11. markyang commented on Nov 2, 2018

    @markyang

    Summary:
    This issue cannot be reproduced using the mixer configuration as follows:
    pin5-port0 : cvt2
    pin6-port0 : cvt3
    pin7-port0 : cvt4

    Test Steps:

    1. aplay -Dhw:0,2 -r 48000 -c 2 -f s16_le -i -vv ~/Music/18_WAV_48000Hz_stereo_16bit.wav

    Test env:
    sof master: 43da169
    sof tool: 937032f
    kernel sof-dev: a5ddc3d
    tplg: sof-apl-pcm512x.tplg-937032f

  12. juimonen commented on Nov 2, 2018

    @juimonen

    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

  13. plbossart commented on Nov 6, 2018

    @plbossart
    MemberAuthor

    I think it's a topology issue, all the HDAudio streams have the left channel muted:

    numid=21,iface=MIXER,name='PGA1.0 Master Playback Volume 1'
      ; type=INTEGER,access=rw---R--,values=2,min=0,max=32,step=0
      : values=32,32
      | dBscale-min=-64.00dB,step=2.00dB,mute=1
    root@ubilinux4:~# amixer -Dhw:0 cset numid=22
    numid=22,iface=MIXER,name='PGA2.0 Master Playback Volume 2'
      ; type=INTEGER,access=rw---R--,values=2,min=0,max=32,step=0
      : values=0,32
      | dBscale-min=-64.00dB,step=2.00dB,mute=1
    root@ubilinux4:~# amixer -Dhw:0 cset numid=23
    numid=23,iface=MIXER,name='PGA3.0 Master Playback Volume 3'
      ; type=INTEGER,access=rw---R--,values=2,min=0,max=32,step=0
      : values=0,32
      | dBscale-min=-64.00dB,step=2.00dB,mute=1
    root@ubilinux4:~# amixer -Dhw:0 cset numid=24
    numid=24,iface=MIXER,name='PGA4.0 Master Playback Volume 4'
      ; type=INTEGER,access=rw---R--,values=2,min=0,max=32,step=0
      : values=0,32
      | dBscale-min=-64.00dB,step=2.00dB,mute=1
    

    I absolutely didn't make this selection so it's coming from the topology or the driver. @ranj063 does this ring a bell?

  14. 4 remaining items

  15. juimonen commented on Nov 8, 2018

    @juimonen

    @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).

  16. juimonen commented on Nov 8, 2018

    @juimonen

    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

  17. lgirdwood commented on Nov 8, 2018

    @lgirdwood
    Member

    @juimonen ok, looks like bug in volume.c

  18. juimonen commented on Nov 8, 2018

    @juimonen

    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.

  19. juimonen commented on Nov 8, 2018

    @juimonen

    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).

  20. juimonen commented on Nov 8, 2018

    @juimonen

    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.

  21. juimonen commented on Nov 8, 2018

    @juimonen
  22. plbossart commented on Nov 8, 2018

    @plbossart
    MemberAuthor

    @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!

  23. plbossart commented on Nov 12, 2018

    @plbossart
    MemberAuthor

    closed with PR258

  24. added a commit that references this issue on May 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

APLApplies to ApolloLake platformP1Blocker bugs or important featuresbugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions