Linux Device Driver Development
John Madieu
- 708 pages
- English
- ePUB (mobile friendly)
- Available on iOS & Android
Linux Device Driver Development
John Madieu
About This Book
Get up to speed with the most important concepts in driver development and focus on common embedded system requirements such as memory management, interrupt management, and locking mechanismsKey Features• Write feature-rich and customized Linux device drivers for any character, SPI, and I2C device• Develop a deep understanding of locking primitives, IRQ management, memory management, DMA, and so on• Gain practical experience in the embedded side of Linux using GPIO, IIO, and input subsystemsBook DescriptionLinux is by far the most-used kernel on embedded systems. Thanks to its subsystems, the Linux kernel supports almost all of the application fields in the industrial world. This updated second edition of Linux Device Driver Development is a comprehensive introduction to the Linux kernel world and the different subsystems that it is made of, and will be useful for embedded developers from any discipline.You'll learn how to configure, tailor, and build the Linux kernel. Filled with real-world examples, the book covers each of the most-used subsystems in the embedded domains such as GPIO, direct memory access, interrupt management, and I2C/SPI device drivers. This book will show you how Linux abstracts each device from a hardware point of view and how a device is bound to its driver(s). You'll also see how interrupts are propagated in the system as the book covers the interrupt processing mechanisms in-depth and describes every kernel structure and API involved. This new edition also addresses how not to write device drivers using user space libraries for GPIO clients, I2C, and SPI drivers.By the end of this Linux book, you'll be able to write device drivers for most of the embedded devices out there. What you will learn• Download, configure, build, and tailor the Linux kernel• Describe the hardware using a device tree• Write feature-rich platform drivers and leverage I2C and SPI buses• Get the most out of the new concurrency managed workqueue infrastructure• Understand the Linux kernel timekeeping mechanism and use time-related APIs• Use the regmap framework to factor the code and make it generic• Offload CPU for memory copies using DMA• Interact with the real world using GPIO, IIO, and input subsystemsWho this book is forThis Linux OS book is for embedded system and embedded Linux enthusiasts/developers who want to get started with Linux kernel development and leverage its subsystems. Electronic hackers and hobbyists interested in Linux kernel development as well as anyone looking to interact with the platform using GPIO, IIO, and input subsystems will also find this book useful.
Frequently asked questions
Information
Section 1 -Linux Kernel Development Basics
- Chapter 1, Introduction to Kernel Development
- Chapter 2, Understanding Linux Kernel Module Basic Concepts
- Chapter 3, Dealing with Kernel Core Helpers
- Chapter 4, Writing Character Device Drivers
Chapter 1: Introduction to Kernel Development
- Setting up the development environment
- Understanding the kernel configuration process
- Building your kernel
Setting up the development environment
- Target: This is the machine that the binaries resulting from the build process are produced for. This is the machine that is going to run the binary.
- Host: This is the machine where the build process takes place.
- Compilation: This is also called native compilation or a native build. This happens when the target and the host are the same; that is, when you're building on machine A (the host) a binary that is going to be executed on the same machine (A, the target) or a machine of the same kind. Native compilation requires a native compiler. Therefore, a native compiler is one where the target and the host are the same.
- Cross-compilation: Here, the target and the host are different. It is where you build a binary from machine A (the host) that is going to be executed on machine B (the target). In this case, the host (machine A) must have installed the cross-compiler that supports the target architecture. Thus, a cross-compiler is a compiler where the target is different from the host.