Looks like we need 1.39V for it to work --- arch/arm/boot/dts/omap5-board-common.dtsi | 4 ++-- 1 file changed, 2 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 @@ -476,8 +476,8 @@ smps6_reg: smps6 { /* VDD_DDR3 - over VDD_SMPS6 */ regulator-name = "smps6"; - regulator-min-microvolt = <1350000>; - regulator-max-microvolt = <1350000>; + regulator-min-microvolt = <1390000>; + regulator-max-microvolt = <1390000>; regulator-always-on; regulator-boot-on; };
As long as the kernel command line has earlycon, we will see console messages on the UART very early with this.
Signed-off-by: Tony Lindgren tony@atomide.com --- arch/arm/boot/dts/omap5-letux-cortex15-v5.0.dts | 4 ++++ 1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/omap5-letux-cortex15-v5.0.dts b/arch/arm/boot/dts/omap5-letux-cortex15-v5.0.dts --- a/arch/arm/boot/dts/omap5-letux-cortex15-v5.0.dts +++ b/arch/arm/boot/dts/omap5-letux-cortex15-v5.0.dts @@ -25,6 +25,10 @@ device_type = "memory"; reg = <0 0x80000000 0 0x7f000000>; /* 2032 MB */ }; + + chosen { + stdout-path = &uart3; + }; };
&cpu0 {
Pyra uses an alternate pad for uart3 to not conflict with sdio4. The wake-up interrupt address is the offset from pinctrl base 0x4A002920 - 0x4a002840 = 0xe0.
sleep 5; grep 2920 /sys/kernel/debug/pinctrl/4a002840.pinmux/pins --- arch/arm/boot/dts/pyra-mainboard-v5.0.dtsi | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/arch/arm/boot/dts/pyra-mainboard-v5.0.dtsi b/arch/arm/boot/dts/pyra-mainboard-v5.0.dtsi --- a/arch/arm/boot/dts/pyra-mainboard-v5.0.dtsi +++ b/arch/arm/boot/dts/pyra-mainboard-v5.0.dtsi @@ -789,6 +789,11 @@ >; };
+&uart3 { + interrupts-extended = <&wakeupgen GIC_SPI 74 IRQ_TYPE_LEVEL_HIGH>, + <&omap5_pmx_core 0xe0>; +}; + &mmc4 { /* enable second (ยต)SD slot (SDIO capable) */ status = "okay"; };
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>;
-
Tony Lindgren