【发布时间】:2015-01-07 02:41:20
【问题描述】:
在驱动程序开发方面,我对 sysfs 相当陌生,而且我似乎观察到一些相当奇怪的行为。长话短说,内核似乎没有将完整的结构传递回我的回调。该驱动程序是一个相当简单的 SPI-ADC 驱动程序,用于读取模拟热/电压数据。
现在,我很难相信自己在如此广泛使用的子系统中发现了 Linux 内核中的错误。我已经在互联网上搜索了任何可能有帮助的东西,但所有迹象都表明这应该可以正常工作。其他传递的结构似乎已正确填充,只有 attr->attr 成员似乎是 NULL。
我还要提一下,这是针对 3.2 内核的。
那么,简而言之,什么会导致 sysfs 回调没有收到完全填充的 kobj_attribute 结构?
示例代码:
static ssize_t ads7960_sysfs_show(struct kobject *kobj, struct kobj_attribute *attr, char *buf)
{
int var, rc, i = 0, j = 0;
long channel = 0;
//DEBUG
printk("%s: kobj->name = %s\n", __func__, kobj->name);
printk("%s: attr = %p\n", __func__, attr);
printk("%s: attr->attr = %p\n", __func__, attr->attr);
printk("%s: attr->attr.name = %s\n", __func__, attr->attr.name);
printk("%s: attr->attr.mode = %o\n", __func__, attr->attr.mode);
/* check for silly things */
if ((attr->attr.name == NULL) || (strlen(attr->attr.name) < 1)) {
printk("%s: invalid channel number. = %s\n", __func__, attr->attr.name);
return -EINVAL;
}
... snip (We never get past here) ...
static struct kobj_attribute ads7960_ch0 = __ATTR(0, 0444, ads7960_sysfs_show, NULL);
static struct kobj_attribute ads7960_ch1 = __ATTR(1, 0444, ads7960_sysfs_show, NULL);
static struct kobj_attribute ads7960_ch2 = __ATTR(2, 0444, ads7960_sysfs_show, NULL);
... snip (there are 12 total ADC channels in the same format) ...
static struct attribute *ch_attrs[] = {
&ads7960_ch0.attr,
&ads7960_ch1.attr,
&ads7960_ch2.attr,
... snip (same 12 channels as above)...
NULL,
};
static struct attribute_group attr_group = {
.attrs = ch_attrs,
};
static struct attribute_group *attr_group_ptr = &attr_group;
... snip ...
static struct spi_driver ads7960_driver = {
.driver = {
.name = "ads7960",
.bus = &spi_bus_type,
.owner = THIS_MODULE,
.groups = &attr_group_ptr,
},
.probe = ads7960_probe,
.remove = __devexit_p(ads7960_remove),
.id_table = ads7960_id,
};
... snip ...
产生的输出:
[root@172.17.152.42: ]# cat /sys/bus/spi/drivers/ads7960/4
[ 65.344789] ads7960_sysfs_show: kobj->name = ads7960
[ 65.350026] ads7960_sysfs_show: attr = dc934000
[ 65.354859] ads7960_sysfs_show: attr->attr = (null)
[ 65.360155] ads7960_sysfs_show: attr->attr.name = (null)
[ 65.365746] ads7960_sysfs_show: attr->attr.mode = 0
[ 65.370861] ads7960_sysfs_show: invalid channel number. = (null)
cat: read error: Invalid argument
参考文献
http://www.cs.fsu.edu/~baker/devices/lxr/http/source/linux/samples/kobject/kobject-example.c http://kroah.com/log/blog/2013/06/26/how-to-create-a-sysfs-file-correctly/
编辑 1:
总结下面的 cmets,我从 _init 手动调用了 sysfs_create_group,并且传递给回调的 kobj_attribute 结构似乎已正确填充。回调现在可以正常工作(或修改,就此而言)。如下所述,spi_register_driver 只是调用sysfs_create_group。那么,为什么一个能正确调用回调而另一个不能呢?
下面的每个 cmets,下面是完整的 _init 函数和 spi_driver 结构。我自己手动创建路径的测试是基于第一个参考中的_init 代码,几乎没有修改。
static struct spi_driver ads7960_driver = {
.driver = {
.name = "ads7960",
.bus = &spi_bus_type,
.owner = THIS_MODULE,
.groups = attr_groups,
},
.probe = ads7960_probe,
.remove = __devexit_p(ads7960_remove),
.id_table = ads7960_id,
};
static int __init ads7960_init(void)
{
return spi_register_driver(&ads7960_driver);
}
module_init(ads7960_init);
【问题讨论】:
-
attr->attr不是指针,而是struct,因此您不应该尝试使用%p格式打印它(您只是看到第一个成员的值,即attr->attr.name)
标签: c linux linux-kernel driver