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 23016 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

  • Hi Matthias (and all),

     

    I currently set up my Raspberry 2 + Cirrus/Wolfson card with the latest kernel (4.1.13) and the drivers updated from this thread. Being happy, everything works image. Just thought to share some feedback, mainly small notes.

     

    On the configuration, several people are talking about updating the raspi-blacklist.conf, while you are referring to /etc/modprobe.d/cirrus.conf. I wondered a bit at the difference (their content is the same), then chose to have the lines in raspi-blacklist.conf. Does it matter, and can somebody explain the difference? As I know, raspi-blacklist.conf is a list of modules what the kernel is instructed to avoid. Will do the same for cirrus.conf?

     

    Another small note is that after made the setup, aplay -l reports 2 audio cards, the bcm2835 ALSA being listed first. (so I have card 1: sndrpiwsp). Although I set up pcm.!default and ctl.!default in .asoundrc to card 1, I wonder if there is a way to disable the bcm2835 card completely from boot, so that apps would find sndrpiwsp by default. Thanks.

     

    Otherwise the card works beautifully so far. Many thanks!

     

    Zsolt

Reply

  • Hi Matthias (and all),

     

    I currently set up my Raspberry 2 + Cirrus/Wolfson card with the latest kernel (4.1.13) and the drivers updated from this thread. Being happy, everything works image. Just thought to share some feedback, mainly small notes.

     

    On the configuration, several people are talking about updating the raspi-blacklist.conf, while you are referring to /etc/modprobe.d/cirrus.conf. I wondered a bit at the difference (their content is the same), then chose to have the lines in raspi-blacklist.conf. Does it matter, and can somebody explain the difference? As I know, raspi-blacklist.conf is a list of modules what the kernel is instructed to avoid. Will do the same for cirrus.conf?

     

    Another small note is that after made the setup, aplay -l reports 2 audio cards, the bcm2835 ALSA being listed first. (so I have card 1: sndrpiwsp). Although I set up pcm.!default and ctl.!default in .asoundrc to card 1, I wonder if there is a way to disable the bcm2835 card completely from boot, so that apps would find sndrpiwsp by default. Thanks.

     

    Otherwise the card works beautifully so far. Many thanks!

     

    Zsolt

Children
  • in reply to gkzsolt

    Hi Zsolt!

    On the configuration, several people are talking about updating the raspi-blacklist.conf, while you are referring to /etc/modprobe.d/cirrus.conf. I wondered a bit at the difference (their content is the same), then chose to have the lines in raspi-blacklist.conf. Does it matter, and can somebody explain the difference? As I know, raspi-blacklist.conf is a list of modules what the kernel is instructed to avoid. Will do the same for cirrus.conf?

    Concerning functionality it doesn't matter to which file you add the lines, all files in /etc/modprobe.d (that end with .conf) are read in and merged together.

     

    But it's good practice to put separate configurations in separate files and use filenames that reflect the type of configuration - so it's easier to find them again later.

     

    My guess is that Cirrus used the raspi-blacklist.conf file because it was already there, but personally I prefer to have this config in cirrus.conf - this filename tells me that it'll contain the config of the Cirrus card.

    Another small note is that after made the setup, aplay -l reports 2 audio cards, the bcm2835 ALSA being listed first. (so I have card 1: sndrpiwsp). Although I set up pcm.!default and ctl.!default in .asoundrc to card 1, I wonder if there is a way to disable the bcm2835 card completely from boot, so that apps would find sndrpiwsp by default. Thanks.

    Yes, that's possible, and I've disabled snd-bcm2835 here, too.

     

    snd-bcm2835 can be enabled in 2 different ways, be sure to check for both and disable them:

    • by a snd-bcm2835 line in /etc/modules
    • by dtparam=audio=on in /boot/config.txt

     

    Either comment out or delete these lines, then bcm2835 ALSA will be gone.

     

    so long,

     

    Hias