> diff --git a/arch/arm/boot/dts/omap4.dtsi b/arch/arm/boot/dts/omap4.dtsi
> index 29f4589..9204f60 100644
> --- a/arch/arm/boot/dts/omap4.dtsi
> +++ b/arch/arm/boot/dts/omap4.dtsi
> @@ -25,6 +25,11 @@
> serial1 = &uart2;
> serial2 = &uart3;
> serial3 = &uart4;
> + mmc1 = &mmc1;
> + mmc2 = &mmc2;
> + mmc3 = &mmc3;
> + mmc4 = &mmc4;
> + mmc5 = &mmc5;
> };
>
> cpus {
> @@ -155,5 +160,31 @@
> #size-cells = <0>;
> ti,hwmods = "i2c4";
> };
> +
> + mmc1: mmc@1 {
> + compatible = "ti,omap4-hsmmc";
> + ti,hwmods = "mmc1";
> + ti,dual-volt;
> + };
> +
> + mmc2: mmc@2 {
> + compatible = "ti,omap4-hsmmc";
> + ti,hwmods = "mmc2";
> + };
Hi Rajendra,
Is there a way to control the device registration order,
eMMC connected to mmc2 needs to be registered as /dev/mmcblk0p ...
irrespective of whether SD card is mount or not on mmc1 card slot.
So that bootargs would not have to be modified when filesystem is on eMMC.
> +
> + mmc3: mmc@3 {
> + compatible = "ti,omap4-hsmmc";
> + ti,hwmods = "mmc3";
> + };
> +
> + mmc4: mmc@4 {
> + compatible = "ti,omap4-hsmmc";
> + ti,hwmods = "mmc4";
> + };
> +
> + mmc5: mmc@5 {
> + compatible = "ti,omap4-hsmmc";
> + ti,hwmods = "mmc5";
> + };
> };
> };
> --
> 1.7.1
>
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
