element14 Community
element14 Community
    Register Log In
  • Site
  • Search
  • Log In Register
  • Members
    Members
    • Benefits of Membership
    • Achievement Levels
    • Members Area
    • Personal Blogs
    • Feedback and Support
    • What's New on element14
  • Learn
    Learn
    • Learning Center
    • eBooks
    • STEM Academy
    • Webinars, Training and Events
    • More
  • Technologies
    Technologies
    • 3D Printing
    • FPGA
    • Industrial Automation
    • Internet of Things
    • Power & Energy
    • Sensors
    • More
  • Challenges & Projects
    Challenges & Projects
    • Design Challenges
    • element14 presents
    • Project14
    • Arduino Projects
    • Raspberry Pi Projects
    • More
  • Products
    Products
    • Arduino
    • Dev Tools
    • Manufacturers
    • Raspberry Pi
    • RoadTests & Reviews
    • Avnet Boards Community
    • More
  • 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
      •  Korea (Korean)
      •  Malaysia
      •  New Zealand
      •  Philippines
      •  Singapore
      •  Taiwan
      •  Thailand (Thai)
      • 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
Raspberry Pi
  • Products
  • More
Raspberry Pi
Forum Driver fixes and updates to kernel 3.18.16 and 4.0.5
  • Blog
  • Forum
  • Documents
  • Events
  • Members
  • Mentions
  • Sub-Groups
  • Tags
  • More
  • Cancel
  • New
Raspberry Pi requires membership for participation - click to join
Actions
  • Share
  • More
  • Cancel
Forum Thread Details
  • Replies 180 replies
  • Subscribers 148 subscribers
  • Views 3443 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 6 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

  • Reply
  • Cancel
  • Cancel

Top Replies

  • hiassoft
    hiassoft over 5 years ago in reply to Former Member +3

    I just had a look at volumio 2 (RC2 hotfix):

     

    It's setup is a quite different to Raspbian, it uses an initrd which sets up squashfs+overlayfs for the root partition. If you update the kernel, the modules…

  • hiassoft
    hiassoft over 6 years ago +2

    I've uploaded a new kernel build, based upon 4.1.19:

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

     

    I finally found out what was causing the issues on the new RPi3 (other soundcards where…

  • markzed
    markzed over 6 years ago +1

    Thanks a bunch for doing this. For those of us who are really noobs (like me) here are detailed instructions.

     

    For 3.18.16

     

    • Get the 3.18.16 raspbian image. I used the Raspbian image provided by Raspberry Pi…
Parents
  • Former Member
    Former Member over 6 years ago

    Hias,

     

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


    Paul

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
  • hiassoft
    hiassoft over 6 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
    • Up 0 Down
    • Reply
    • Cancel
  • Former Member
    Former Member over 6 years ago in reply to hiassoft

    Many thanks, that's awesome, that will fix lots of things for me and no doubt others too - Paul

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
  • Former Member
    Former Member over 6 years ago in reply to Former Member

    Does anyone habe a compiled Version for Kernel 4.0.13?

     

    I've tryed it on Jessie and Wheezy with my Pi2, the Cirrus Logic Audio card and the official 7" Touch Screen. The Cirrus won't work und the worst thing, even the Touchscreen won't recognize touch anymore after the procedure.

     

    Or do I have a missunderstanding. Compile a new kernel means that the drivers for the cirrus are add to the existing/installed kernel?

     

    After installing Jessie I was on Kernel 4.0.7 for what no compiled kernel for the Cirrus was uploaded. Because of that I made an update und voila 4.0.13

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
Reply
  • Former Member
    Former Member over 6 years ago in reply to Former Member

    Does anyone habe a compiled Version for Kernel 4.0.13?

     

    I've tryed it on Jessie and Wheezy with my Pi2, the Cirrus Logic Audio card and the official 7" Touch Screen. The Cirrus won't work und the worst thing, even the Touchscreen won't recognize touch anymore after the procedure.

     

    Or do I have a missunderstanding. Compile a new kernel means that the drivers for the cirrus are add to the existing/installed kernel?

     

    After installing Jessie I was on Kernel 4.0.7 for what no compiled kernel for the Cirrus was uploaded. Because of that I made an update und voila 4.0.13

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
Children
  • hiassoft
    hiassoft over 6 years ago in reply to Former Member

    Does anyone habe a compiled Version for Kernel 4.0.13?

    Do you mean 4.1.13? I'll upload one shortly.

    I've tryed it on Jessie and Wheezy with my Pi2, the Cirrus Logic Audio card and the official 7" Touch Screen. The Cirrus won't work und the worst thing, even the Touchscreen won't recognize touch anymore after the procedure.

     

    Or do I have a missunderstanding. Compile a new kernel means that the drivers for the cirrus are add to the existing/installed kernel?

     

    After installing Jessie I was on Kernel 4.0.7 for what no compiled kernel for the Cirrus was uploaded. Because of that I made an update und voila 4.0.13

    What exactly did you do? Did you compile a kernel yourself, if yes which kernel sources did you use?

     

    I'm not familiar with the touchscreen, but I'd suggest you first try to get the touchscreen working with the official RPi kernel and once you are there try getting the the Cirrus card working, too.

     

    BTW: If you download the kernel with the Cirrus driver from my github repository and compile it yourself, or if you just install the precompiled cirrus kernel, you are replacing the whole kernel and all drivers with the new version.

     

    In my precompiled kernels I use the exact same kernel config options as the official kernel plus the Cirrus specific options added to that. So basically it should behave like an official kernel with the Cirrus drivers added, but still there's some risk that one of the Cirrus specific options causes issues with other drivers.

     

    so long,

     

    Hias

    • Cancel
    • Up 0 Down
    • Reply
    • Cancel
Element14

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 © 2022 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

  • Facebook
  • Twitter
  • linkedin
  • YouTube