Skip to content

[Bug][SDW][CML_2 RTC1308] Paplay via speaker only has Left Channel Output. #1564

Closed

Description

@ClarexZhou

Describe the bug
Paplay via speaker only has Left Channel Output. Because Paplay is using device 2: SDW1-speakers.
And device 2: SDW1-speakers is using Left channel. device 3: SDW2-speakers is using Right Channel.

UCM is using one 1308 UCM https://github.com/thesofproject/alsa-ucm-conf/tree/master/ucm/sof-sdw-rt711-1308-715 commit: 39528c5

To Reproduce

  1. Do system reboot via "sudo reboot"
  2. Run ./rt1308_mixer.sh to setup amixer setting for speaker
    rt1308_mixer.txt
  3. Open Setting->Sound, select Speaker as Output Source.
  4. paplay 48California_Dreaming.wav -vvv

Reproduce Rate
100%

Actual result
Only Left channel has output. Paplay is using device 2: SDW1-speakers.
And device 2: SDW1-speakers is using Left channel. device 3: SDW2-speakers is using Right

ubuntu@ubuntu-XPS-17-9700-02:~$ paplay 48California_Dreaming.wav -vvv
Opening a playback stream with sample specification 's16le 2ch 48000Hz' and channel map 'front-left,front-right'.
Connection established.
Stream successfully created.
Buffer metrics: maxlength=4194304, tlength=384000, prebuf=380164, minreq=3840
Using sample spec 's16le 2ch 48000Hz', channel map 'front-left,front-right'.
Connected to device alsa_output.pci-0000_00_1f.3-platform-sdw_rt711_rt1308_rt715.HiFi__hw_sofsdwrt7111308_2__sink (index: 4, suspended: no).
Stream started.

Expected result
Both L and R channel should have output when paplay via speaker.

Environment
Firmware: decd206 cml-009-drop-stable
Kernel: d6078f9 on integration/soundwire-latest
Kernel config: Run https://github.com/thesofproject/kconfig/blob/master/kconfig-sof-default.sh
Topology: Same with FW branch, sof-cml-rt711-rt1308-rt715.tplg
platform: CML Laptop with codec ALC711, 2 x RT1308, RT715 in SDW mode
UCM: https://github.com/thesofproject/alsa-ucm-conf/tree/master/ucm/sof-sdw-rt711-1308-715 commit: 39528c5

logger.txt
dmesg.txt

Activity

  1. added
    bugSomething isn't working
    CMLApplies to Comet Lake platform
    SDWApplies to SoundWire bus for codec connection
    on Nov 29, 2019
  2. ClarexZhou commented on Nov 29, 2019

    @ClarexZhou
    Author

    use UCM https://github.com/bardliao/alsa-ucm-conf/tree/separate-speakers/ucm/sof-sdw-rt711-1308-715 And PR #1567
    2 RTC1308 Speaker are listed separately in sound setting. As below snapshot.
    Is it expected? Or should list one speaker and output on both 2 RTC1308 at same time?
    image

  3. bardliao commented on Dec 2, 2019

    @bardliao
    Collaborator

    use UCM https://github.com/bardliao/alsa-ucm-conf/tree/separate-speakers/ucm/sof-sdw-rt711-1308-715 And PR #1567
    2 RTC1308 Speaker are listed separately in sound setting. As below snapshot.
    Is it expected? Or should list one speaker and output on both 2 RTC1308 at same time?
    image

    @ClarexZhou It is expected for now. The two rt1308 are on different sdw link. Use multi-codecs in a dai link is a new feature on Soundwire and we will implement it soon.

  4. mengdonglin commented on Jan 6, 2020

    @mengdonglin

    Depend on the new feature of synchronized playbackm #1644 is to address the feature in driver and WIP

  5. bardliao commented on Jan 15, 2020

    @bardliao
    Collaborator

    FW change is also required for the issue. A WIP PR is thesofproject/sof#2258

  6. sinahuang commented on Apr 29, 2020

    @sinahuang

    Issue can't be seen with sof-dev(commit:8f1c6ad) +PR #2058 (note :PR2058 is for other blocked issue #2031) and master (commit:af38b20b), closed it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    CMLApplies to Comet Lake platformSDWApplies to SoundWire bus for codec connectionSynchronized PlaybackApplies to synchronized playback over multiple backend linksbugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions