element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Community Hub
    Community Hub
    • What's New on element14
    • Feedback and Support
    • Benefits of Membership
    • Personal Blogs
    • Members Area
    • Achievement Levels
  • Learn
    Learn
    • Ask an Expert
    • eBooks
    • element14 presents
    • Learning Center
    • Tech Spotlight
    • STEM Academy
    • Webinars, Training and Events
    • Learning Groups
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • Technology Groups
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents Projects
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • Project Groups
  • Products
    Products
    • Arduino
    • Avnet & Tria Boards Community
    • Dev Tools
    • Manufacturers
    • Multicomp Pro
    • Product Groups
    • Raspberry Pi
    • RoadTests & Reviews
  • About Us
  • Store
    Store
    • Visit Your Store
    • Choose another store...
      • Europe
      •  Austria (German)
      •  Belgium (Dutch, French)
      •  Bulgaria (Bulgarian)
      •  Czech Republic (Czech)
      •  Denmark (Danish)
      •  Estonia (Estonian)
      •  Finland (Finnish)
      •  France (French)
      •  Germany (German)
      •  Hungary (Hungarian)
      •  Ireland
      •  Israel
      •  Italy (Italian)
      •  Latvia (Latvian)
      •  
      •  Lithuania (Lithuanian)
      •  Netherlands (Dutch)
      •  Norway (Norwegian)
      •  Poland (Polish)
      •  Portugal (Portuguese)
      •  Romania (Romanian)
      •  Russia (Russian)
      •  Slovakia (Slovak)
      •  Slovenia (Slovenian)
      •  Spain (Spanish)
      •  Sweden (Swedish)
      •  Switzerland(German, French)
      •  Turkey (Turkish)
      •  United Kingdom
      • Asia Pacific
      •  Australia
      •  China
      •  Hong Kong
      •  India
      • Japan
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • Vietnam
      • Americas
      •  Brazil (Portuguese)
      •  Canada
      •  Mexico (Spanish)
      •  United States
      Can't find the country/region you're looking for? Visit our export site or find a local distributor.
  • Translate
  • Profile
  • Settings
Raspberry Pi
  • Products
  • More
Raspberry Pi
Raspberry Pi Forum Driver fixes and updates to kernel 3.18.16 and 4.0.5
  • Blog
  • Forum
  • Documents
  • Quiz
  • Events
  • Polls
  • Files
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Join Raspberry Pi to participate - click to join for free!
Featured Articles
Announcing Pi
Technical Specifications
Raspberry Pi FAQs
Win a Pi
Raspberry Pi Wishlist
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 180 replies
  • Subscribers 689 subscribers
  • Views 23096 views
  • Users 0 members are here
  • raspberry_pi
  • raspeberry_pi_accessories
Related

Driver fixes and updates to kernel 3.18.16 and 4.0.5

hiassoft
hiassoft over 10 years ago

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

  • Sign in to reply
  • Cancel
Parents
  • Former Member
    Former Member over 10 years ago

    Hias,

     

    Thanks for your hard work producing these kernel patches. Any chance of a precompiled 4.1.7 kernel?


    Paul

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hiassoft
    hiassoft over 10 years ago in reply to Former Member

    Thanks for your hard work producing these kernel patches. Any chance of a precompiled 4.1.7 kernel?

    Here's a precompiled tarball of the current 4.1.12 kernel:

    http://www.horus.com/~hias/tmp/cirrus/cirrus-linux-4.1.12.tgz

     

    @Ed: thanks a lot for the Arch pkgbuild, that's really cool!

     

    so long,

     

    Hias

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    Hi HiassofT,

     

    thanks for your great work.

     

    I unpacked your newest Kernel-package in the root directory. Modified the two files but can't find the soundcard via aplay -l

    Do you have any idear what I could have done wrong?

     

    my edited files:

     

    /etc/modprobe.d/cirrus.conf

     

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

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

    blacklist snd_bcm2835

     

    /boot/config.txt

     

    dtoverlay=rpi-cirrus-wm5102-overlay
    dtoverlay=i2s-mmap

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hiassoft
    hiassoft over 10 years ago in reply to Former Member

    Hi Jonas & Esmi!

     

    Could you please do the following:

    • add dtdebug=1 to config.txt
    • reboot the pi
    • then post the outputs of vcdbg log msg and dmesg

     

    BTW: The easiest way to post the log outputs is by installing the pastebinit package in Raspbian (apt-get install pastebinit). Then enter the following commands and just post the URLs you got from pastebinit

    vcdbg log msg 2>&1 | pastebinit
    dmesg | pastebinit

     

    Also: have you tried the previous 4.1.12 version, did that work for you?

     

    so long,

     

    Hias

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to hiassoft

    Hi Matthias,

     

    thanks for your response. I will do that today evening. I'm know following a lead, that my noobs-installer could be the cause of the problem....could that be?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    Ok, here are the logs

     

    vcdbg log msg:

     

    paste.debian.net/336029

     

    001453.656: Failed to load overlay 'rpi-cirrus-wm5102-overlay'

     

    dmesg:

     

    paste.debian.net/336030

     

     

     

    regarding NOOBS: I mounted mmcblk0p5 to copy the new kernel bootfiles in it (as I read in a nother board) - but they seem to be the same content as root/boot

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hiassoft
    hiassoft over 10 years ago in reply to Former Member

    Esmi Schildburg wrote:

     

    thanks for your response. I will do that today evening. I'm know following a lead, that my noobs-installer could be the cause of the problem....could that be?

    I'm not familiar with noobs, but it could be - for example if you edited config.txt on the wrong partition. So I wouldn't rule that out as a possibility.

     

    A simple way to check if the dtoverlay was loaded is to look at the files in /proc/device-tree/sound/ .

     

    If the overlay is loaded you should have a file named "compatible" there with the contents "wlf,rpi-wm5102". You also should have a file "status" with contents "okay" and a file "i2s-controller".

     

    If these files are missing, something went wrong with the dtoverlay or the overlay files. The "vcdbg log msg" output should reveal the details. Ah, BTW, since you are using noobs you might have to add the "dtdebug=1" to the noobs config.txt file on the primary partition - but I'm not sure about that.

     

    so long,

     

    Hias

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hiassoft
    hiassoft over 10 years ago in reply to Former Member
    Ok, here are the logs

    Thanks! It looks like not only it didn't find the overlay but also booted an old kernel (4.1.7 instead of 4.1.13).

     

    So quite certainly the files the boot/* files in the tarball (kernel and overlay) ended up on the wrong partition.

    regarding NOOBS: I mounted mmcblk0p5 to copy the new kernel bootfiles in it (as I read in a nother board) - but they seem to be the same content as root/boot

    Hmmm... Sorry, can't help with that. I'm a total noob regarding NOOBS image

     

    so long,

     

    Hias

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to hiassoft

    okay, thank you - so the /boot - / NOOBS - thing seems to be the problem

     

    At the moment I am short on SD-Cards - I will try it with an raspbian image without noobs next week

     

    But thanks for your insight!

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to Former Member

    okay - solved^^

     

    I doublechecked - and well.... it seems I didn't really extract the tgz file - I just unpacked in in a tar file - so there was indeed no new kernel image

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • hiassoft
    hiassoft over 10 years ago in reply to Former Member

    Esmi Schildburg wrote:

     

    okay - solved^^

     

    I doublechecked - and well.... it seems I didn't really extract the tgz file - I just unpacked in in a tar file - so there was indeed no new kernel

    Cool, glad you got it working!

     

    Did you have to do anything special regarding NOOBS?

     

    so long,

     

    Hias

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Former Member
    Former Member over 10 years ago in reply to hiassoft

    Since someone asked if the provided compiled kernel can be used with Arch Linux: I was able to use the provided 4.1.13 kernel without any problems on my Arch Linux based Runeaudio installation.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Former Member
    Former Member over 10 years ago in reply to hiassoft

    Since someone asked if the provided compiled kernel can be used with Arch Linux: I was able to use the provided 4.1.13 kernel without any problems on my Arch Linux based Runeaudio installation.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
No Data
element14 Community

element14 is the first online community specifically for engineers. Connect with your peers and get expert answers to your questions.

  • Members
  • Learn
  • Technologies
  • Challenges & Projects
  • Products
  • Store
  • About Us
  • Feedback & Support
  • FAQs
  • Terms of Use
  • Privacy Policy
  • Legal and Copyright Notices
  • Sitemap
  • Cookies

An Avnet Company © 2026 Premier Farnell Limited. All Rights Reserved.

Premier Farnell Ltd, registered in England and Wales (no 00876412), registered office: Farnell House, Forge Lane, Leeds LS12 2NE.

ICP 备案号 10220084.

Follow element14

  • X
  • Facebook
  • linkedin
  • YouTube