i2c_register_board_info(9) [suse man page]

I2C_REGISTER_BOARD_I(9) 				      I2C and SMBus Subsystem					   I2C_REGISTER_BOARD_I(9)

NAME

       i2c_register_board_info - statically declare I2C devices

SYNOPSIS

       int i2c_register_board_info(int busnum, struct i2c_board_info const * info, unsigned len);

ARGUMENTS

       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.

DESCRIPTION

       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.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010						   I2C_REGISTER_BOARD_I(9)

STRUCT 
I2C_BOARD_INF(9) 				      I2C and SMBus Subsystem					   STRUCT I2C_BOARD_INF(9)

NAME

       struct_i2c_board_info - template for device creation

SYNOPSIS

       struct i2c_board_info {
	 char type[I2C_NAME_SIZE];
	 unsigned short flags;
	 unsigned short addr;
	 void * platform_data;
	 struct dev_archdata * archdata;
	 struct device_node * of_node;
	 struct acpi_dev_node acpi_node;
	 int irq;
       };

MEMBERS

       type[I2C_NAME_SIZE]
	   chip type, to initialize i2c_client.name

       flags
	   to initialize i2c_client.flags

       addr
	   stored in i2c_client.addr

       platform_data
	   stored in i2c_client.dev.platform_data

       archdata
	   copied into i2c_client.dev.archdata

       of_node
	   pointer to OpenFirmware device node

       acpi_node
	   ACPI device node

       irq
	   stored in i2c_client.irq

DESCRIPTION

       I2C doesn't actually support hardware probing, although controllers and devices may be able to use I2C_SMBUS_QUICK to tell whether or not
       there's a device at a given address. Drivers commonly need more information than that, such as chip type, configuration, associated IRQ,
       and so on.

       i2c_board_info is used to build tables of information listing I2C devices that are present. This information is used to grow the driver
       model tree. For mainboards this is done statically using i2c_register_board_info; bus numbers identify adapters that aren't yet available.
       For add-on boards, i2c_new_device does this dynamically with the adapter already known.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   STRUCT I2C_BOARD_INF(9)