树莓派 - platform总线,设备和驱动

本文解析了树莓派上LED设备的platform device与driver工作原理。通过具体代码示例和设备树配置,展示了LED设备如何与GPIO交互,并实现亮度控制等功能。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

以树莓派为例子,分析一下其中LED的 platform device 和 platform driver.


查看LED设备,被挂载在/sys/devices/platform下。

注意其中的driver指向, 

driver -> ../../../bus/platform/drivers/leds-gpio

pi@raspberrypi:/sys/devices/platform/leds $ tree
.
├── driver -> ../../../bus/platform/drivers/leds-gpio
├── driver_override
├── leds
│   ├── led0
│   │   ├── brightness
│   │   ├── device -> ../../../leds
│   │   ├── max_brightness
│   │   ├── power
│   │   │   ├── autosuspend_delay_ms
│   │   │   ├── control
│   │   │   ├── runtime_active_time
│   │   │   ├── runtime_status
│   │   │   └── runtime_suspended_time
│   │   ├── subsystem -> ../../../../../class/leds
│   │   ├── trigger
│   │   └── uevent
│   └── led1
│       ├── brightness
│       ├── device -> ../../../leds
│       ├── max_brightness
│       ├── power
│       │   ├── autosuspend_delay_ms
│       │   ├── control
│       │   ├── runtime_active_time
│       │   ├── runtime_status
│       │   └── runtime_suspended_time
│       ├── subsystem -> ../../../../../class/leds
│       ├── trigger
│       └── uevent
├── modalias
├── of_node -> ../../../firmware/devicetree/base/leds
├── power
│   ├── autosuspend_delay_ms
│   ├── control
│   ├── runtime_active_time
│   ├── runtime_status
│   └── runtime_suspended_time
├── subsystem -> ../../../bus/platform
└── uevent

同样,在/sys/bus/platform/drivers/leds-gpio下可以看到其中的leds指向了leds设备

pi@raspberrypi:/sys/bus/platform/drivers/leds-gpio $ tree
.
├── bind
├── leds -> ../../../../devices/platform/leds
├── uevent
└── unbind
这表示leds设备和leds-gpio驱动匹配



驱动leds-gpio.c

查看驱动,linux\drivers\leds\leds-gpio.c

/*
 * LEDs driver for GPIOs
 *
 * Copyright (C) 2007 8D Technologies inc.
 * Raphael Assenat <raph@8d.com>
 * Copyright (C) 2008 Freescale Semiconductor, Inc.
 *
 * This program is free software; you can redistribute it and/or modify
 * it under the terms of the GNU General Public License version 2 as
 * published by the Free Software Foundation.
 *
 */
#include <linux/err.h>
#include <linux/gpio.h>
#include <linux/gpio/consumer.h>
#include <linux/kernel.h>
#include <linux/leds.h>
#include <linux/module.h>
#include <linux/of.h>
#include <linux/platform_device.h>
#include <linux/property.h>
#include <linux/slab.h>

struct gpio_led_data {
	struct led_classdev cdev;
	struct gpio_desc *gpiod;
	u8 can_sleep;
	u8 blinking;
	gpio_blink_set_t platform_gpio_blink_set;
};

static inline struct gpio_led_data *
			cdev_to_gpio_led_data(struct led_classdev *led_cdev)
{
	return container_of(led_cdev, struct gpio_led_data, cdev);
}

static void gpio_led_set(struct led_classdev *led_cdev,
	enum led_brightness value)
{
	struct gpio_led_data *led_dat = cdev_to_gpio_led_data(led_cdev);
	int level;

	if (value == LED_OFF)
		level = 0;
	else
		level = 1;

	if (led_dat->blinking) {
		led_dat->platform_gpio_blink_set(led_dat->gpiod, level,
						 NULL, NULL);
		led_dat->blinking = 0;
	} else if (led_dat->cdev.flags & SET_GPIO_INPUT) {
		gpiod_direction_input(led_dat->gpiod);
		led_dat->cdev.flags &= ~SET_GPIO_INPUT;
	} else if (led_dat->cdev.flags & SET_GPIO_OUTPUT) {
		gpiod_direction_output(led_dat->gpiod, level);
		led_dat->cdev.flags &= ~SET_GPIO_OUTPUT;
	} else {
		if (led_dat->can_sleep ||
			(led_dat->cdev.flags & (SET_GPIO_INPUT | SET_GPIO_OUTPUT) ))
			gpiod_set_value_cansleep(led_dat->gpiod, level);
		else
			gpiod_set_value(led_dat->gpiod, level);
	}
}

static int gpio_led_set_blocking(struct led_classdev *led_cdev,
	enum led_brightness value)
{
	gpio_led_set(led_cdev, value);
	return 0;
}

static enum led_brightness gpio_led_get(struct led_classdev *led_cdev)
{
	struct gpio_led_data *led_dat =
		container_of(led_cdev, struct gpio_led_data, cdev);
	return gpiod_get_value_cansleep(led_dat->gpiod) ? LED_FULL : LED_OFF;
}

static int gpio_blink_set(struct led_classdev *led_cdev,
	unsigned long *delay_on, unsigned long *delay_off)
{
	struct gpio_led_data *led_dat = cdev_to_gpio_led_data(led_cdev);

	led_dat->blinking = 1;
	return led_dat->platform_gpio_blink_set(led_dat->gpiod, GPIO_LED_BLINK,
						delay_on, delay_off);
}

static int create_gpio_led(const struct gpio_led *template,
	struct gpio_led_data *led_dat, struct device *parent,
	struct device_node *np, gpio_blink_set_t blink_set)
{
	int ret, state;

	led_dat->gpiod = template->gpiod;
	if (!led_dat->gpiod) {
		/*
		 * This is the legacy code path for platform code that
		 * still uses GPIO numbers. Ultimately we would like to get
		 * rid of this block completely.
		 */
		unsigned long flags = GPIOF_OUT_INIT_LOW;

		/* skip leds that aren't available */
		if (!gpio_is_valid(template->gpio)) {
			dev_info(parent, "Skipping unavailable LED gpio %d (%s)\n",
					template->gpio, template->name);
			return 0;
		}

		if (template->active_low)
			flags |= GPIOF_ACTIVE_LOW;

		ret = devm_gpio_request_one(parent, template->gpio, flags,
					    template->name);
		if (ret < 0)
			return ret;

		led_dat->gpiod = gpio_to_desc(template->gpio);
		if (!led_dat->gpiod)
			return -EINVAL;
	}

	led_dat->cdev.name = template->name;
	led_dat->cdev.default_trigger = template->default_trigger;
	led_dat->can_sleep = gpiod_cansleep(led_dat->gpiod);
	if (!led_dat->can_sleep)
		led_dat->cdev.brightness_set = gpio_led_set;
	else
		led_dat->cdev.brightness_set_blocking = gpio_led_set_blocking;
	led_dat->blinking = 0;
	if (blink_set) {
		led_dat->platform_gpio_blink_set = blink_set;
		led_dat->cdev.blink_set = gpio_blink_set;
	}
	led_dat->cdev.brightness_get = gpio_led_get;
	if (template->default_state == LEDS_GPIO_DEFSTATE_KEEP) {
		state = gpiod_get_value_cansleep(led_dat->gpiod);
		if (state < 0)
			return state;
	} else {
		state = (template->default_state == LEDS_GPIO_DEFSTATE_ON);
	}
	led_dat->cdev.brightness = state ? LED_FULL : LED_OFF;
	if (!template->retain_state_suspended)
		led_dat->cdev.flags |= LED_CORE_SUSPENDRESUME;
	if (template->panic_indicator)
		led_dat->cdev.flags |= LED_PANIC_INDICATOR;
	if (template->retain_state_shutdown)
		led_dat->cdev.flags |= LED_RETAIN_AT_SHUTDOWN;

	ret = gpiod_direction_output(led_dat->gpiod, state);
	if (ret < 0)
		return ret;

	return devm_of_led_classdev_register(parent, np, &led_dat->cdev);
}

struct gpio_leds_priv {
	int num_leds;
	struct gpio_led_data leds[];
};

static inline int sizeof_gpio_leds_priv(int num_leds)
{
	return sizeof(struct gpio_leds_priv) +
		(sizeof(struct gpio_led_data) * num_leds);
}

static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
{
	struct device *dev = &pdev->dev;
	struct fwnode_handle *child;
	struct gpio_leds_priv *priv;
	int count, ret;

	count = device_get_child_node_count(dev);
	if (!count)
		return ERR_PTR(-ENODEV);

	priv = devm_kzalloc(dev, sizeof_gpio_leds_priv(count), GFP_KERNEL);
	if (!priv)
		return ERR_PTR(-ENOMEM);

	device_for_each_child_node(dev, child) {
		struct gpio_led_data *led_dat = &priv->leds[priv->num_leds];
		struct gpio_led led = {};
		const char *state = NULL;
		struct device_node *np = to_of_node(child);

		ret = fwnode_property_read_string(child, "label", &led.name);
		if (ret && IS_ENABLED(CONFIG_OF) && np)
			led.name = np->name;
		if (!led.name) {
			fwnode_handle_put(child);
			return ERR_PTR(-EINVAL);
		}

		led.gpiod = devm_fwnode_get_gpiod_from_child(dev, NULL, child,
							     GPIOD_ASIS,
							     led.name);
		if (IS_ERR(led.gpiod)) {
			fwnode_handle_put(child);
			return ERR_CAST(led.gpiod);
		}

		fwnode_property_read_string(child, "linux,default-trigger",
					    &led.default_trigger);

		if (!fwnode_property_read_string(child, "default-state",
						 &state)) {
			if (!strcmp(state, "keep"))
				led.default_state = LEDS_GPIO_DEFSTATE_KEEP;
			else if (!strcmp(state, "on"))
				led.default_state = LEDS_GPIO_DEFSTATE_ON;
			else
				led.default_state = LEDS_GPIO_DEFSTATE_OFF;
		}

		if (fwnode_property_present(child, "retain-state-suspended"))
			led.retain_state_suspended = 1;
		if (fwnode_property_present(child, "retain-state-shutdown"))
			led.retain_state_shutdown = 1;
		if (fwnode_property_present(child, "panic-indicator"))
			led.panic_indicator = 1;

		ret = create_gpio_led(&led, led_dat, dev, np, NULL);
		if (ret < 0) {
			fwnode_handle_put(child);
			return ERR_PTR(ret);
		}
		led_dat->cdev.dev->of_node = np;
		priv->num_leds++;
	}

	return priv;
}

static const struct of_device_id of_gpio_leds_match[] = {
	{ .compatible = "gpio-leds", },
	{},
};

MODULE_DEVICE_TABLE(of, of_gpio_leds_match);

static int gpio_led_probe(struct platform_device *pdev)
{
	struct gpio_led_platform_data *pdata = dev_get_platdata(&pdev->dev);
	struct gpio_leds_priv *priv;
	int i, ret = 0;

	if (pdata && pdata->num_leds) {
		priv = devm_kzalloc(&pdev->dev,
				sizeof_gpio_leds_priv(pdata->num_leds),
					GFP_KERNEL);
		if (!priv)
			return -ENOMEM;

		priv->num_leds = pdata->num_leds;
		for (i = 0; i < priv->num_leds; i++) {
			ret = create_gpio_led(&pdata->leds[i], &priv->leds[i],
					      &pdev->dev, NULL,
					      pdata->gpio_blink_set);
			if (ret < 0)
				return ret;
		}
	} else {
		priv = gpio_leds_create(pdev);
		if (IS_ERR(priv))
			return PTR_ERR(priv);
	}

	platform_set_drvdata(pdev, priv);

	return 0;
}

static void gpio_led_shutdown(struct platform_device *pdev)
{
	struct gpio_leds_priv *priv = platform_get_drvdata(pdev);
	int i;

	for (i = 0; i < priv->num_leds; i++) {
		struct gpio_led_data *led = &priv->leds[i];

		if (!(led->cdev.flags & LED_RETAIN_AT_SHUTDOWN))
			gpio_led_set(&led->cdev, LED_OFF);
	}
}

static struct platform_driver gpio_led_driver = {
	.probe		= gpio_led_probe,
	.shutdown	= gpio_led_shutdown,
	.driver		= {
		.name	= "leds-gpio",
		.of_match_table = of_gpio_leds_match,
	},
};

module_platform_driver(gpio_led_driver);

MODULE_AUTHOR("Raphael Assenat <raph@8d.com>, Trent Piepho <tpiepho@freescale.com>");
MODULE_DESCRIPTION("GPIO LED driver");
MODULE_LICENSE("GPL");
MODULE_ALIAS("platform:leds-gpio");

注册platform device

在树莓派的系统中是通过设备树来注册leds设备的

在bcm2708-rpi.dtsi中

	leds: leds {
		compatible = "gpio-leds";
	};

在bcm2709-rpi-2-b.dts

&leds {
	act_led: act {
		label = "led0";
		linux,default-trigger = "mmc0";
		gpios = <&gpio 47 0>;
	};

	pwr_led: pwr {
		label = "led1";
		linux,default-trigger = "input";
		gpios = <&gpio 35 0>;
	};
};



参考:

https://blog.youkuaiyun.com/zqixiao_09/article/details/50889458

https://blog.youkuaiyun.com/subfate/article/details/53494926

https://blog.youkuaiyun.com/jklinux/article/details/78645106

<think>好的,我现在需要回答用户关于platform驱动字符设备驱动之间的区别以及它们的应用场景的问题。首先,我应该回顾一下这两种驱动的基本概念结构,然后比较它们的差异,最后讨论各自的应用场景。 根据用户提供的引用内容,尤其是引用[1]提到字符设备驱动设备是静态绑定的,设备信息以常量形式写在驱动中,没有探测PROBE过程。而引用[4]提到platform驱动中的platform_device结构体是由设备树生成的,包含硬件资源描述。这说明platform驱动更动态,设备信息可能来自设备树,而字符设备驱动则是静态绑定的。 接下来,我需要明确两者的主要差异。可能包括设备绑定方式、硬件资源管理、设备探测机制等方面。例如,字符设备驱动通常是直接与硬件绑定,而platform驱动通过platform总线进行匹配,设备信息可能来自设备树或ACPI,这使得platform驱动更灵活,适合嵌入式系统中的外设管理。 然后,应用场景方面,字符设备驱动可能用于简单的、固定的设备,比如早期的GPIO控制(引用[2]提到GPIO属于嵌入式系统的重要部分),而platform驱动用于更复杂的、动态检测的设备,比如MMC主控制器(引用[3]提到的MMC主设备驱动)。此外,platform驱动常用于那些不需要传统总线(如PCI、USB)的设备,但需要与内核的platform总线框架集成的情况。 需要确保回答结构清晰,分点列出差异场景,并正确引用提供的资料。同时,检查是否有遗漏点,比如设备树的使用、资源管理方式等。还要注意用户提到的驱动开发分类,可能涉及总线设备驱动模型与字符驱动的对比,如引用[1]所述总线设备驱动不同,platform驱动属于总线设备驱动模型的一部分,而字符驱动则不是。 最后,生成相关问题时要围绕主题,可能涉及两种驱动的选择标准、迁移到设备树的优势,或者具体开发实例的区别。确保问题有针对性,能帮助用户深入理解主题。</think>### Platform驱动与字符设备驱动的差异及应用场景 #### 一、主要差异 1. **设备绑定方式** - **字符设备驱动**:设备信息通常硬编码在驱动代码中,与硬件静态绑定[^1]。例如早期的GPIO驱动直接通过寄存器地址操作硬件[^2]。 - **Platform驱动**:通过设备树(Device Tree)或ACPI动态描述设备资源(如内存地址、中断号),驱动设备通过`platform_device``platform_driver`匹配[^4]。例如MMC主控制器驱动注册时会关联设备树中的节点[^3]。 2. **硬件资源管理** - **字符设备驱动**:资源(如寄存器地址)直接以常量形式定义,缺乏灵活性。 - **Platform驱动**:资源由`platform_device`动态传递,驱动通过`probe()`函数获取资源(如`gpiod_get()`获取GPIO描述符),适配不同硬件配置。 3. **设备探测机制** - **字符设备驱动**:无探测过程,设备存在性由驱动初始化时预设。 - **Platform驱动**:依赖总线匹配机制,当设备树中定义的设备驱动匹配时,触发`probe()`函数完成初始化。 4. **代码结构** - **字符设备驱动**:仅需实现`file_operations`接口,注册主设备号(如`register_chrdev()`)。 - **Platform驱动**:需实现`platform_driver`结构体,包含`probe()`、`remove()`等方法,并与设备树节点绑定(如`.of_match_table`)。 --- #### 二、应用场景 1. **字符设备驱动适用场景** - **简单固定设备**:如早期按键、LED控制,硬件资源固定且无需动态适配。 - **无总线依赖的设备**:如直接操作寄存器的硬件(如某些传感器)。 - **快速原型开发**:适合功能验证,无需复杂设备模型支持。 2. **Platform驱动适用场景** - **动态资源配置**:如基于设备树的嵌入式系统(如树莓派GPIO管理)。 - **片上系统(SoC)外设**:如I2C控制器、SPI总线、MMC/SD接口。 - **需热插拔支持的设备**:通过设备树动态加载驱动,适应硬件变化。 --- #### 三、代码示例对比 **字符设备驱动(简化)** ```c static int my_chrdev_open(struct inode *inode, struct file *filp) { // 直接操作固定硬件地址 writel(0x1, HW_REG_ADDR); return 0; } static struct file_operations fops = { .open = my_chrdev_open, }; static int __init chrdev_init(void) { register_chrdev(MAJOR_NUM, "my_chrdev", &fops); // 静态注册 return 0; } ``` **Platform驱动(简化)** ```c static int my_platform_probe(struct platform_device *pdev) { struct resource *res = platform_get_resource(pdev, IORESOURCE_MEM, 0); void __iomem *reg = ioremap(res->start, resource_size(res)); // 动态获取资源 gpiod_get(&pdev->dev, "led", GPIOD_OUT_LOW); // 从设备树获取GPIO return 0; } static struct platform_driver plt_drv = { .probe = my_platform_probe, .driver = { .name = "my_platform", .of_match_table = of_match_ptr(my_of_ids) }, }; module_platform_driver(plt_drv); // 自动注册并与设备树节点匹配 ``` ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值