Until we figure out if wlcore can use a secondary wakeup interrupt or until we figure out why omap5 gpio_wk14 won't wake up the system, we can configure gpio_wk14 padconf wake-up interrupt for SDIO. This allows ssh to pyra to work waking up to keyboard events. --- arch/arm/boot/dts/omap5-board-common.dtsi | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/omap5-board-common.dtsi b/arch/arm/boot/dts/omap5-board-common.dtsi --- a/arch/arm/boot/dts/omap5-board-common.dtsi +++ b/arch/arm/boot/dts/omap5-board-common.dtsi @@ -339,16 +339,24 @@ ti,non-removable; };
+/* + * Note that we use gpio_wk14 padconf interrupt as the WLAN wakeirq + * for wlcore instead of the sdio_dat1 interrupt as wlcore does not + * seem to support sdio_dat1 interrupt. Any boards using other WLAN + * chips such as mwifiex_sdio probably need to configure the wakeirq + * to <&omap5_pmx_core 0x16a> instead of <&omap5_pmx_wkup 0>. + */ &mmc3 { vmmc-supply = <&vmmcsdio_fixed>; mmc-pwrseq = <&mmc3_pwrseq>; bus-width = <4>; non-removable; cap-power-off-card; + keep-power-in-suspend; pinctrl-names = "default"; pinctrl-0 = <&mmc3_pins>; - interrupts-extended = <&wakeupgen GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH - &omap5_pmx_core 0x16a>; + interrupts-extended = <&wakeupgen GIC_SPI 94 IRQ_TYPE_LEVEL_HIGH>, + <&omap5_pmx_wkup 0>;
#address-cells = <1>; #size-cells = <0>;