On Mon, Jul 29, 2013 at 1:11 PM, Javier Martinez Canillas <javier.martinez@xxxxxxxxxxxxxxx> wrote: > A different "GPIO hogs" approach will be used to pre-define which GPIO > are going to be used as IRQ so the core can request them and setup as input. > > I expect you will have the same issue with this new approach though since > the omap hsmmc driver will try to call gpio_request() on a previously > requested GPIO. This should not happen. I've realized that GPIO interrupt hogs will just redefine information that already exist in the device tree. The right way is to traverse the tree, find all references to the GPIO based interrupt-controller, and request each of these lines as GPIO (i.e. hog them) in the gpiolib OF core. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
