Bug 93571 - bytt100_rt5640 bytt100_rt5640: devm_snd_soc_register_card failed -517
Summary: bytt100_rt5640 bytt100_rt5640: devm_snd_soc_register_card failed -517
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Sound(ALSA) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Jaroslav Kysela
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-20 19:49 UTC by fritsch
Modified: 2016-11-29 18:48 UTC (History)
5 users (show)

See Also:
Kernel Version: 3.19
Subsystem:
Regression: No
Bisected commit-id:


Attachments
dmesg of running kernel (59.05 KB, text/plain)
2015-02-20 19:49 UTC, fritsch
Details
dmidecode output (11.22 KB, text/plain)
2015-02-20 19:50 UTC, fritsch
Details
output of lspci (2.13 KB, text/plain)
2015-02-20 19:51 UTC, fritsch
Details
DSDT (60.61 KB, application/octet-stream)
2015-03-05 18:46 UTC, fritsch
Details
Kernel Config (113.20 KB, text/plain)
2015-03-05 18:47 UTC, fritsch
Details
dsdt dumps done with acpidump -b (27.81 KB, application/octet-stream)
2015-03-05 18:51 UTC, fritsch
Details
Full kernel log (with patches, workarounds applied) (49.80 KB, text/plain)
2015-03-22 08:33 UTC, fritsch
Details

Description fritsch 2015-02-20 19:49:49 UTC
Created attachment 167761 [details]
dmesg of running kernel

Audio on Z3736F is not detected. Kernel tells:

bytt100_rt5640 bytt100_rt5640: devm_snd_soc_register_card failed -517

on boot. No audio devices are detected.
Comment 1 fritsch 2015-02-20 19:50:20 UTC
Created attachment 167771 [details]
dmidecode output
Comment 2 fritsch 2015-02-20 19:51:09 UTC
Created attachment 167781 [details]
output of lspci
Comment 3 Jarkko Nikula 2015-03-05 09:17:37 UTC
I forward this to guys who have been doing the bytcr_dpcm_rt5640.c and sound/soc/intel/sst driver stack. In the meanwhile could you attach here your kernel config and DSDT table from /sys/firmware/acpi/tables/DSDT?
Comment 4 fritsch 2015-03-05 18:46:51 UTC
Created attachment 169321 [details]
DSDT
Comment 5 fritsch 2015-03-05 18:47:23 UTC
Created attachment 169331 [details]
Kernel Config
Comment 6 fritsch 2015-03-05 18:51:47 UTC
Created attachment 169341 [details]
dsdt dumps done with acpidump -b
Comment 7 fritsch 2015-03-19 18:26:46 UTC
Is there anything missing from my side? Something I can provide to ease development?

Best Regards
Peter
Comment 8 Jarkko Nikula 2015-03-20 09:28:56 UTC
No info from driver authors but I checked your DSDT dump and it shares some similar findings than the bug https://bugzilla.kernel.org/show_bug.cgi?id=86581

For instance DSP host interrupt is defined in another index than code in existing drivers.

Your kernel config seems to miss needed drivers. I guess you accidentally included a wrong one? Anyway, could you try experimenting with the following configuration and with one hack patch from above bug how far you go with the audio?

CONFIG_I2C_DESIGNWARE_CORE=m
CONFIG_I2C_DESIGNWARE_PLATFORM=m
CONFIG_I2C_DESIGNWARE_PCI=m

CONFIG_SND_SOC=m
CONFIG_SND_SOC_INTEL_SST=m
CONFIG_SND_SOC_INTEL_SST_ACPI=m
CONFIG_SND_SOC_INTEL_BAYTRAIL=m
CONFIG_SND_SOC_INTEL_BYT_RT5640_MACH=m
and following not set
# CONFIG_SND_SOC_INTEL_BYTCR_RT5640_MACH is not set

"Hack patch that takes DSP-host interrupt from another index":
https://bugzilla.kernel.org/attachment.cgi?id=155341

However I fear they don't make the audio working since if I read correctly the Z3736F is a low-pin count variant that has 2 SSP ports instead of 3. Currently both firmware variants in linux-firmware.git are hard coded for 3rd SSP2 port :-(
Comment 9 fritsch 2015-03-22 08:32:41 UTC
Thanks for your reply.

Here is what I get:

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: bytrt5640 [byt-rt5640], device 0: Audio rt5640-aif1-0 []
  Subdevices: 1/1
  Subdevice #0: subdevice #0

Kernel:
[    5.208591] baytrail-pcm-audio baytrail-pcm-audio: error: invalid DMA engine 0
[    5.208600] baytrail-pcm-audio baytrail-pcm-audio: sst_dma_new failed -22
[    5.215702] usb 1-2.3: reset high-speed USB device number 4 using xhci_hcd
[    5.243662] baytrail-pcm-audio baytrail-pcm-audio: FW version: 04.05.13.a0
[    5.243671] baytrail-pcm-audio baytrail-pcm-audio: Build type: a0
[    5.243676] baytrail-pcm-audio baytrail-pcm-audio: Build date: Apr  2 2014 14:14:39
[    5.256685] byt-rt5640 byt-rt5640: rt5640-aif1 <-> baytrail-pcm-audio mapping ok
[    5.309091] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007ae01b00
[    5.309099] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007ae01b48
[    5.309105] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff88007ae01b90

Complete log is attached
Comment 10 fritsch 2015-03-22 08:33:34 UTC
Created attachment 171631 [details]
Full kernel log (with patches, workarounds applied)
Comment 11 fritsch 2015-03-22 08:34:56 UTC
Nearly forgot the important part: As you told before: No audio coming out at all. I also did only find that Analog Audio output, no separate HDMI device was shown.
Comment 12 Pierre Bossart 2016-11-29 18:48:14 UTC
try with a more recent kernel, this is solved

Note You need to log in before you can comment on or make changes to this bug.