AnsweredAssumed Answered

Can't find SDIO WIFI device on imx6ul

Question asked by Wu on May 17, 2018
Latest reply on May 17, 2018 by igorpadykov

Hi,

 

I have a custom board with the RTL8189ES wifi module based on imx6ul evk board.

The WIFI module connenct the custom board via SDIO.

The system can't find SDIO device when the system start.

The boot log as below:

sdhci: Secure Digital Host Controller Interface driver
[ 1.915328] sdhci: Copyright(c) Pierre Ossman
[ 1.919718] sdhci-pltfm: SDHCI platform and OF driver helper
[ 1.927607] sdhci-esdhc-imx 2190000.usdhc: none removable!
[ 1.933568] mmc0: no vqmmc regulator found
[ 1.983106] mmc0: SDHCI controller on 2190000.usdhc [2190000.usdhc] using ADMA
[ 1.990402] mmc0: mmc_rescan_try_freq: trying to init card at 400000 Hz
[ 1.998350] sdhci-esdhc-imx 2194000.usdhc: none removable!
[ 2.005338] mmc1: no vqmmc regulator found
[ 2.009475] mmc1: no vmmc regulator found
[ 2.065894] mmc1: SDHCI controller on 2194000.usdhc [2194000.usdhc] using ADMA

...........................

[ 2.315065] Waiting for root device /dev/mmcblk0p2...
[ 2.471278] mmc0: host does not support reading read-only switch. assuming write-enable.
[ 2.483658] mmc0: new SD card at address e33b
[ 2.490340] mmcblk0: mmc0:e33b SD01G 982 MiB
[ 2.498602] mmcblk0: p1 p2
[ 2.505054] mmc1: mmc_rescan_try_freq: trying to init card at 400000 Hz
[ 2.565829] kjournald starting. Commit interval 5 seconds
[ 2.586689] mmc1: mmc_rescan_try_freq: trying to init card at 300000 Hz
[ 2.639949] EXT3-fs (mmcblk0p2): using internal journal
[ 2.646374] EXT3-fs (mmcblk0p2): mounted filesystem with ordered data mode
[ 2.656605] VFS: Mounted root (ext3 filesystem) on device 179:2.
[ 2.675007] devtmpfs: mounted
[ 2.678780] Freeing unused kernel memory: 384K (809c8000 - 80a28000)
[ 2.722361] mmc1: mmc_rescan_try_freq: trying to init card at 200000 Hz
[ 2.839274] mmc1: mmc_rescan_try_freq: trying to init card at 100000 Hz

The device tree as below:

 

&usdhc2 {
pinctrl-names = "default", "state_100mhz", "state_200mhz";
pinctrl-0 = <&pinctrl_usdhc2>;
pinctrl-1 = <&pinctrl_usdhc2_100mhz>;
pinctrl-2 = <&pinctrl_usdhc2_200mhz>;
non-removable;
keep-power-in-suspend;
enable-sdio-wakeup;
status = "okay";
};

 

pinctrl_usdhc2: usdhc2grp {
fsl,pins = <
MX6UL_PAD_LCD_DATA19__USDHC2_CLK 0x10069
MX6UL_PAD_LCD_DATA18__USDHC2_CMD 0x17059
MX6UL_PAD_LCD_DATA20__USDHC2_DATA0 0x17059
MX6UL_PAD_LCD_DATA21__USDHC2_DATA1 0x17059
MX6UL_PAD_LCD_DATA22__USDHC2_DATA2 0x17059
MX6UL_PAD_LCD_DATA23__USDHC2_DATA3 0x17059
>;
};

 

pinctrl_usdhc2_100mhz: usdhc2grp100mhz {
fsl,pins = <
MX6UL_PAD_LCD_DATA19__USDHC2_CLK 0x100b9
MX6UL_PAD_LCD_DATA18__USDHC2_CMD 0x170b9
MX6UL_PAD_LCD_DATA20__USDHC2_DATA0 0x170b9
MX6UL_PAD_LCD_DATA21__USDHC2_DATA1 0x170b9
MX6UL_PAD_LCD_DATA22__USDHC2_DATA2 0x170b9
MX6UL_PAD_LCD_DATA23__USDHC2_DATA3 0x170b9
>;
};

pinctrl_usdhc2_200mhz: usdhc2grp200mhz {
fsl,pins = <
MX6UL_PAD_LCD_DATA19__USDHC2_CLK 0x100f9
MX6UL_PAD_LCD_DATA18__USDHC2_CMD 0x170f9
MX6UL_PAD_LCD_DATA20__USDHC2_DATA0 0x170f9
MX6UL_PAD_LCD_DATA21__USDHC2_DATA1 0x170f9
MX6UL_PAD_LCD_DATA22__USDHC2_DATA2 0x170f9
MX6UL_PAD_LCD_DATA23__USDHC2_DATA3 0x170f9
>;
};

I  didn't the root cause, could you help me for this issue.

 

 

Thanks.

Outcomes