spidev.c中spidev_probe函数没有被调用
/* The main reason to have this class is to make mdev/udev create the
* /dev/spidevB.C character device nodes exposing our userspace API.
* It also simplifies memory management.
*/
static struct class spidev_class = {
.name = "spidev",
.owner = THIS_MODULE,
};
/*-------------------------------------------------------------------------*/
static int spidev_probe(struct spi_device *spi)
{
struct spidev_data *spidev;
int status;
unsigned long minor;
/* Allocate driver data */
spidev = kzalloc(sizeof(*spidev), GFP_KERNEL);
printk("in the spidev_probe\n");
if (!spidev)
return -ENOMEM;
/* Initialize the driver data */
spidev->spi = spi;
mutex_init(&spidev->buf_lock);
INIT_LIST_HEAD(&spidev->device_entry);
/* If we can allocate a minor number, hook up this device.
* Reusing minors is fine so long as udev or mdev is working.
*/
mutex_lock(&device_list_lock);
minor = find_first_zero_bit(minors, N_SPI_MINORS);
if (minor < N_SPI_MINORS) {
spidev->dev.parent = &spi->dev;
spidev->dev.class = &spidev_class;
spidev->dev.devt = MKDEV(SPIDEV_MAJOR, minor);
snprintf(spidev->dev.bus_id, sizeof spidev->dev.bus_id,
"spidev%d.%d",
spi->master->bus_num, spi->chip_select);
status = device_register(&spidev->dev);
} else {
dev_dbg(&spi->dev, "no minor number available!\n");
status = -ENODEV;
}
if (status == 0) {
set_bit(minor, minors);
dev_set_drvdata(&spi->dev, spidev);
list_add(&spidev->device_entry, &device_list);
}
mutex_unlock(&device_list_lock);
if (status != 0)
kfree(spidev);
return status;
}
把相关的config都配置了,但是编译后的内核启动后并没有调用spidev_probe探测函数。这个probe是如何才会被调用的。
* /dev/spidevB.C character device nodes exposing our userspace API.
* It also simplifies memory management.
*/
static struct class spidev_class = {
.name = "spidev",
.owner = THIS_MODULE,
};
/*-------------------------------------------------------------------------*/
static int spidev_probe(struct spi_device *spi)
{
struct spidev_data *spidev;
int status;
unsigned long minor;
/* Allocate driver data */
spidev = kzalloc(sizeof(*spidev), GFP_KERNEL);
printk("in the spidev_probe\n");
if (!spidev)
return -ENOMEM;
/* Initialize the driver data */
spidev->spi = spi;
mutex_init(&spidev->buf_lock);
INIT_LIST_HEAD(&spidev->device_entry);
/* If we can allocate a minor number, hook up this device.
* Reusing minors is fine so long as udev or mdev is working.
*/
mutex_lock(&device_list_lock);
minor = find_first_zero_bit(minors, N_SPI_MINORS);
if (minor < N_SPI_MINORS) {
spidev->dev.parent = &spi->dev;
spidev->dev.class = &spidev_class;
spidev->dev.devt = MKDEV(SPIDEV_MAJOR, minor);
snprintf(spidev->dev.bus_id, sizeof spidev->dev.bus_id,
"spidev%d.%d",
spi->master->bus_num, spi->chip_select);
status = device_register(&spidev->dev);
} else {
dev_dbg(&spi->dev, "no minor number available!\n");
status = -ENODEV;
}
if (status == 0) {
set_bit(minor, minors);
dev_set_drvdata(&spi->dev, spidev);
list_add(&spidev->device_entry, &device_list);
}
mutex_unlock(&device_list_lock);
if (status != 0)
kfree(spidev);
return status;
}
把相关的config都配置了,但是编译后的内核启动后并没有调用spidev_probe探测函数。这个probe是如何才会被调用的。
...全文
相关推荐
linux c spi应用层 通信源代码
linux c spi应用层 通信源代码
linux 驱动修炼 SPI驱动
linux驱动修炼 SPI驱动框架源码分析(中)
嵌入式Linux驱动之RFID-rc522[源码]
本文详细介绍了在嵌入式Linux系统中如何为RFID-rc522模块编写SPI设备驱动程序。作者以kernel4.8.17为例,首先讲解了如何修改mach-smdk2440.c文件以适配spi1接口,然后详细说明了如何解决platform信息缺失、时钟问题以及devm_kzalloc与kzalloc的选择等关键问题。文章还包含了完整的设备注册代码、驱动实现代码以及调试过程中遇到的各种问题及其解决方案,为开发者提供了宝贵的实践经验。最后,作者还分享了如何通过spidev_test工具进行调试,并给出了相关的头文件定义。
DuCut_1795224829955_400.mp4
DuCut_1795224829955_400.mp4
互联网+智慧医疗大数据信息平台建设方案.pptx
互联网+智慧医疗大数据信息平台建设方案.pptx


