Sensor在内核中的驱动框架【转】
本文转载自:http://blog.csdn.net/armfpga123/article/details/52840370
模块初始化函数:
- static int __init sensors_init(void)
- {
- sensors_class = class_create(THIS_MODULE, "sensors");
- if (IS_ERR(sensors_class))
- return PTR_ERR(sensors_class);
- sensors_class->dev_attrs = sensors_class_attrs;
- return 0;
- }
创建sensor的类class,通过sensors_class->dev_attrs = sensors_class_attrs;在sysfs文件系统下面创建设备节点,上层调用读写函数往文件节点读写数据时,相应的show和store函数就会被调用。sensors_class_attrs的定义如下:
- static struct device_attribute sensors_class_attrs[] = {
- __ATTR(name, 0444, sensors_name_show, NULL),
- __ATTR(vendor, 0444, sensors_vendor_show, NULL),
- __ATTR(version, 0444, sensors_version_show, NULL),
- __ATTR(handle, 0444, sensors_handle_show, NULL),
- __ATTR(type, 0444, sensors_type_show, NULL),
- __ATTR(max_range, 0444, sensors_max_range_show, NULL),
- __ATTR(resolution, 0444, sensors_resolution_show, NULL),
- __ATTR(sensor_power, 0444, sensors_power_show, NULL),
- __ATTR(min_delay, 0444, sensors_min_delay_show, NULL),
- __ATTR(fifo_reserved_event_count, 0444, sensors_fifo_event_show, NULL),
- __ATTR(fifo_max_event_count, 0444, sensors_fifo_max_show, NULL),
- __ATTR(max_delay, 0444, sensors_max_delay_show, NULL),
- __ATTR(flags, 0444, sensors_flags_show, NULL),
- __ATTR(enable, 0664, sensors_enable_show, sensors_enable_store),
- __ATTR(enable_wakeup, 0664, sensors_enable_wakeup_show,
- sensors_enable_wakeup_store),
- __ATTR(poll_delay, 0664, sensors_delay_show, sensors_delay_store),
- __ATTR(self_test, 0440, sensors_test_show, NULL),
- __ATTR(max_latency, 0660, sensors_max_latency_show,
- sensors_max_latency_store),
- __ATTR(flush, 0660, sensors_flush_show, sensors_flush_store),
- __ATTR(calibrate, 0664, sensors_calibrate_show,
- sensors_calibrate_store),
- __ATTR_NULL,
- };
具体的sensor驱动程序会调用sensors_classdev_register函数注册自己,以地磁传感器mmc3524为例,在驱动的proble函数中,有如下代码:
- memsic->cdev = sensors_cdev;
- memsic->cdev.sensors_enable = mmc3524x_set_enable;
- memsic->cdev.sensors_poll_delay = mmc3524x_set_poll_delay;
- res = sensors_classdev_register(&memsic->idev->dev, &memsic->cdev);
mmc3524的数据结构如下,里面有个struct sensors_classdev cdev;成员,上面的代码设置cdev的enable和poll_delay函数指针指向驱动程序的函数,供sensor的HAL层调用。
- struct mmc3524x_data {
- struct mutex ecompass_lock;
- struct mutex ops_lock;
- struct workqueue_struct *data_wq;
- struct delayed_work dwork;
- struct sensors_classdev cdev;
- struct mmc3524x_vec last;
- struct i2c_client *i2c;
- struct input_dev *idev;
- struct regulator *vdd;
- struct regulator *vio;
- struct regmap *regmap;
- int dir;
- int auto_report;
- int enable;
- int poll_interval;
- int power_enabled;
- unsigned long timeout;
sensors_classdev_register函数是sensor的核心,该函数根据之前创建的sensors_class,在类下面创建设备,前面调用sensors_classdev_register(&memsic->idev->dev, &memsic->cdev);时,将memsic->cdev成员的地址作为device_create函数的第四个参数传入,然后将sensors_cdev放入sensors_list链表。
- int sensors_classdev_register(struct device *parent,
- struct sensors_classdev *sensors_cdev)
- {
- sensors_cdev->dev = device_create(sensors_class, parent, 0,
- sensors_cdev, "%s", sensors_cdev->name);
- if (IS_ERR(sensors_cdev->dev))
- return PTR_ERR(sensors_cdev->dev);
- down_write(&sensors_list_lock);
- list_add_tail(&sensors_cdev->node, &sensors_list);
- up_write(&sensors_list_lock);
- pr_debug("Registered sensors device: %s\n",
- sensors_cdev->name);
- return 0;
- }
在device_create函数中,调用device_create_vargs将之前传入的&memsic->cdev传入device_create_vargs函数中。
- struct device *device_create(struct classclass *class, struct device *parent,
- dev_t devt, voidvoid *drvdata, const charchar *fmt, ...)
- {
- va_list vargs;
- struct device *dev;
- va_start(vargs, fmt);
- dev = device_create_vargs(class, parent, devt, drvdata, fmt, vargs);
- va_end(vargs);
- return dev;
- }
在device_create_vargs函数中,会调用dev_set_drvdata(dev, drvdata);
- struct device *device_create_vargs(struct classclass *class, struct device *parent,
- dev_t devt, voidvoid *drvdata, const charchar *fmt,
- va_list args)
- {
- struct device *dev = NULL;
- int retval = -ENODEV;
- if (class == NULL || IS_ERR(class))
- goto error;
- dev = kzalloc(sizeof(*dev), GFP_KERNEL);
- if (!dev) {
- retval = -ENOMEM;
- goto error;
- }
- dev->devt = devt;
- dev->class = class;
- dev->parent = parent;
- dev->release = device_create_release;
- dev_set_drvdata(dev, drvdata);
- retval = kobject_set_name_vargs(&dev->kobj, fmt, args);
- if (retval)
- goto error;
- retval = device_register(dev);
- if (retval)
- goto error;
- return dev;
- error:
- put_device(dev);
- return ERR_PTR(retval);
- }dev_set_drvdata
在dev_set_drvdata函数中,会调用dev->p->driver_data = data;这样dev->p->driver_data就指向了&memsic->cdev。
- int dev_set_drvdata(struct device *dev, voidvoid *data)
- {
- int error;
- if (!dev->p) {
- error = device_private_init(dev);
- if (error)
- return error;
- }
- dev->p->driver_data = data;
- return 0;
- }
在sensors_enable_store和sensors_enable_show函数中,会调用dev_get_drvdata函数:
- static ssize_t sensors_enable_store(struct device *dev,
- struct device_attribute *attr, const charchar *buf, size_t size)
- {
- struct sensors_classdev *sensors_cdev = dev_get_drvdata(dev);
- ssize_t ret = -EINVAL;
- unsigned long data = 0;
- ret = kstrtoul(buf, 10, &data);
- if (ret)
- return ret;
- if (data > 1) {
- dev_err(dev, "Invalid value of input, input=%ld\n", data);
- return -EINVAL;
- }
- if (sensors_cdev->sensors_enable == NULL) {
- dev_err(dev, "Invalid sensor class enable handle\n");
- return -EINVAL;
- }
- ret = sensors_cdev->sensors_enable(sensors_cdev, data);
- if (ret)
- return ret;
- sensors_cdev->enabled = data;
- return size;
- }
- <pre name="code" class="objc">static ssize_t sensors_enable_show(struct device *dev,
- struct device_attribute *attr, charchar *buf)
- {
- struct sensors_classdev *sensors_cdev = dev_get_drvdata(dev);
- return snprintf(buf, PAGE_SIZE, "%u\n",
- sensors_cdev->enabled);
- }
dev_get_drvdata函数会返回之前在dev_set_drvdata函数中设置的指针dev->p->driver_data。
- voidvoid *dev_get_drvdata(const struct device *dev)
- {
- if (dev && dev->p)
- return dev->p->driver_data;
- return NULL;
- }
之前在驱动的probe函数中设置了memsic->cdev.sensors_enable = mmc3524x_set_enable;sensors_enable_store函数通过ret = sensors_cdev->sensors_enable(sensors_cdev, data);来调用驱动程序中的enable函数。HAL层会根据sensor的设备节点来找到sensor,调用enable,delay等函数来调用sensor驱动中对应的函数,本例子中对应的文件是:hardware/qcom/sensors/CompassSensor.cpp:
- int CompassSensor::enable(int32_t, int en) {
- int flags = en ? 1 : 0;
- compass_algo_args arg;
- arg.common.enable = flags;
- char propBuf[PROPERTY_VALUE_MAX];
- property_get("sensors.compass.loopback", propBuf, "0");
- if (strcmp(propBuf, "1") == 0) {
- ALOGE("sensors.compass.loopback is set");
- mEnabled = flags;
- mEnabledTime = 0;
- return 0;
- }
- if (flags != mEnabled) {
- int fd;
- if ((algo != NULL) && (algo->methods->config != NULL)) {
- if (algo->methods->config(CMD_ENABLE, (sensor_algo_args*)&arg)) {
- ALOGW("Calling enable config failed for compass");
- }
- }
- strlcpy(&input_sysfs_path[input_sysfs_path_len],
- SYSFS_ENABLE, SYSFS_MAXLEN);
- fd = open(input_sysfs_path, O_RDWR);
- if (fd >= 0) {
- char buf[2];
- int err;
- buf[1] = 0;
- if (flags) {
- buf[0] = '1';
- mEnabledTime = getTimestamp() + IGNORE_EVENT_TIME;
- } else {
- buf[0] = '0';
- }
- err = write(fd, buf, sizeof(buf));
- close(fd);
- mEnabled = flags;
- return 0;
- }
- ALOGE("CompassSensor: failed to open %s", input_sysfs_path);
- return -1;
- }
- return 0;
- }
HAL层的enable函数中,通过write系统调用来调用内核的enable函数,内核的enable函数首先会打开设备的电源,然后通过工作队列函数queue_delayed_work(memsic->data_wq,&memsic->dwork,msecs_to_jiffies(memsic->poll_interval));来调用sensor的mmc3524x_poll函数。
- static int mmc3524x_set_enable(struct sensors_classdev *sensors_cdev,
- unsigned int enable)
- {
- int rc = 0;
- struct mmc3524x_data *memsic = container_of(sensors_cdev,
- struct mmc3524x_data, cdev);
- mutex_lock(&memsic->ops_lock);
- if (enable && (!memsic->enable)) {
- rc = mmc3524x_power_set(memsic, true);
- if (rc) {
- dev_err(&memsic->i2c->dev, "Power up failed\n");
- goto exit;
- }
- /* send TM cmd before read */
- rc = regmap_write(memsic->regmap, MMC3524X_REG_CTRL,
- MMC3524X_CTRL_TM);
- if (rc) {
- dev_err(&memsic->i2c->dev, "write reg %d failed.(%d)\n",
- MMC3524X_REG_CTRL, rc);
- goto exit;
- }
- memsic->timeout = jiffies;
- if (memsic->auto_report)
- queue_delayed_work(memsic->data_wq,
- &memsic->dwork,
- msecs_to_jiffies(memsic->poll_interval));
- } else if ((!enable) && memsic->enable) {
- if (memsic->auto_report)
- cancel_delayed_work_sync(&memsic->dwork);
- if (mmc3524x_power_set(memsic, false))
- dev_warn(&memsic->i2c->dev, "Power off failed\n");
- } else {
- dev_warn(&memsic->i2c->dev,
- "ignore enable state change from %d to %d\n",
- memsic->enable, enable);
- }
- memsic->enable = enable;
- exit:
- mutex_unlock(&memsic->ops_lock);
- return rc;
mmc3524x_poll函数通过I2C接口获取数据,上报数据。
- static void mmc3524x_poll(struct work_struct *work)
- {
- int ret;
- s8 *tmp;
- struct mmc3524x_vec vec;
- struct mmc3524x_vec report;
- struct mmc3524x_data *memsic = container_of((struct delayed_work *)work,
- struct mmc3524x_data, dwork);
- ktime_t timestamp;
- vec.x = vec.y = vec.z = 0;
- ret = mmc3524x_read_xyz(memsic, &vec);
- if (ret) {
- dev_warn(&memsic->i2c->dev, "read xyz failed\n");
- goto exit;
- }
- tmp = &mmc3524x_rotation_matrix[memsic->dir][0];
- report.x = tmp[0] * vec.x + tmp[1] * vec.y + tmp[2] * vec.z;
- report.y = tmp[3] * vec.x + tmp[4] * vec.y + tmp[5] * vec.z;
- report.z = tmp[6] * vec.x + tmp[7] * vec.y + tmp[8] * vec.z;
- timestamp = ktime_get_boottime();
- input_report_abs(memsic->idev, ABS_X, report.x);
- input_report_abs(memsic->idev, ABS_Y, report.y);
- input_report_abs(memsic->idev, ABS_Z, report.z);
- input_event(memsic->idev,
- EV_SYN, SYN_TIME_SEC,
- ktime_to_timespec(timestamp).tv_sec);
- input_event(memsic->idev,
- EV_SYN, SYN_TIME_NSEC,
- ktime_to_timespec(timestamp).tv_nsec);
- input_sync(memsic->idev);
- exit:
- queue_delayed_work(memsic->data_wq,
- &memsic->dwork,
- msecs_to_jiffies(memsic->poll_interval));
- }
- 顶
- 0
Sensor在内核中的驱动框架【转】的更多相关文章
- linux 保留内核中sas驱动的加载导致crash问题
[root@localhost ~]# uname -a Linux localhost.localdomain -.el7.x86_64 问题描述,在crash的时候,小内核因为分配中断号失败而触发 ...
- linux 驱动学习笔记02--应用实例:在内核中新增驱动代码目录和子目录
下面来看一个综合实例,假设我们要在内核源代码 drivers 目录下为 ARM 体系结构新增如下用于 test driver 的树型目录:| --test | -- cpu | -- cpu.c ...
- 从串口驱动的移植看linux2.6内核中的驱动模型 platform device & platform driver【转】
转自:http://blog.csdn.net/bonnshore/article/details/7979705 写在前面的话: 博主新开了个人站点:你也可以在这里看到这篇文章,点击打开链接 本文是 ...
- linux内核中i2c驱动中slave模式接口的调用
1. 关注unreg_slave接口 1.1 这个接口在哪里被调用呢? 在drivers/i2c/i2c-core-slave.c中 int i2c_slave_unregister(struct i ...
- I2C驱动框架 (kernel-3.4.2)
先用韦老师的图: 注: 新版本内核的i2c驱动框架采用了 i2c_client -------> i2c_bus_type <-------- i2c_driver 框架 如 ...
- (转)S5pv210 HDMI 接口在 Linux 3.0.8 驱动框架解析 (By liukun321 咕唧咕唧)
作者:liukun321 咕唧咕唧 日期:2014.1.18 转载请标明作者.出处:http://blog.csdn.net/liukun321/article/details/18452663 本文 ...
- S5pv210 HDMI 接口在 Linux 3.0.8 驱动框架解析
作者:liukun321 咕唧咕唧 日期:2014.1.18 转载请标明作者.出处:http://blog.csdn.net/liukun321/article/details/18452663 本文 ...
- 驱动框架入门——以LED为例[【转】
本文转载自;http://blog.csdn.net/oqqHuTu12345678/article/details/72783903 以下内容源于朱有鹏<物联网大讲堂>课程的学习,如有侵 ...
- linux设备驱动程序--串行通信驱动框架分析
linux 串行通信接口驱动框架 在学习linux内核驱动时,不论是看linux相关的书籍,又或者是直接看linux的源码,总是能在linux中看到各种各样的框架,linux内核极其庞杂,linux各 ...
随机推荐
- java使用Callable创建又返回值的线程
并发编程使我们可以将程序分为很多个分离的,相互之间独立的任务,通过使用多线程的机制,将每个任务都会有一个执行线程来单独的驱动,一个线程是 进程中一个单一顺序控制流,一个进程可以拥有多个线程,也就相当于 ...
- IA-32 Assembly Language Reference Manual
Load Full Pointer (lds,les, lfs, lgs, and lss) lds{wl} mem[32|48], reg[16|32]les{wl} mem[32|48], reg ...
- c#获取网络时间
public static DateTime GetInternetDate() { var client = new TcpClient("time.n ...
- 工具使用——VMware安装及使用
一.VMware的安装 本文使用VMware 14 pro,双击打开安装包,点击下一步: 选中我接受许可协议中的条款,点击下一步: 选择安装路径,点击下一步: 点击下一步: 点击下一步: 点击安装: ...
- 微软宣布全新命令行+脚本工具:PowerShell 7
DOS 逐渐退出历史舞台后,Windows 一直内置着 CMD 命令行工具,并在 Windows 7 时代升级为更强悍的 PowerShell,不仅可以执行命令行,更可以执行各种高级脚本,还能跨平台. ...
- Qualcomm_Mobile_OpenCL.pdf 翻译-7 内存性能优化
内存优化是最重要也是最有效的OpenCL性能优化技术.大量的应用程序是内存限制而不是计算限制.所以,掌握内存优化的方法是OpenCL优化的基础.在这章中,将会回顾OpenCL的内存模型,然后是最优的实 ...
- mysql5.7二进制包进行多实例安装
一.需求 在一台服务器上安装mysql5.7,并且部署两个实例:3306用于本机主库,3307用于其他MYSQL服务器的从库 二.下载mysql二进制包 [root@push-- src]# -lin ...
- 将临时全局表中的符合字段导入test数据库中
--表1 开户级别表 insert into test.dbo.crm_m_cust_summary(CUST_CERT_N O,ASSETAMT_GRADE_CD)select cust_no,cu ...
- Jmeter之cookie的处理方式,token处理
cookie是什么 由于http是无状态的协议,一旦客户端和服务器的数据交换完毕,就会断开连接,再次请求,会重新连接,这就说明服务器单从网络连接上是没有办法知道用户身份的.怎么办呢?那就给每次新的用户 ...
- springboot 配置quart多数据源
Springboot版本为2.1.6 多数据源配置使用druid进行配置,数据库使用的为Oracle11g,如果使用的是MySQL,直接将数据库的地址和驱动改一下即可 <parent> & ...