STRUCT IRQ_DATA(9) Structures STRUCT IRQ_DATA(9)NAME
struct_irq_data - per irq and irq chip data passed down to chip functions
SYNOPSIS
struct irq_data {
unsigned int irq;
unsigned long hwirq;
unsigned int node;
unsigned int state_use_accessors;
struct irq_chip * chip;
struct irq_domain * domain;
void * handler_data;
void * chip_data;
struct msi_desc * msi_desc;
cpumask_var_t affinity;
};
MEMBERS
irq
interrupt number
hwirq
hardware interrupt number, local to the interrupt domain
node
node index useful for balancing
state_use_accessors
status information for irq chip functions. Use accessor functions to deal with it
chip
low level interrupt hardware access
domain
Interrupt translation domain; responsible for mapping between hwirq number and linux irq number.
handler_data
per-IRQ data for the irq_chip methods
chip_data
platform-specific per-chip private data for the chip methods, to allow shared chip implementations
msi_desc
MSI descriptor
affinity
IRQ affinity on SMP
DESCRIPTION
The fields here need to overlay the ones in irq_desc until we cleaned up the direct references and switched everything over to irq_data.
AUTHORS
Thomas Gleixner <tglx@linutronix.de>
Author.
Ingo Molnar <mingo@elte.hu>
Author.
COPYRIGHT Kernel Hackers Manual 3.10 June 2014 STRUCT IRQ_DATA(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;
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)
Hello,
I have develop a driver for my hardware and now, I need to handle a IRQ but I does not work.
As I can understand, to handle a irq, it is necessary to make a request_irq(). If the return value is zero, ok, no problem to handle irq.
Here is a easy example of my driver:
#include... (8 Replies)
I receive the following warning messages on a very new machine which has FreeBSD 8.1 x64 installed on it:
Interrupt storm detected on "irq 20" throttling interrupt source
It is unclear what this means and what its origins are (motherboard? CPU? RAM?).
I can start the desktop and the message is... (4 Replies)
what is this error log = hda: irq timeout: error=0x00 and how to solve?
every day upon checking the logs i see this error.
hda: irq timeout: error=0x00
hda: irq timeout: error=0x00
hda: irq timeout: error=0x00
hda: irq timeout: error=0x00
hw_client: segfault at 0000000000000046 rip... (3 Replies)
Hello everyone. I feel that I'm about to answer my own question, but I just want to be sure that I'm right. I know computers all use, at a very low level, the IRQ system of interrupting the CPU when it needs something. My questions are as follows:
1. Does the device in question, say.. a mouse,... (1 Reply)