struct_uio_mem(9) [centos man page]

STRUCT 
UIO_MEM(9)					   Device drivers infrastructure					 STRUCT UIO_MEM(9)

NAME

       struct_uio_mem - description of a UIO memory region

SYNOPSIS

       struct uio_mem {
	 const char * name;
	 phys_addr_t addr;
	 unsigned long size;
	 int memtype;
	 void __iomem * internal_addr;
	 struct uio_map * map;
       };

MEMBERS

       name
	   name of the memory region for identification

       addr
	   address of the device's memory (phys_addr is used since addr can be logical, virtual, or physical & phys_addr_t should always be large
	   enough to handle any of the address types)

       size
	   size of IO

       memtype
	   type of memory addr points to

       internal_addr
	   ioremap-ped version of addr, for driver internal use

       map
	   for use by the UIO core only.

COPYRIGHT

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