Hi Simon, On 15.12.2011 17:41, Simon Budig wrote: > If I am not supposed to use irq_to_gpio, then how do I solve this? > > * expect the board file to set up the resp. GPIO direction? If you don't need GPIO number for anything else (e.g. reading GPIO state manually) I'd go that way. This introduces a bit of code duplication as Anatolij already said but I think this is acceptable. If your code wants IRQ number than pass IRQ number to it. I can't see any reason for the driver to "know" that IRQ comes from GPIO. > or > > * use an entry in my platform data (next to the reset pin) for the gpio > number and then try to map this to an irq number? > > or did I miss the best solution? Probably it makes sense to configure GPIO as input when the corresponding interrupt is requested from GPIO driver internally. However, this will require some rework. Regards, Ilya. -- 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
