diff options
| author | Balaji T K <balajitk@ti.com> | 2013-12-02 11:38:13 -0800 |
|---|---|---|
| committer | Tony Lindgren <tony@atomide.com> | 2013-12-02 11:38:13 -0800 |
| commit | 2ba2866f782f7f1c38abc3dd56d3295efd289264 (patch) | |
| tree | f04ebd55521d179704c65bf6134d981fd9e37f47 /arch/arm/boot/dts/phy3250.dts | |
| parent | 9cb238c00ba5c1ddfff2c2ed6aa66c15b962e4c3 (diff) | |
| download | talos-obmc-linux-2ba2866f782f7f1c38abc3dd56d3295efd289264.tar.gz talos-obmc-linux-2ba2866f782f7f1c38abc3dd56d3295efd289264.zip | |
ARM: dts: omap4-panda-common: Fix pin muxing for wl12xx
pin mux wl12xx_gpio and wl12xx_pins should be part of omap4_pmx_core
and not omap4_pmx_wkup. So, move wl12xx_* to omap4_pmx_core.
Fix the following error message:
pinctrl-single 4a31e040.pinmux: mux offset out of range: 0x38 (0x38)
pinctrl-single 4a31e040.pinmux: could not add functions for pinmux_wl12xx_pins 56x
SDIO card is not detected after moving pin mux to omap4_pmx_core since
sdmmc5_clk pull is disabled. Enable Pull up on sdmmc5_clk to detect SDIO card.
This fixes a regression where WLAN did not work after a warm reset
or after one up/down cycle that happened when we move omap4 to boot
using device tree only. For reference, the kernel bug is described at:
https://bugzilla.kernel.org/show_bug.cgi?id=63821
Cc: stable@vger.kernel.org # v3.10+
Signed-off-by: Balaji T K <balajitk@ti.com>
[tony@atomide.com: update comments to describe the regression]
Signed-off-by: Tony Lindgren <tony@atomide.com>
Diffstat (limited to 'arch/arm/boot/dts/phy3250.dts')
0 files changed, 0 insertions, 0 deletions
