Query: i2c_register_board_info
OS: centos
Section: 9
Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar
I2C_REGISTER_BOARD_I(9) I2C and SMBus Subsystem I2C_REGISTER_BOARD_I(9)NAMEi2c_register_board_info - statically declare I2C devicesSYNOPSISint i2c_register_board_info(int busnum, struct i2c_board_info const * info, unsigned len);ARGUMENTSbusnum 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.DESCRIPTIONSystems 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.COPYRIGHTKernel Hackers Manual 3.10 June 2014 I2C_REGISTER_BOARD_I(9)
Related Man Pages |
---|
i2c_register_board_info(9) - centos |
i2c_register_board_info(9) - suse |
struct_i2c_driver(9) - suse |
iicbus(4) - netbsd |
iicbus(4) - linux |
Similar Topics in the Unix Linux Community |
---|
WatchDog ReInit |
The new openSUSE community-elected board speaks |
new system board replacement? |
Keep connection alive between PC and board |
The Alternate DC board for AudioScope.sh. |