struct_hsi_board_info(9) [centos man page]

STRUCT 
HSI_BOARD_INF(9) 				   High Speed Synchronous Serial				   STRUCT HSI_BOARD_INF(9)

NAME

       struct_hsi_board_info - HSI client board info

SYNOPSIS

       struct hsi_board_info {
	 const char * name;
	 unsigned int hsi_id;
	 unsigned int port;
	 struct hsi_config tx_cfg;
	 struct hsi_config rx_cfg;
	 void * platform_data;
	 struct dev_archdata * archdata;
       };

MEMBERS

       name
	   Name for the HSI device

       hsi_id
	   HSI controller id where the client sits

       port
	   Port number in the controller where the client sits

       tx_cfg
	   HSI TX configuration

       rx_cfg
	   HSI RX configuration

       platform_data
	   Platform related data

       archdata
	   Architecture-dependent device data

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   STRUCT HSI_BOARD_INF(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;
	 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

       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 2.6.					     July 2010						   STRUCT I2C_BOARD_INF(9)