Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
Forum Thread Details
  • Replies 180 replies
  • Subscribers 689 subscribers
  • Views 23024 views
  • Users 0 members are here
Related

Driver fixes and updates to kernel 3.18.16 and 4.0.5

hiassoft

Edit: Current kernel versions and install/config instructions are also available from my webpage http://www.horus.com/~hias/cirrus-driver.html

 

During the last few weeks I fixed various issues in the Wolfson/Cirrus driver and rebased it so it works with the current RPi kernel versions (3.18.16 and 4.0.5).

 

You can download the patches from my GitHub repository. The 3.18 kernel with Cirrus drivers is in the cirrus-3.18.y branch, the 4.0 kernel with Cirrus drivers is in the cirrus-4.0.y branch. I'll rebase and update these branches from time to time so that the Cirrus driver and my changes will stay on top of the commit list.

 

If you just want to have an updated 3.18.16 kernel you can download precompiled binaries from here. Just unpack the tarball in the root directory. Before you do that it might be a good idea to update the firmware files (bootcode.bin, start*.elf and fixup*.dat in the boot directory) to the latest version.

 

Here's a list of my changes:

- Added the FLL1 setup back so that switching between 44.1kHz and 48kHz (and other sample rates) works fine.

- Don't register Arizona IRQ if it's set to 0. The Cirrus driver uses polling here and if we register an interrupt handler for irq 0 we get lots of "spurious interrupt" messages spamming dmesg in kernel 3.19 and newer. IRQ 0 is wrong anyway.

- Include DCVDD patches from the Cirrus linux-drivers repository. These patches make sure the WM8804 chip is initialized properly. Without this patch I sometimes had SPDIF audio out only on the right channel.

- Disable spidev0 in Cirrus device tree overlay. That's mainly a safety precaution so that userspace programs trying to access spi0.0 won't interfere with the WM8804 reset line. I'm not 100% sure this is needed at all, so maybe I'll remove it some time later.

 

And some important notes:

I haven't included the mmap patch, this is already supported in the upstream kernels but currently disabled by default. To enable mmap support add the following line to config.txt:

dtoverlay=i2s-mmap

 

If you compile the kernel on your own please note that the devicetree overlays have now been moved to arch/arm/boot/dts/overlays.

 

Kernel 4.0 now uses spi_bcm2835 by default (the older spi_bcm2708 module is available via a devicetree overlay) so you have to extend your /etc/modprobe.d conf file and add a pre-depend for spi_bcm2835 as well. It's safe to have both the old and the new module in here, so just use this configuration:

softdep arizona-spi pre: arizona-ldo1
softdep spi-bcm2708 pre: fixed
softdep spi-bcm2835 pre: fixed

 

so long,

 

Hias

Parents

  • I am hitting a wall with my Raspberry Pi B+ and Cirrus Audio card. I'm pretty sure the card is not recognized now and/or the driver is not even loading. It was working previously on wheezy before I switched to jessie.

     

    After downloading your precompiled kernel, I installed like so:

    pi@raspberrypi ~ $ sudo tar zxf cirrus-linux-4.1.19.tgz -C /

     

    Then I updated /boot/config.txt like so:

    dtdebug=1
dtoverlay=rpi-cirrus-wm5102
dtoverlay=i2s-mmap
#dtparam=audio=on

    I know this config.txt file is correct because after commenting that last line it does indeed disable the on-board sound (see note below about aplay -l after reboot).

     

    ...and I created /etc/modprobe.d/cirrus.conf as follows:

    softdep arizona-spi pre: arizona-ldo1
softdep spi-bcm2708 pre: fixed
softdep spi-bcm2835 pre: fixed

     

    Then I rebooted, but now...

    pi@raspberrypi ~ $ aplay -l
aplay: device_list:268: no soundcards found...

     

    Here is some info about my Pi:

    pi@raspberrypi ~ $ uname -a
Linux raspberrypi 4.1.19+ #1 Fri Mar 11 15:05:42 CET 2016 armv6l GNU/Linux
pi@raspberrypi ~ $ vcgencmd version
Mar  9 2016 18:15:17
Copyright (c) 2012 Broadcom
version 3a754304b032a5298ee7889b179c667bbc75dec5 (clean) (release)

     

    I checked vcdbg log msg, but it has only this:

    debug_sym: OpenVideoCoreMemoryFileWithOffset: Unable to open '/dev/vc-mem': Permission denied(13)
Unable to open videocore memory access: -13

     

    I also checked dmesg with grep for various terms relating to the soundcard, and it appears there are no errors about it at all, so I don't know what to make of that. Here is the pastebin link. Maybe there is something else there that will shed some light on the problem.

    http://paste.debian.net/417519/

     

    Hopefully this week or next my new RPi 2 will arrive, and it will not have these problems, but until then I'd like to get the B+ working again if possible. I upgraded to jessie because I was having problems with the camera's inaccurate framerate, which made synchronizing video and audio impossible. Supposedly a firmware update fixed that framerate problem, but of course I'll need the Cirrus working to test the new firmware.

     

     

    Additional notes:

     

    I also tried these lines in /etc/modprobe.d/cirrus.conf even though they apparently are not needed after 4.1.16, and of course they didn't help:

    softdep snd-soc-wm8804-i2c pre: snd-soc-rpi-wsp-preinit
softdep snd-soc-rpi-wsp pre: snd-soc-wm8804-i2c

     

    By the way, there is also /etc/modprobe.d/fbdevblacklist.conf with this line:

    blacklist cirrusfb

    ...so I tried commenting that line, but it does not seem to change anything.

Reply

  • I am hitting a wall with my Raspberry Pi B+ and Cirrus Audio card. I'm pretty sure the card is not recognized now and/or the driver is not even loading. It was working previously on wheezy before I switched to jessie.

     

    After downloading your precompiled kernel, I installed like so:

    pi@raspberrypi ~ $ sudo tar zxf cirrus-linux-4.1.19.tgz -C /

     

    Then I updated /boot/config.txt like so:

    dtdebug=1
dtoverlay=rpi-cirrus-wm5102
dtoverlay=i2s-mmap
#dtparam=audio=on

    I know this config.txt file is correct because after commenting that last line it does indeed disable the on-board sound (see note below about aplay -l after reboot).

     

    ...and I created /etc/modprobe.d/cirrus.conf as follows:

    softdep arizona-spi pre: arizona-ldo1
softdep spi-bcm2708 pre: fixed
softdep spi-bcm2835 pre: fixed

     

    Then I rebooted, but now...

    pi@raspberrypi ~ $ aplay -l
aplay: device_list:268: no soundcards found...

     

    Here is some info about my Pi:

    pi@raspberrypi ~ $ uname -a
Linux raspberrypi 4.1.19+ #1 Fri Mar 11 15:05:42 CET 2016 armv6l GNU/Linux
pi@raspberrypi ~ $ vcgencmd version
Mar  9 2016 18:15:17
Copyright (c) 2012 Broadcom
version 3a754304b032a5298ee7889b179c667bbc75dec5 (clean) (release)

     

    I checked vcdbg log msg, but it has only this:

    debug_sym: OpenVideoCoreMemoryFileWithOffset: Unable to open '/dev/vc-mem': Permission denied(13)
Unable to open videocore memory access: -13

     

    I also checked dmesg with grep for various terms relating to the soundcard, and it appears there are no errors about it at all, so I don't know what to make of that. Here is the pastebin link. Maybe there is something else there that will shed some light on the problem.

    http://paste.debian.net/417519/

     

    Hopefully this week or next my new RPi 2 will arrive, and it will not have these problems, but until then I'd like to get the B+ working again if possible. I upgraded to jessie because I was having problems with the camera's inaccurate framerate, which made synchronizing video and audio impossible. Supposedly a firmware update fixed that framerate problem, but of course I'll need the Cirrus working to test the new firmware.

     

     

    Additional notes:

     

    I also tried these lines in /etc/modprobe.d/cirrus.conf even though they apparently are not needed after 4.1.16, and of course they didn't help:

    softdep snd-soc-wm8804-i2c pre: snd-soc-rpi-wsp-preinit
softdep snd-soc-rpi-wsp pre: snd-soc-wm8804-i2c

     

    By the way, there is also /etc/modprobe.d/fbdevblacklist.conf with this line:

    blacklist cirrusfb

    ...so I tried commenting that line, but it does not seem to change anything.

Children