Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

struct_uio_info(9) [suse man page]

STRUCT 
UIO_INFO(9) Device drivers infrastructure STRUCT UIO_INFO(9) NAME
struct_uio_info - UIO device capabilities SYNOPSIS
struct uio_info { struct uio_device * uio_dev; const char * name; const char * version; struct uio_mem mem[MAX_UIO_MAPS]; struct uio_port port[MAX_UIO_PORT_REGIONS]; long irq; unsigned long irq_flags; void * priv; irqreturn_t (* handler) (int irq, struct uio_info *dev_info); int (* mmap) (struct uio_info *info, struct vm_area_struct *vma); int (* open) (struct uio_info *info, struct inode *inode); int (* release) (struct uio_info *info, struct inode *inode); int (* irqcontrol) (struct uio_info *info, s32 irq_on); }; MEMBERS
uio_dev the UIO device this info belongs to name device name version device driver version mem[MAX_UIO_MAPS] list of mappable memory regions, size==0 for end of list port[MAX_UIO_PORT_REGIONS] list of port regions, size==0 for end of list irq interrupt number or UIO_IRQ_CUSTOM irq_flags flags for request_irq priv optional private data handler the device's irq handler mmap mmap operation for this uio device open open operation for this uio device release release operation for this uio device irqcontrol disable/enable irqs when 0/1 is written to /dev/uioX COPYRIGHT
Kernel Hackers Manual 2.6. July 2010 STRUCT UIO_INFO(9)

Check Out this Related Man Page

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)
Man Page