linux i2c子系統程式碼分析9---i2c裝置的註冊方法

阿新 • • 發佈：2019-01-20

/**
* i2c_register_board_info - statically declare I2C devices
* @busnum: identifies the bus to which these devices belong
* @info: vector of i2c device descriptors
* @len: how many descriptors in the vector; may be zero to reserve
*the specified bus number.
*
* Systems using the Linux I2C driver stack can declare tables of board info
* while they initialize. This should be done in board-specific init code
* near arch_initcall() time, or equivalent, before any I2C adapter driver is
* registered. For example, mainboard init code could define several devices,
* as could the init code for each daughtercard in a board stack.
*
* The I2C devices will be created later, after the adapter for the relevant
* bus has been registered. After that moment, standard driver model tools
* are used to bind "new style" I2C drivers to the devices. The bus number
* for any device declared using this routine is not available for dynamic
* allocation.
*
* The board info passed can safely be __initdata, but be careful of embedded
* pointers (for platform_data, functions, etc) since that won't be copied.
*/
int __init
i2c_register_board_info(int busnum,
struct i2c_board_info const *info, unsigned len)
{
int status;

down_write(&__i2c_board_lock);

/* dynamic bus numbers will be assigned after the last static one */
if (busnum >= __i2c_first_dynamic_bus_num)
__i2c_first_dynamic_bus_num = busnum + 1;

for (status = 0; len; len--, info++) {
struct i2c_devinfo*devinfo;

devinfo = kzalloc(sizeof(*devinfo), GFP_KERNEL);
if (!devinfo) {
pr_debug("i2c-core: can't register boardinfo!\n");
status = -ENOMEM;
break;
}

devinfo->busnum = busnum;
devinfo->board_info = *info;
list_add_tail(&devinfo->list, &__i2c_board_list);
}

up_write(&__i2c_board_lock);

return status;
}

linux i2c子系統程式碼分析9---i2c裝置的註冊方法

linux i2c子系統程式碼分析9---i2c裝置的註冊方法

MTK I2C驅動程式碼分析

clk子系統 - 程式碼分析

linux input子系統程式碼閱讀簡單記錄

Linux ubi子系統原理分析

老男孩教育每日一題-第60天-一道實用Linux運維問題的9種Shell解答方法！

linux下adb連不上android裝置解決方法

linux IIC子系統分析(九)——例項分析通過裝置節點訪問I2c裝置

Linux裝置驅動程式架構分析之I2C架構（基於3.10.1核心）

linux IIC子系統分析(二)—— linux i2c 架構概述

基於i2c子系統的驅動分析-裝置樹

linux IIC子系統分析(四)——I2c bus初始化

linux裝置模型之I2C子系統

Linux i2c子系統(一) _動手寫一個i2c裝置驅動

i2c子系統-eeprom例項分析

linux核心的I2C子系統

Linux--核心---I2C匯流排驅動分析以linux3.10.0 RK3288為例

linux驅動由淺入深系列：usb子系統之四（android平臺滑鼠驅動程式碼分析）

linux驅動學習（八） i2c驅動架構（史上最全） davinc dm368 i2c驅動分析

嵌入式Linux——IIC驅動（2）：i2c驅動框架分析

linux i2c子系統程式碼分析9---i2c裝置的註冊方法

相關推薦