struct_matrix_keypad_platform_data(9) [centos man page]
STRUCT
MATRIX_KEYPAD(9) Input Subsystem STRUCT MATRIX_KEYPAD(9) NAME
struct_matrix_keypad_platform_data - platform-dependent keypad data SYNOPSIS
struct matrix_keypad_platform_data { const struct matrix_keymap_data * keymap_data; const unsigned int * row_gpios; const unsigned int * col_gpios; unsigned int num_row_gpios; unsigned int num_col_gpios; unsigned int col_scan_delay_us; unsigned int debounce_ms; unsigned int clustered_irq; unsigned int clustered_irq_flags; bool active_low; bool wakeup; bool no_autorepeat; }; MEMBERS
keymap_data pointer to matrix_keymap_data row_gpios pointer to array of gpio numbers representing rows col_gpios pointer to array of gpio numbers reporesenting colums num_row_gpios actual number of row gpios used by device num_col_gpios actual number of col gpios used by device col_scan_delay_us delay, measured in microseconds, that is needed before we can keypad after activating column gpio debounce_ms debounce interval in milliseconds clustered_irq may be specified if interrupts of all row/column GPIOs are bundled to one single irq clustered_irq_flags flags that are needed for the clustered irq active_low gpio polarity wakeup controls whether the device should be set up as wakeup source no_autorepeat disable key autorepeat DESCRIPTION
This structure represents platform-specific data that use used by matrix_keypad driver to perform proper initialization. COPYRIGHT
Kernel Hackers Manual 3.10 June 2014 STRUCT MATRIX_KEYPAD(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)