[i2c] [PATCH 2/2] I2C: ISP1301_OMAP: New-style i2c driver updates, part 2

David Brownell david-b at pacbell.net
Fri Mar 7 21:20:09 CET 2008


On Tuesday 26 February 2008, Felipe Balbi wrote:
> >
> >  Passing irq_flags???  That sounds like nonsense.  Please explain ...
> 
> request_irq was using different irq flags depending on the board, so
> instead of keeping if (machine_is_*) in the driver just because of irq
> flags we could bring it from a platform_data.

Just use the resource type flags ... IORESOURCE_IRQ can
be combined with 

#define IORESOURCE_IRQ_HIGHEDGE         (1<<0)
#define IORESOURCE_IRQ_LOWEDGE          (1<<1)
#define IORESOURCE_IRQ_HIGHLEVEL        (1<<2)
#define IORESOURCE_IRQ_LOWLEVEL         (1<<3)
#define IORESOURCE_IRQ_SHAREABLE        (1<<4)

I'd presume "highedge" means "rising", etc.

- Dave



More information about the i2c mailing list