Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Linux Device Driver Development

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

Arrow left icon
Product type Paperback
Published in Jan 2021
Publisher Packt
ISBN-13 9781789342048
Length 646 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
John Madieu John Madieu
Author Profile Icon John Madieu
John Madieu
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

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

Video device opening and property management

Drivers expose node entries in the /dev/ directory corresponding to the video interfaces they are responsible for. These file nodes correspond to the /dev/videoX special files for capture devices (in our case). The application must open the appropriate file node prior to any interaction with the video device. It uses the open() system call for that, which will return a file descriptor that will be the entry point for any command sent to the device, as in the following example:

static const char *dev_name = "/dev/video0";
fd = open (dev_name, O_RDWR);
if (fd == -1) {
    perror("Failed to open capture device\n");
    return -1;
}

The preceding snippet is an opening in blocking mode. Passing O_NONBLOCK to open() would prevent the application from being blocked if there is no ready buffer while trying to dequeue. Once you're done with the video device, it should be closed...

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 $19.99/month. Cancel anytime
Banner background image