mmc2: error -22 whilst initialising SDIO card

Fabio Martins

Other Parts Discussed in Thread: WL1271

Hello all,

I am trying to setup a wifi module (wl12xx) in MMC2 (mmc0, MMC1, MMC2) in AM335x, but I'm always getting the same message:

[ 15.480617] mmc2: queuing unknown CIS tuple 0x0f (0 bytes)
[ 15.487081] mmc2: queuing unknown CIS tuple 0x03 (0 bytes)
[ 15.589693] mmc2: queuing unknown CIS tuple 0x01 (0 bytes)
[ 15.595537] mmc2: queuing unknown CIS tuple 0x10 (0 bytes)
[ 15.601843] mmc2: queuing unknown CIS tuple 0x04 (0 bytes)
[ 15.610737] mmc2: queuing unknown CIS tuple 0x3f (0 bytes)
[ 15.703955] mmc2: queuing unknown CIS tuple 0x04 (0 bytes)
[ 15.710504] mmc2: queuing unknown CIS tuple 0x01 (0 bytes)
[ 15.717756] mmc2: queuing unknown CIS tuple 0x3f (0 bytes)
[ 15.811368] mmc2: queuing unknown CIS tuple 0x04 (0 bytes)

[ 18.602396] mmc2: error -22 whilst initialising SDIO card

I checked all the signs as suggested in:

processors.wiki.ti.com/.../WL18xx_Platform_Integration_Guide

My device tree:

mmc3_pins: pinmux_mmc3_pins {

pinctrl-single,pins = <
0x74 (PIN_INPUT_PULLUP | MUX_MODE7) /* gpmc_wpn.gpio0_31 */
0x44 (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_a1.mmc2_dat0 */
0x48 (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_a2.mmc2_dat1 */
0x4C (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_a3.mmc2_dat2 */
0x78 (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_ben1.mmc2_dat3 */
0x88 (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_csn3.mmc2_cmd */
0x8C (PIN_INPUT_PULLUP | MUX_MODE3) /* gpmc_clk.mmc2_clk */
>;
};

wl12xx_gpio: pinmux_wl12xx_gpio {
pinctrl-single,pins = <
0x7c (PIN_OUTPUT_PULLUP | MUX_MODE7) /* gpmc_csn0.gpio1_29 */
>;
};

wl12xx_vmmc: fixedregulator@2 {
pinctrl-names = "default";
pinctrl-0 = <&wl12xx_gpio>;
compatible = "regulator-fixed";
regulator-name = "vwl1271";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
gpio = <&gpio1 29 0>;
startup-delay-us = <70000>;
enable-active-high;
};

&edma {
ti,edma-xbar-event-map = /bits/ 16 <1 12
2 13>;
};

&mmc3 {
/*these are on the crossbar and are outlined in the
xbar-event-map element */
dmas = <&edma 12
&edma 13>;
dma-names = "tx", "rx";
status = "okay";
vmmc-supply = <&wl12xx_vmmc>;
bus-width = <4>;
pinctrl-names = "default";
pinctrl-0 = <&mmc3_pins>;
ti,dual-volt;
ti,non-removable;
cap-power-off-card;
keep-power-in-suspend;
};

Any error in my configuration?
This error may be hardware?

I'm using the kernel by Robert Nelson. eewiki.net/.../BeagleBone+Black

Thanks

Fabio

over 9 years ago

0 Iain Hunter over 9 years ago

TI__Genius 16130 points

Fabio,
First thing I want to check is that you are using a wl1271 device based on your naming.

From a device tree point of view you seem to be missing the regulator vwl1271 that should have the gpio defined to drive the WL_EN line. Can you check with a scope if this is triggered.

Secondly you need to build the wl12xx drivers out of the tree. TI does not support the wl12xx drivers in the kernel and in fact they compile but fail at runtime. You need to following the instructions at processors.wiki.ti.com/.../WL12xx_NLCP_Build_Instructions.

For an example to guide you the article at processors.wiki.ti.com/.../WL1835_Cape_on_BeagleBone_with_Debian shows how to build the Robert Nelson kernel for wl18xx using the same principle of a script.

Iain

0 Fabio Martins over 9 years ago in reply to Iain Hunter

Intellectual 315 points

Hello Iain Hunter,

Thank you for your quick reply.

I am sending a picture of the main signals in the scope.

MMC2_WLAN_CMD
MMC2_WLAN_CLK
COMWL_RST

Thanks for the tips, I'll follow these instructions suggested.

Thanks

Fabio

0 Fabio Martins over 9 years ago in reply to Iain Hunter

Intellectual 315 points

Hello Iain

This script will only work for the Kernel before the Device Tree? ( processors.wiki.ti.com/.../WL12xx_NLCP_Build_Instructions. )
If I want to use Device Tree I have to follow the example of the second link that you showed me? ( processors.wiki.ti.com/.../WL1835_Cape_on_BeagleBone_with_Debian ).

Thank you,

Fabio

0 Iain Hunter over 9 years ago in reply to Fabio Martins

TI__Genius 16130 points

Hi Fabio,

The work to port the WL127x (WiLink6) drivers to support device tree has not been done, and in fact will not be done as these drivers are not being maintained. I'd overlooked that fact.

All our development is and has been for a couple of years on wl18xx (Wilink8). Is there a reason why you are developing on Wilink6 rather than WiLink8?

Iain

0 Fabio Martins over 9 years ago in reply to Iain Hunter

Intellectual 315 points

Hi Iain

In fact I used the kit www.ti.com/.../tmdssk3358 as the basis of my project and I heed not me this detail.

Thanks.

Fabio

Wi-Fi

Wi-Fi forum

mmc2: error -22 whilst initialising SDIO card