Message ID | CAOMZO5DvYQRBWmJwXBA_kDG_rt0rpreLzshx+dY_UEttQMSE-g@mail.gmail.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Hi Fabio, On Mon, Nov 18, 2013 at 12:49:27PM -0200, Fabio Estevam wrote: > Hi, > > When I add support to esdhc4 port, which is connected to a eMMC on mx6qsabresd: > > --- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi > +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi > @@ -229,6 +229,10 @@ > pinctrl_usdhc3: usdhc3grp { > fsl,pins = <MX6QDL_USDHC3_PINGRP1>; > }; > + > + pinctrl_usdhc4: usdhc4grp { > + fsl,pins = <MX6QDL_USDHC4_PINGRP1>; > + }; > }; > }; > > @@ -304,3 +308,11 @@ > wp-gpios = <&gpio2 1 0>; > status = "okay"; > }; > + > +&usdhc4 { > + pinctrl-names = "default"; > + pinctrl-0 = <&pinctrl_usdhc4>; > + bus-width = <8>; > + non-removable; > + status = "okay"; > +}; > > I get the following: > > mmc2: Timeout waiting for hardware interrupt. > mmcblk1boot1: unknown partition table > mmc2: Timeout waiting for hardware interrupt. > mmcblk1boot0: unknown partition table > > The boots proceeds until the end, but there is a big delay due to the > above messages. > > Does anything special need to be done in order to support eMMC? > It's already fixed but still not in Chris' tree. Please refer to: http://comments.gmane.org/gmane.linux.kernel.mmc/23339 Regards Dong Aisheng > Regards, > > Fabio Estevam >
--- a/arch/arm/boot/dts/imx6qdl-sabresd.dtsi +++ b/arch/arm/boot/dts/imx6qdl-sabresd.dtsi @@ -229,6 +229,10 @@ pinctrl_usdhc3: usdhc3grp { fsl,pins = <MX6QDL_USDHC3_PINGRP1>; }; + + pinctrl_usdhc4: usdhc4grp { + fsl,pins = <MX6QDL_USDHC4_PINGRP1>; + }; }; }; @@ -304,3 +308,11 @@ wp-gpios = <&gpio2 1 0>; status = "okay"; }; + +&usdhc4 { + pinctrl-names = "default"; + pinctrl-0 = <&pinctrl_usdhc4>; + bus-width = <8>; + non-removable; + status = "okay"; +};