From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King - ARM Linux Subject: Re: [PATCH RFC 1/2] ARM: imx6qdl: provide pinctrl configurations for DAT3 pull-down Date: Mon, 7 Oct 2013 19:03:57 +0100 Message-ID: <20131007180357.GS12758@n2100.arm.linux.org.uk> References: <20131005112147.GX12758@n2100.arm.linux.org.uk> <20131007055340.GB3739@S2101-09.ap.freescale.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20131007055340.GB3739-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org> Sender: devicetree-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Shawn Guo Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Mark Rutland , Ian Campbell , Pawel Moll , Rob Herring , Stephen Warren List-Id: devicetree@vger.kernel.org On Mon, Oct 07, 2013 at 01:53:43PM +0800, Shawn Guo wrote: > I think we can redefine only pad DAT3 in pinctrl_usdhc1_1_dat3cd, and > overwrite the DAT3 configuration in pinctrl_usdhc1_1 to save the > redundant data of other pads, something like the following. > > pinctrl_usdhc1_1_dat3cd: usdhc1grp-3 { > fsl,pins = < > MX6QDL_PAD_SD1_DAT3__SD1_DATA3 0x13059 > >; > }; > > &usdhc1 { > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_usdhc1_1 &pinctrl_usdhc1_1_dat3cd>; > ... > status = "okay"; > }; Are you sure that this will always be the case? This would assume that the pinctrl entries are always processed sequentially. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html