On Fri, Jun 7, 2013 at 10:50 PM, Tony Lindgren [off-list ref] wrote:

For wake-up events from deeper idle modes we need to check the
configured padconf registers for the wake-up bit and then call
the related interrupt handler.

Done in collaboration with Roger Quadros [off-list ref].

Cc: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: Peter Ujfalusi <redacted>
Cc: devicetree-discuss at lists.ozlabs.org
Signed-off-by: Roger Quadros <redacted>
Signed-off-by: Tony Lindgren <tony@atomide.com>

(...)

+                       pcsoi->gpio = r->gpio;

This "gpio" member appear to be used nowhere, which is probably
related to what I was saying about custom GPIO interfaces doing
pinconf, but I could be wrong...

+/*
+ * Note that omap2430 has 8-bit padconf registers and uses
+ * the plain pinctrl-single binding.
+ */
+static const struct of_device_id pcs_omap_of_match[] = {
+       { .compatible = "ti,omap3-padconf", },
+       { .compatible = "ti,omap4-padconf", },
+       { .compatible = "ti,omap5-padconf", },
+       {}
+};

Goes into some binding document?

Yours,
Linus Walleij