You're reading from Mastering Linux Device Driver Development Write custom device drivers to support computer peripherals in Linux operating systems

Product type Paperback

Published in Jan 2021

Publisher Packt

ISBN-13 9781789342048

Length 646 pages

Edition 1st Edition

Languages

C++

Tools

Linux

Concepts

Embedded Systems

Author (1):

John Madieu

View More author details

Table of Contents (19) Chapters

Preface

1. Section 1:Kernel Core Frameworks for Embedded Device Driver Development

2. Chapter 1: Linux Kernel Concepts for Embedded Developers FREE CHAPTER

3. Chapter 2: Leveraging the Regmap API and Simplifying the Code

4. Chapter 3: Delving into the MFD Subsystem and Syscon API

5. Chapter 4: Storming the Common Clock Framework

6. Section 2: Multimedia and Power Saving in Embedded Linux Systems

7. Chapter 5: ALSA SoC Framework – Leveraging Codec and Platform Class Drivers

8. Chapter 6: ALSA SoC Framework – Delving into the Machine Class Drivers

9. Chapter 7: Demystifying V4L2 and Video Capture Device Drivers

10. Chapter 8: Integrating with V4L2 Async and Media Controller Frameworks

11. Chapter 9:Leveraging the V4L2 API from the User Space

12. Chapter 10: Linux Kernel Power Management

13. Section 3: Staying Up to Date with Other Linux Kernel Subsystems

14. Chapter 11: Writing PCI Device Drivers

15. Chapter 12: Leveraging the NVMEM Framework

16. Chapter 13: Watchdog Device Drivers

17. Chapter 14: Linux Kernel Debugging Tips and Best Practices

18. Other Books You May Enjoy

Leave a review - let other readers know what you think

Writing codec class drivers

In order to be coupled together, machine, platform, and codec entities need dedicated drivers. The codec class driver is the most basic. It implements code that should leverage the codec device and expose its hardware properties so that user space tools such as amixer can play with it. The codec class driver is and should be platform-independent. The same codec driver can be used whatever the platform. Since it targets a specific codec, it should contain audio controls, audio interface capabilities, a codec DAPM definition, and I/O functions. Each codec driver must fulfill the following specifications:

Provide an interface to other modules by defining DAI and PCM configurations.
Provide codec control IO hooks (using I2C or SPI or both APIs).
Expose additional kcontrols (kernel controls) as needed for userspace utilities to dynamically control module behavior.
Optionally, define DAPM widgets and establish DAPM routes for dynamic power...