较USB和LCD,输入子系统相对要难一些,重在理解。
一、输入子系统的结构流程(之后再详细介绍)
首先必须知道内核中有很多事件处理器(evdev, keyboard, ts 等等),且每个处理器下的handler会放入list_head这个链表。
input_subsystem总体流程如下:
(1) 注册设备register_input_device:该函数会在list_head链表中查找与input_dev匹配的handler(可能会成功匹配多个handler,后文详细介绍实现过程),匹配成功就会建立相关联系。
(2) 用户通过cat /dev/event*等连续不间断的访问上报数据存放的缓冲区,直到有内容就读取(后文详细介绍实现过程)
(3) 上报事件input_event:该函数会依据device和handler匹配成功建立的相关联系,将得到的数据上报到一个用户可以直接访问的环形缓冲区(循环队列),数据将在缓冲区内供用户将访问。
二、输入子系统的结构详细介绍:
驱动一开始会input_register_device,里边会去找与input_dev相匹配的input_handler,在事先了解几个结构体是必须的。
input_dev 结构体如下:(其中缩进的很重要、很常用)
[csharp] view plain copy print?
- struct input_dev {
- const char *name; //名称
- const char *phys; //设备在系统中的物理路径
- const char *uniq; //设备唯一识别符
- struct input_id id; //设备ID,包含总线ID(PCI、USB)、厂商ID,与input_handler匹配的时会用到
- <span style="color:#cc33cc;"> //在input.h中定义了不同的宏,表示不同的意义
- unsigned long evbit[BITS_TO_LONGS(EV_CNT)]; //支持的所有事件类型
- unsigned long keybit[BITS_TO_LONGS(KEY_CNT)]; //支持的键盘事件
- unsigned long relbit[BITS_TO_LONGS(REL_CNT)]; //支持的鼠标相对值事件
- unsigned long absbit[BITS_TO_LONGS(ABS_CNT)]; //支持的鼠标绝对值事件
- unsigned long mscbit[BITS_TO_LONGS(MSC_CNT)]; //支持的其它事件类型
- unsigned long ledbit[BITS_TO_LONGS(LED_CNT)]; //支持的LED灯事件
- unsigned long sndbit[BITS_TO_LONGS(SND_CNT)]; //支持的声效事件
- unsigned long ffbit[BITS_TO_LONGS(FF_CNT)]; //支持的力反馈事件
- unsigned long swbit[BITS_TO_LONGS(SW_CNT)]; //支持的开关事件 </span>
- unsigned int keycodemax; //keycode表的大小
- unsigned int keycodesize; //keycode表中元素个数
- void *keycode; //设备的键盘表
- int (*setkeycode)(struct input_dev *dev, int scancode, int keycode);//配置keycode表
- int (*getkeycode)(struct input_dev *dev, int scancode, int *keycode);//获取keycode表
- unsigned int repeat_key;//保存上一个键值
- struct timer_list timer;
- int sync;
- int abs[ABS_MAX + 1]; //绝对坐标上报的当前值
- int rep[REP_MAX + 1]; //这个参数主要是处理重复按键,后面讲
- unsigned long key[BITS_TO_LONGS(KEY_CNT)]; //按键有两种状态,按下和抬起,这个字段就是记录这两个状态。
- unsigned long led[BITS_TO_LONGS(LED_CNT)];
- unsigned long snd[BITS_TO_LONGS(SND_CNT)];
- unsigned long sw[BITS_TO_LONGS(SW_CNT)];
- int absmax[ABS_MAX + 1]; //绝对坐标的最大值
- int absmin[ABS_MAX + 1]; //绝对坐标的最小值
- int absfuzz[ABS_MAX + 1];
- int absflat[ABS_MAX + 1];
- //操作接口
- int (*open)(struct input_dev *dev);
- void (*close)(struct input_dev *dev);
- int (*flush)(struct input_dev *dev, struct file *file);
- int (*event)(struct input_dev *dev, unsigned int type, unsigned int code, int value);
- struct input_handle *grab; //当前使用的handle
- struct device dev;
- struct list_head h_list; //h_list是一个链表头,用来把handle挂载在这个上
- struct list_head node; //这个node是用来连到input_dev_list上的
- };
input_handler结构如下:
[csharp] view plain copy print?
- struct input_handler {
- void *private;
- void (*event)(struct input_handle *handle, unsigned int type, unsigned int code, int value);
- int (*connect)(struct input_handler *handler, struct input_dev *dev, const struct input_device_id *id);
- void (*disconnect)(struct input_handle *handle);
- void (*start)(struct input_handle *handle);
- const struct file_operations *fops;
- int minor; //每个处理器(evdev\keyboard..)都有自己的handler,对应不同的次设备号,input_open_file依
- 据此设备号找到对应的handler
- const char *name;
- const struct input_device_id *id_table; //每个处理器都有自己的id_table,处理器据此与input_dev中的
- input_id匹配,匹配成功的处理器会与该dev建立联系
- const struct input_device_id *blacklist;
- struct list_head h_list; //h_list是一个链表头,用来把handle挂载在这个上
- struct list_head node; //这个node是用来连到input_handler_list上的
- };
了解了这两个结构体后,看input_register_device函数的完成过程,这个函数从名字上看注册一个设备,意思就是让我们写的驱动程序能被操作系统识别,所以这个函数一定能够和那8个input_handler中某个创建联系:
[csharp] view plain copy print?
- int input_register_device(struct input_dev *dev)
- {
- static atomic_t input_no = ATOMIC_INIT(0);
- struct input_handler *handler;
- const char *path;
- int error;
- __set_bit(EV_SYN, dev->evbit);
- /*
- * If delay and period are pre-set by the driver, then autorepeating
- * is handled by the driver itself and we don't do it in input.c.
- */
- init_timer(&dev->timer);
- /*
- *rep主要是处理重复按键,如果没有定义dev->rep[REP_DELAY]和dev->rep[REP_PERIOD],
- *则将其赋值为默认值。dev->rep[REP_DELAY]是指第一次按下多久算一次,这里是250ms,
- *dev->rep[REP_PERIOD]指如果按键没有被抬起,每33ms算一次。
- */
- if (!dev->rep[REP_DELAY] && !dev->rep[REP_PERIOD]) {
- dev->timer.data = (long) dev;
- dev->timer.function = input_repeat_key;
- dev->rep[REP_DELAY] = 250;
- dev->rep[REP_PERIOD] = 33;
- }
- /*如果dev没有定义getkeycode和setkeycode,则赋默认值。他们的作用一个是获得键的扫描码,一个是设置键的扫描码*/
- if (!dev->getkeycode)
- dev->getkeycode = input_default_getkeycode;
- if (!dev->setkeycode)
- dev->setkeycode = input_default_setkeycode;
- dev_set_name(&dev->dev, "input%ld",
- (unsigned long) atomic_inc_return(&input_no) - 1);
- /*将input_dev封装的dev注册到sysfs*/
- error = device_add(&dev->dev);
- if (error)
- return error;
- path = kobject_get_path(&dev->dev.kobj, GFP_KERNEL);
- printk(KERN_INFO "input: %s as %s/n",
- dev->name ? dev->name : "Unspecified device", path ? path : "N/A");
- kfree(path);
- error = mutex_lock_interruptible(&input_mutex);
- if (error) {
- device_del(&dev->dev);
- return error;
- }
- /*将input_dev挂在input_dev_list上*/
- list_add_tail(&dev->node, &input_dev_list);
- /*这个函数网上都说很简单,但我还是没看懂,只知道它是个for循环,猜测循环是为了遍历8个handler*/
- list_for_each_entry(handler, &input_handler_list, node)
- /*通过其中的match函数遍历每个handler的id,如果成功匹配就调用该handler下的connect函数*/
- input_attach_handler(dev, handler); //这两个函数就是遍历所有handler,找到能和id匹配的handler
- input_wakeup_procfs_readers();
- mutex_unlock(&input_mutex);
- return 0;
- }
该函数主要是通过input_attach_handler()函数来匹配input_dev和input_handle并建立联系
input_dev与input_handler的匹配由input_attach_handler决定,所以继续跟踪input_attach_handler:
[csharp] view plain copy print?
- static int input_attach_handler(struct input_dev *dev, struct input_handler *handler)
- {
- const struct input_device_id *id;
- int error;
- /*handler有一个黑名单,如果存在黑名单,并且这个id匹配就退出*/
- if (handler->blacklist && input_match_device(handler->blacklist, dev))
- return -ENODEV;
- /*匹配id,判断某handler下的id是否与dev相匹配,若匹配就将此handler和dev通过connect建立联系*/
- id = input_match_device(handler->id_table, dev);
- if (!id)
- return -ENODEV;
- /*如果匹配,则调用具体的handler的connect函数*/
- error = handler->connect(handler, dev, id);
- if (error && error != -ENODEV)
- printk(KERN_ERR
- "input: failed to attach handler %s to device %s, "
- "error: %d/n",
- handler->name, kobject_name(&dev->dev.kobj), error);
- return error;
- }
如果匹配成功将会调用响应handler的connect函数(handler->connect),下面看能否匹配成功。
能否匹配成功由的input_match_device决定,依据handler->id_table和dev,若handler->id和input_dev匹配,表示dev由能匹配handler来处理:
[csharp] view plain copy print?
- static const struct input_device_id *input_match_device(const struct input_device_id *id,
- struct input_dev *dev)
- {
- int i;
- for (; id->flags || id->driver_info; id++) {
- if (id->flags & INPUT_DEVICE_ID_MATCH_BUS)
- if (id->bustype != dev->id.bustype)
- continue;
- if (id->flags & INPUT_DEVICE_ID_MATCH_VENDOR)
- if (id->vendor != dev->id.vendor)
- continue;
- if (id->flags & INPUT_DEVICE_ID_MATCH_PRODUCT)
- if (id->product != dev->id.product)
- continue;
- if (id->flags & INPUT_DEVICE_ID_MATCH_VERSION)
- if (id->version != dev->id.version)
- continue;
- MATCH_BIT(evbit, EV_MAX);
- MATCH_BIT(keybit, KEY_MAX);
- MATCH_BIT(relbit, REL_MAX);
- MATCH_BIT(absbit, ABS_MAX);
- MATCH_BIT(mscbit, MSC_MAX);
- MATCH_BIT(ledbit, LED_MAX);
- MATCH_BIT(sndbit, SND_MAX);
- MATCH_BIT(ffbit, FF_MAX);
- MATCH_BIT(swbit, SW_MAX);
- return id;
- }
- return NULL;
- }
dev和handler在input_match_device中匹配,可能与多个handler匹配成功,与下文中input_event可能打开多个hanle相对应。如果匹配成功input_attach_handler调用connect函数。值得注意的是不管是dev匹配handler还是handler匹配dev都是可以一对多的,比如:
Ubuntu中,/dev/input/event3 和 /dev/input/mouse1 都是对应鼠标这个设备。
connect函数将会创建一个evdev结构体,该结构体中有一个handle结构体成员。
evdev_connect:
[csharp] view plain copy print?
- /*
- * Create new evdev device. Note that input core serializes calls
- * to connect and disconnect so we don't need to lock evdev_table here.
- */
- static int evdev_connect(struct input_handler *handler, struct input_dev *dev,
- const struct input_device_id *id)
- {
- struct evdev *evdev;
- int minor;
- int error;
- /*evdev_table是evdev结构体指针数组,最大值32
- *下边的for循环,在evdev_table数组中找一个未使用的地方
- */
- for (minor = 0; minor < EVDEV_MINORS; minor++)
- if (!evdev_table[minor])
- break;
- if (minor == EVDEV_MINORS) {
- printk(KERN_ERR "evdev: no more free evdev devices/n");
- return -ENFILE;
- }
- /*下边的代码是为每一个匹配的设备分配一个evdev结构体,并对成员进行初始化*/
- evdev = kzalloc(sizeof(struct evdev), GFP_KERNEL);
- if (!evdev)
- return -ENOMEM;
- INIT_LIST_HEAD(&evdev->client_list);
- spin_lock_init(&evdev->client_lock);
- mutex_init(&evdev->mutex);
- init_waitqueue_head(&evdev->wait);
- snprintf(evdev->name, sizeof(evdev->name), "event%d", minor);
- evdev->exist = 1;
- evdev->minor = minor;
- evdev->handle.dev = input_get_device(dev);
- evdev->handle.name = evdev->name;
- evdev->handle.handler = handler;
- evdev->handle.private = evdev;
- dev_set_name(&evdev->dev, evdev->name);
- evdev->dev.devt = MKDEV(INPUT_MAJOR, EVDEV_MINOR_BASE + minor);
- evdev->dev.class = &input_class;
- evdev->dev.parent = &dev->dev;
- evdev->dev.release = evdev_free;
- /**/
- device_initialize(&evdev->dev);
- /*
- *input_register_handle完成的主要功能是:
- *list_add_tail_rcu(&handle->d_node, &dev->h_list);
- *list_add_tail(&handle->h_node, &handler->h_list);
- */
- error = input_register_handle(&evdev->handle);
- if (error)
- goto err_free_evdev;
- /*evdev_install_chrdev完成的功能是evdev_table[evdev->minor]=evdev;*/
- error = evdev_install_chrdev(evdev);
- if (error)
- goto err_unregister_handle;
- error = device_add(&evdev->dev); /*添加字符设备节点*/
- if (error)
- goto err_cleanup_evdev;
- return 0;
- }
input_register_handle 函数将input_dev和input_handler的链表存放到handle结构体,这俩链表让handle成为了input_dev和input_handler的联系。
int input_register_handle(struct input_handle *handle)
{
struct input_handler *handler = handle->handler;
list_add_tail(&handle->d_node, &handle->dev->h_list);
list_add_tail(&handle->h_node, &handler->h_list);
if (handler->start)
handler->start(handle);
return 0;
}
以上是dev通过input_register_device如何匹配到对应handler,然后如何建立连接的过程。
这里要明白一对应关系:1个上报事--- 1个evdev --- 1个handle---1个/dev/event*( * 表示0~256的数字) ,下面有幅图说明以上过程后相关结构体之间的关系:
下面讲解如何利用handle这个链接来上报事件input_event:
[csharp] view plain copy print?
- void input_event(struct input_dev *dev,
- unsigned int type, unsigned int code, int value)
- {
- unsigned long flags;
- if (is_event_supported(type, dev->evbit, EV_MAX)) {
- spin_lock_irqsave(&dev->event_lock, flags);
- add_input_randomness(type, code, value);
- input_handle_event(dev, type, code, value);
- spin_unlock_irqrestore(&dev->event_lock, flags);
- }
- }
该函数主要通过input_handle_event上报
input_handle_event函数:
[csharp] view plain copy print?
- static void input_handle_event(struct input_dev *dev,
- unsigned int type, unsigned int code, int value)
- {
- int disposition = INPUT_IGNORE_EVENT;
- switch (type) {
- 。。。。。。。。。。。。。。。。
- //将忽略事件
- if (disposition != INPUT_IGNORE_EVENT && type != EV_SYN)
- dev->sync = 0;
- //将会把事件传递给input_dev
- if ((disposition & INPUT_PASS_TO_DEVICE) && dev->event)
- dev->event(dev, type, code, value);
- //将会把事件传递给input_handler
- if (disposition & INPUT_PASS_TO_HANDLERS)
- input_pass_event(dev, type, code, value);
- }
将事件传递给input_handler的函数为input_pass_event:
[csharp] view plain copy print?
- static void input_pass_event(struct input_dev *dev, unsigned int type, unsigned int code, int value)
- {
- struct input_handler *handler;
- struct input_handle *handle;
- rcu_read_lock();
- handle = rcu_dereference(dev->grab);
- //如果是绑定的handle,则调用绑定的handler->event函数
- if (handle)
- handle->handler->event(handle, type, code, value);
- else
- {
- //如果没有绑定,则遍历dev的h_list链表,寻找handle,如果handle已经打开,说明有进程读取设备关联的evdev。
- bool filtered = false;
- list_for_each_entry_rcu(handle, &dev->h_list, d_node)
- {
- if (!handle->open) //依据open的值判断handle是否被打开,同一事件可能会适用多个handler
- continue;
- handler = handle->handler;
- if (!handler->filter)
- {
- if (filtered)
- break;
- // 调用相关的事件处理器的event函数,进行事件的处理
- handler->event(handle, type, code, value);
- }
- else if(handler->filter(handle, type, code, value))
- filtered = true;
- }
- }
- rcu_read_unlock();
- }
input_pass_event利用之前建立的联系"handle",利用handle结构体中open的数值找到input_dev对应的handler(open的值在用户打开文件部分会
变化,后边详解),调用handler的event函数。
调用到某处理器(evdev. keyboard...)的handler-->event,那么这个event做了什么?
下边以evdev中的event为例:
[csharp] view plain copy print?
- static void evdev_event(struct input_handle *handle,
- unsigned int type, unsigned int code, int value)
- {
- struct evdev *evdev = handle->private;
- struct evdev_client *client;
- struct input_event event;
- do_gettimeofday(&event.time);
- event.type = type;
- event.code = code;
- event.value = value;
- //将传过来的事件,赋值给input_event结构
- rcu_read_lock();
- client = rcu_dereference(evdev->grab);
- //如果evdev绑定了client那么,处理这个客户端,触摸屏驱动没有绑定
- if (client)
- evdev_pass_event(client, &event);
- else
- //遍历client链表,调用evdev_pass_event函数
- list_for_each_entry_rcu(client, &evdev->client_list, node)
- evdev_pass_event(client, &event);
- rcu_read_unlock();
- wake_up_interruptible(&evdev->wait); //唤醒等待的进程
- }
该函数主要作用就是将上报事件的数据放到input_event[]等待用户读取。
上报事件结束。
如果数据已经准备到位,那么用户是怎么得到呢?
很明显用户首先得打开文件,所以调用input_open_file再调用其中的ofps-> evdev_open
input_open_file:
[csharp] view plain copy print?
- static int input_open_file(struct inode *inode, struct file *file)
- {
- struct input_handler *handler;
- const struct file_operations *old_fops, *new_fops = NULL;
- int err;
- lock_kernel();
- /* No load-on-demand here? */
- /*因为 >>5 表示除上32*/
- handler = input_table[iminor(inode) >> 5]; //根据次设备号找到对应的handler,然后就利用该handler
- if (!handler || !(new_fops = fops_get(handler->fops))) {
- err = -ENODEV;
- goto out;
- }
- /*
- * That's _really_ odd. Usually NULL ->open means "nothing special",
- * not "no device". Oh, well...
- */
- if (!new_fops->open) {
- fops_put(new_fops);
- err = -ENODEV;
- goto out;
- }
- /*保存以前的fops,使用相应的handler的fops*/
- old_fops = file->f_op;
- file->f_op = new_fops;
- err = new_fops->open(inode, file);
- if (err) {
- fops_put(file->f_op);
- file->f_op = fops_get(old_fops);
- }
- fops_put(old_fops);
- out:
- unlock_kernel();
- return err;
- }
input_table[]大小为8,用来存放事件处理器的handler,内核最多支持256个事件,那么1个handler最多支持256/8=32个事件
该函数是通过次设备号为input_table[]下标索引找到对应的handler,每个处理器在register_handler时是以次设备号为索引将handler放入input_table[]中,handler中fops里边有读、写、释放等等。
继续调用fops中的evdev_open函数:
[csharp] view plain copy print?
- static int evdev_open(struct inode *inode, struct file *file)
- {
- struct evdev *evdev;
- struct evdev_client *client;
- /*因为次设备号是从EVDEV_MINOR_BASE开始的*/
- int i = iminor(inode) - EVDEV_MINOR_BASE;
- int error;
- if (i >= EVDEV_MINORS)
- return -ENODEV;
- error = mutex_lock_interruptible(&evdev_table_mutex);
- if (error)
- return error;
- /*evdev_table一共可容纳32个成员,找到次设备号对应的那个*/
- evdev = evdev_table[i];
- if (evdev)
- get_device(&evdev->dev);
- mutex_unlock(&evdev_table_mutex);
- if (!evdev)
- return -ENODEV;
- /*打开的时候创建一个client*/
- client = kzalloc(sizeof(struct evdev_client), GFP_KERNEL);
- if (!client) {
- error = -ENOMEM;
- goto err_put_evdev;
- }
- spin_lock_init(&client->buffer_lock);
- /*下边两句的作用就是将evdev和client绑定到一起*/
- client->evdev = evdev;
- evdev_attach_client(evdev, client);
- error = evdev_open_device(evdev);
- if (error)
- goto err_free_client;
- /*将file->private_data指向刚刚建的client,后边会用到的*/
- file->private_data = client;
- return 0;
- err_free_client:
- evdev_detach_client(evdev, client);
- kfree(client);
- err_put_evdev:
- put_device(&evdev->dev);
- return error;
- }
该函数将存放数据的数组input_event[]和evdev绑定了起来,后边的读函数会用到
在evdev_open最终会调用带到input_open_device:
[csharp] view plain copy print?
- int input_open_device(struct input_handle *handle)
- {
- struct input_dev *dev = handle->dev;
- int retval;
- retval = mutex_lock_interruptible(&dev->mutex);
- if (retval)
- return retval;
- if (dev->going_away) {
- retval = -ENODEV;
- goto out;
- }
- handle->open++;
- if (!dev->users++ && dev->open)
- retval = dev->open(dev);
- if (retval) {
- dev->users--;
- if (!--handle->open) {
- /*
- * Make sure we are not delivering any more events
- * through this handle
- */
- synchronize_rcu();
- }
- }
- out:
- mutex_unlock(&dev->mutex);
- return retval;
- }
这里可以看到上报上来的数据了:
[csharp] view plain copy print?
- static ssize_t evdev_read(struct file *file, char __user *buffer,
- size_t count, loff_t *ppos)
- {
- /*这个就是刚才在open函数中*/
- struct evdev_client *client = file->private_data;
- struct evdev *evdev = client->evdev;
- struct input_event event;
- int retval;
- if (count < input_event_size())
- return -EINVAL;
- /*如果client的环形缓冲区中没有数据并且是非阻塞的,那么返回-EAGAIN,也就是try again*/
- if (client->head == client->tail && evdev->exist &&
- (file->f_flags & O_NONBLOCK))
- return -EAGAIN;
- /*如果没有数据,并且是阻塞的,则在等待队列上等待吧*/
- retval = wait_event_interruptible(evdev->wait,
- client->head != client->tail || !evdev->exist);
- if (retval)
- return retval;
- if (!evdev->exist)
- return -ENODEV;
- /*如果获得了数据则取出来,调用evdev_fetch_next_event*/
- while (retval + input_event_size() <= count &&
- evdev_fetch_next_event(client, &event)) {
- /*input_event_to_user调用copy_to_user传入用户程序中,这样读取完成*/
- if (input_event_to_user(buffer + retval, &event))
- return -EFAULT;
- retval += input_event_size();
- }
- return retval;
- }
[csharp] view plain copy print?
- static int evdev_fetch_next_event(struct evdev_client *client,
- struct input_event *event)
- {
- int have_event;
- spin_lock_irq(&client->buffer_lock);
- /*先判断一下是否有数据*/
- have_event = client->head != client->tail;
- /*如果有就从环形缓冲区的取出来,记得是从head存储,tail取出*/
- if (have_event) {
- *event = client->buffer[client->tail++];
- client->tail &= EVDEV_BUFFER_SIZE - 1;
- }
- spin_unlock_irq(&client->buffer_lock);
- return have_event;
- }
[csharp] view plain copy print?
- int input_event_to_user(char __user *buffer,
- const struct input_event *event)
- {
- /*如果设置了标志INPUT_COMPAT_TEST就将事件event包装成结构体compat_event*/
- if (INPUT_COMPAT_TEST) {
- struct input_event_compat compat_event;
- compat_event.time.tv_sec = event->time.tv_sec;
- compat_event.time.tv_usec = event->time.tv_usec;
- compat_event.type = event->type;
- compat_event.code = event->code;
- compat_event.value = event->value;
- /*将包装成的compat_event拷贝到用户空间*/
- if (copy_to_user(buffer, &compat_event,
- sizeof(struct input_event_compat)))
- return -EFAULT;
- } else {
- /*否则,将event拷贝到用户空间*/
- if (copy_to_user(buffer, event, sizeof(struct input_event)))
- return -EFAULT;
- }
- return 0;
- }
后边的读函数未做详细介绍,内容主要是把input_event的数据读取给用户
本文参考了两篇博文,都非常好:
linux input 子系统分析: 点击打开链接
输入子系统架构分析: 点击打开链接