On Thu, Mar 26, 2015 at 05:38:24PM +0000, Ben Dooks wrote:
> The SAM5D3 Xplained device tree is missing hte vqmmc node which is
> tied to 3.3V on the board. Add this to avoid the kernel warning that
> there is no vqmmc node.
> 
> atmel_mci f0000000.mmc: No vqmmc regulator found
> 
> Signed-off-by: Ben Dooks <[email protected]>
> --
> CC: [email protected]
> CC: Andrew Victor <[email protected]>
> CC: Nicolas Ferre <[email protected]>
> CC: Jean-Christophe Plagniol-Villard <[email protected]>
> CC: Rob Herring <[email protected]>
> CC: Pawel Moll <[email protected]>
> CC: Mark Rutland <[email protected]>
> CC: Ian Campbell <[email protected]>
> CC: Kumar Gala <[email protected]>
> CC: Russell King <[email protected]>
> CC: [email protected]
> CC: [email protected]
> ---
>  arch/arm/boot/dts/at91-sama5d3_xplained.dts | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm/boot/dts/at91-sama5d3_xplained.dts 
> b/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> index 652c4dd..1eb150d 100644
> --- a/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> +++ b/arch/arm/boot/dts/at91-sama5d3_xplained.dts
> @@ -36,6 +36,7 @@
>                       mmc0: mmc@f0000000 {
>                               pinctrl-0 = <&pinctrl_mmc0_clk_cmd_dat0 
> &pinctrl_mmc0_dat1_3 &pinctrl_mmc0_dat4_7 &pinctrl_mmc0_cd>;
>                               status = "okay";
> +                             vqmmc-supply = <&vcc_3v3_reg>;

above status would be better, usually we keep status at the latest
property even if in this cas we have slot after... Otherwise

Acked-by: Ludovic Desroches <[email protected]>

>                               slot@0 {
>                                       reg = <0>;
>                                       bus-width = <8>;
> -- 
> 2.1.4
> 
> 
> _______________________________________________
> linux-arm-kernel mailing list
> [email protected]
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to