Hey all,
I am trying to initialize a GPIO interrupt as a wake source on am335x on a custom board.
My current strategy is to initialize it as such in the device tree:
-----------------------------------------------------------------------------------
gpio_keys {
compatible = "gpio-keys";
#address-cells = <1>;
#size-cells = <0>;
//autorepeat;
dummykey {
label = "USB connect";
linux,code = <67>;
gpios = <&gpio2 3 GPIO_ACTIVE_HIGH>;
gpio-key,wakeup;
linux,wakeup;
status = "okay";
};
};
---------------------------------------------------------------------------
The above code creates a dummy gpio-key device to enable the wakeup (since according to this discussion:
https://groups.google.com/forum/#!topic/linux.kernel/91NMQdu3g0E
GPIOs are not devices and hence cannot be a considered as a wakeup source by themselves).
The problem is that I still cannot wakeup from standby mode with this configuration. I am also not sure if the interrupt is even firing, but it at least appears in /proc/interrupts.
Is there any way to expose the GPIO in sysfs without taking it away from my dummy device? That would be helpful
.
Apparently, there is an issue with using omap-gpio as an interrupt controller (http://comments.gmane.org/gmane.linux.ports.arm.omap/92192) in the device tree, which is why I don't think I can get around locking the GPIO
to my device.
If anybody could give me advice on how to get this wakeup interrupt to work, I would greatly appreciate it.
Thanks,
Nolan