Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Save more on your purchases!
Savings automatically calculated. No voucher code required
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Mastering Linux Device Driver Development

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
Author (1):
John Madieu John Madieu
Profile icon 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

The watchdog user space interface

On Linux-based systems, the standard user space interface to the watchdog is the /dev/watchdog file, through which a daemon will notify the kernel watchdog driver that the user space is still alive. The watchdog starts right after the file is opened, and gets pinged by periodically writing into this file.

When the notification occurs, the underlying driver will notify the watchdog device, which will result in resetting its timeout; the watchdog will then wait for yet another timeout duration prior to resetting the system. However, if for any reason the user space does not perform the notification before the timeout is elapsed, the watchdog will reset the system (causing a reboot). This mechanism provides a way to enforce the system availability. Let's start with the basics, learning how to start and stop the watchdog.

Starting and stopping the watchdog

The watchdog is automatically started once you open the /dev/watchdog device file,...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $15.99/month. Cancel anytime}