Am 16.07.2014 12:01, wrote Simon Budig: > On 15/07/14 19:43, Markus Niebel wrote: >> - when adding an int-gpios node to devicetree and parsing this gpio the gpio will be configured as input >> - IRQ can be seen by CPU >> >> Question: >> >> - shall we add an int-gpio property to enable gpio pin config as input or > > Shouldn't it be possible to configure the pin as input directly from the > device tree, indepently from the touch driver section? I don't see, how to do that, maybe I did miss the right point. I digged through the gpio code. There are drivers (gpio-omap) that make sure, that gpio is configured as input and others that don't care (gpio-mxc / gpio-mxs). seeing this I posted "gpio: gpio-mxc: make sure gpio is input when request IRQ" on linux-arm-kernel Global question is: how can we make sure, that the driver that request the IRQ requests also the GPIO (implicit or like in the old platfrom data days explicit)? But thats beyond input devices and my knowledge. Regards Markus > > Bye, > Simon > -- 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
