You're reading from Mastering Linux Device Driver Development

Product type Book

Published in Jan 2021

Publisher Packt

ISBN-13 9781789342048

Pages 646 pages

Edition 1st Edition

Languages

Concepts

Embedded Systems

Author (1):

John Madieu

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

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

Understanding the Linux kernel release process

According to the Linux kernel release model, there are always three types of active kernel release: mainline, the stable release, and the Long-Term Support (LTS) release. First, bug fixes and new features are gathered and prepared by subsystem maintainers and then submitted to Linus Torvalds in order for him to include them in his own Linux tree, which is called the mainline Linux tree, also known as the master Git repository. This is where every stable release originates from.

Before each new kernel version is released, it is submitted to the community through release candidate tags, so that developers can test and polish all the new features and, most importantly, share feedback. During this cycle, Linus will rely on the feedback in order to decide whether the final version is ready to be released. When he is convinced that the new kernel is ready to go, he makes (tags it actually) the final release, and we call this release stable...