Download as PDF, PPTX
Uploaded byGary Yeh
Linux Char Device Driver
This document outlines the key components of a Linux character device driver, including modules, major and minor numbers, data structures like struct file and struct file_operations, driver registration, and core functions like open, release, read and write. It provides an introduction to character device drivers in Linux and their basic architecture.
More Related Content
Similar to Linux Char Device Driver
![Linuxdd[1]](https://cdn.slidesharecdn.com/ss_thumbnails/linuxdd1-110927015846-phpapp01-thumbnail.jpg?width=600ounds&width=560&fit=bounds)
Linux Char Device Driver
- 1. Linux Char DeviceDriver Gary 2013/03/20
- 2. Outline • Introduction • Module •Major Number and Minor Number • Data Structure • Registration • Open and Release • Read and Write • Future Work
- 3. Introduction • Device driveris a bridge between physical devices and programs, and it’s part of kernel. User program can manage physical devices via device driver. • Driver can be roughly divided into Block device driver and Character device driver. The former transfer a fixed amount of data each time, and Character device driver transfer no- fixed amount of data.
- 4.
- 5. Module Advantage: • Reduce kernelimage space • Speed up the boot time • Facilitate the development of the kernel function
- 6. Module Linking a moduleto a kernel
- 7. Major Number andMinor Number • Major number(0-255) When the kernel receives open() system call, it selects the driver based on major number. • Minor number(0-255) Identify individuals of similar devices. Meaningless to kernel. Only the driver itself knows the significance of the minor number.
- 8. Major Number andMinor Number • “c” represents special file of char driver. • “b” represents device file of block driver. Major number Minor number
- 9. Major Number andMinor Number • Use mknod command to create device node. Needs superuser priviledges and four arguments. - <name> <device type> <major> <minor> $mknod /dev/ant c 252 0 • Use rm command to delete device node. $rm /dev/ant
- 10. Data Structure • Structfile represents an opened-device. • Struct file_operations is used for kernel to access the method in driver. - defined in <linux/fs.h> • Struct file has field f_op, which is the pointer point to struct file_operations
- 11.
- 12. File_operations • struct module*owner; Not a function pointer. For kernel to maintain the usage count of module. • loff_t (*llseek) (struct file *, loff_t, int); Change the position of current file read write point.
- 13. File • The filementioned here has no concerned with the file in normal application. • For every file which is opened, there is a correspond struct file. • The pointer point to file is named filp.
- 14.
- 15. Old Registration Method •Call register_chrdev() - define in <linux/fs.h> - /usr/src/<kernel version>/include/linux/fs.h
- 16. Old Registration Method •$cat /proc/devices
- 17. New Registration Method •Kernel uses struct cdev to represent char device driver. You need to include <linux/cdev.h> • Use cdev_alloc() to configure struct cdev • If you have your own designed struct, you need to use cdev_init() Struct cdev *my_cdev = cdev_alloc(); My_cdev->ops = &my_fops; Void cdev_init(struct cdev *dev, struct file_operations *fops);
- 18. New Registration Method •No matter how to initialize struct cdev, the owner field must be set • The last step, use cdev_add() to add to kernel struct cdev my_cdev; my_cdev.owner = THIS_MODULE; int cdev_add(struct cdev *dev, dev_t num, unsigned int count); Struct cdev you set Major number Total amount of device number
- 19. New Registration Method •Destroy cdev void cdev_del(struct cdev *dev);
- 20. Open and Release •Open operation offers driver initialization, and increase usage count. • Release operation decrease usage count. - Defined in <linux/module.h>
- 21. Open • Most ofthe open operation of driver should do the following jobs. - increase usage count - check for device specific errors (ex : no CD in CD-ROM) - if the target device is opened the first time, do initializtion - Identify the minor number and update the f_op pointer - allocate and fill data structure in filp->private data
- 22. Open • The firststep of open operation is to check the target device’s minor number.
- 23. Release • Release anythingthat open operation allocate to flip->private_data. • Shut down the target device on the last close. • Decrease usage count
- 24. Read and Write •flip : file pointer • buff : argument to the buffer in user-space • count : transfer data amount • offp : the file location ssize_t read(struct file *filp, char *buff, size_t count, loff_t *offp); ssize_t write(struct file *filp, const char *buff, size_t count, loff_t *offp);
- 25. Read and Write •Data transfer between kernel space and user space. • Use the function defined in <asm/uaccess.h>
- 26. Read and Write •The arguments to read
- 27. Future Work • Readmore • Ioctl