[alsa-devel] Intel Baytrail Linux Audio

[Nicolas George]

Hi.

Tyler Yeomans:
> I was able to recompile the distribution kernel after a long wait, and with
> the changes that were made I was able to get some semblance of an audio
> device registered.
> 
> I've attached the dmesg.
> 
> $ 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
> 
> I've also attached a screenshot of what I am seeing.
> No HDMI audio though, and when I attach a headphone to the speaker jack... I
> get nothing but very faint buzzing when I put my ear to it and hit 'test
> sound'

I am trying to get a similar device working in a Lenovi Miix 3-1030
PC/tablet, with no more success.

There are three firmware files with which I try the device:

[FIRMWARE_1]
fw_sst_0f28.bin-48kHz_i2s_master from this Git repository HEAD (3161bfa):
git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
sha1 = 2ddd16db3f587584d185ab7c0e2094dfb54b3828, size = 265684

[FIRMWARE_2]
fw_sst_0f28.bin-i2s_master from this Git repository HEAD (2f11e90):
https://chromium.googlesource.com/chromiumos/third_party/linux-firmware
sha1 = 46385c87d5e4d8267007d4353f7627db9715ca3a, size = 265892

[FIRMWARE_3]
The previous revision of fw_sst_0f28.bin-i2s_master from the same Git
repository (24b6a27):
sha1 = 505561c6bba939ff8129ec26dbf82dd7cd4b9d72, size = 265556

I believe Tyler is using FIRMWARE_3.

For me, FIRMWARE_1 and FIRMWARE_2 give similar results, FIRMWARE_3 is
different.

With unpatched 4.1.1 and FIRMWARE_1 and FIRMWARE_2:

When loading snd-soc-sst-baytrail-pcm, the kernel says:

[  558.593576] (NULL device *): ipc: error DSP boot timeout

several times. "NULL device" seems worrying in the first place.

Then when loading snd-soc-sst-byt-rt5640-mach, the kernel says:

[  627.325055] byt-rt5640 byt-rt5640: ASoC: CPU DAI baytrail-pcm-audio not registered

With FIRMWARE_3, loading snd-soc-sst-baytrail-pcm causes a kernel Oops with
the following messages (amongst a lot of lines, of course):

[ 1974.297580] (NULL device *): FW version: 04.05.12.02
[ 1974.297589] (NULL device *): Build type: 2
[ 1974.297594] (NULL device *): Build date: Jul 24 2013 13:17:39
[ 1975.344179] irq 7: nobody cared (try booting with the "irqpoll" option)

After that, an entry sometimes appears in /proc/asound/cards but does not
produce any sound, and quickly starts producing errors.

The oops message led me to try changing sound/soc/intel/common/sst-acpi.c
and set sst_acpi_baytrail_desc.irqindex_host_ipc = 7.

With FIRMWARE_1 and FIRMWARE_2, the "DSP boot timeout" message disappears,
but "CPU DAI baytrail-pcm-audio not registered" is still there. And
FIRMWARE_3 starts behaving exactly the same.

I include the kernel messages for the Oops, in case some extra information
is useful. I can perform more tests as needed with various configurations
and patches.

Regards,

-- 
  Nicolas George
-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg-4.1.1-oops-sound.gz
Type: application/gzip
Size: 16426 bytes
Desc: not available
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20150702/e3d2ef0e/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20150702/e3d2ef0e/attachment-0001.sig>