Title: [8189] trunk: Add irq_flags to:
- Revision
- 8189
- Author
- hennerich
- Date
- 2010-01-19 05:07:34 -0500 (Tue, 19 Jan 2010)
Log Message
Add irq_flags to:
struct spi_board_info
struct i2c_board_info
These flags can be optionally defined - slave drivers may use them as
flags argument for request_irq().
In case they are left un-initialized they will default to zero, and
therefore shouldn't cause problems.
This may avoid unconditional calls from platform init code to
set_irq_type() when SPI/I2C Slave drivers are build as modules.
It also matches behavior of some other frameworks like IDE and UIO.
Modified Paths
Diff
Modified: trunk/drivers/i2c/i2c-core.c (8188 => 8189)
--- trunk/drivers/i2c/i2c-core.c 2010-01-19 10:04:59 UTC (rev 8188)
+++ trunk/drivers/i2c/i2c-core.c 2010-01-19 10:07:34 UTC (rev 8189)
@@ -291,6 +291,7 @@
client->flags = info->flags;
client->addr = info->addr;
client->irq = info->irq;
+ client->irq_flags = info->irq_flags;
strlcpy(client->name, info->type, sizeof(client->name));
Modified: trunk/include/linux/i2c.h (8188 => 8189)
--- trunk/include/linux/i2c.h 2010-01-19 10:04:59 UTC (rev 8188)
+++ trunk/include/linux/i2c.h 2010-01-19 10:07:34 UTC (rev 8189)
@@ -227,6 +227,7 @@
* @platform_data: stored in i2c_client.dev.platform_data
* @archdata: copied into i2c_client.dev.archdata
* @irq: stored in i2c_client.irq
+ * @irq_flags: The flags passed to request_irq() for i2c_client.irq
*
* 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
@@ -246,6 +247,7 @@
void *platform_data;
struct dev_archdata *archdata;
int irq;
+ unsigned long irq_flags;
};
/**
_______________________________________________
Linux-kernel-commits mailing list
[email protected]
https://blackfin.uclinux.org/mailman/listinfo/linux-kernel-commits
