23 Jan
2013
23 Jan
'13
7:02 p.m.
On Wed, Jan 23, 2013 at 12:54 PM, Otavio Salvador otavio@ossystems.com.br wrote:
/* MMC 0 */MX23_PAD_SSP1_DATA0__SSP1_DATA0 | MUX_CONFIG_SSP1,MX23_PAD_SSP1_DATA1__SSP1_DATA1 | MUX_CONFIG_SSP1,MX23_PAD_SSP1_DATA2__SSP1_DATA2 | MUX_CONFIG_SSP1,MX23_PAD_SSP1_DATA3__SSP1_DATA3 | MUX_CONFIG_SSP1,MX23_PAD_GPMI_D08__SSP1_DATA4 | MUX_CONFIG_SSP1,MX23_PAD_GPMI_D09__SSP1_DATA5 | MUX_CONFIG_SSP1,MX23_PAD_GPMI_D10__SSP1_DATA6 | MUX_CONFIG_SSP1,MX23_PAD_GPMI_D11__SSP1_DATA7 | MUX_CONFIG_SSP1,MX23_PAD_SSP1_CMD__SSP1_CMD | MUX_CONFIG_SSP1,MX23_PAD_SSP1_DETECT__SSP1_DETECT | MUX_CONFIG_SSP1,
In order to avoid pin conflicts in the future, in case we add splash screen support, I would suggest you to use only 4-bit MMC mode.
Please look at imx23-evk.dts in Linux to understand how this is done, especially this commit:
commit 72beabae635b9485510ccf8093df319f59eb6688 Author: Shawn Guo shawn.guo@linaro.org Date: Thu Jun 28 11:44:59 2012 +0800
ARM: dts: imx23-evk: updates for mmc device
The 8-bit mode mmc has pin conflicts with display. Let's use 4-bit mode by default, so that display can be enabled together later.
Also add vmmc-supply for mmc device.
Signed-off-by: Shawn Guo shawn.guo@linaro.org