On Wed, Jul 22, 2009 at 10:04:10AM -0700, David Brownell wrote: > On Wednesday 22 July 2009, Mark Brown wrote: > > source for a PMIC then we've got generic code that expects to just take > > a gpio/irq and interact with it. > Is there a problem with how it works now? GPIO calls come in > sleeping (e.g. over I2C or SPI) and non-sleeping (classic SoC > GPIOs) varieties. And it's not gpiolib which would handle any I don't think there's any problem at all with gpiolib at all, it's just an example user here. > IRQ support ... it's the driver for the GPIO chip, which would > expose both irq_chip and gpio_chip facets. (Just like classic > SoC GPIO drivers.) Ah, yeah. If the chip IRQ driver handles the waking of the core thread then this'd not be a problem. For some reason I was thinking of the driver using gpiolib when I read Thomas' post. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
