From mboxrd@z Thu Jan 1 00:00:00 1970 From: marex@denx.de (Marek Vasut) Date: Fri, 13 Dec 2013 12:48:32 +0100 Subject: [PATCH V1 05/11] ARM: dts: imx6qdl-sabrelite: specify pad settings In-Reply-To: <1386899355-17379-6-git-send-email-troy.kisky@boundarydevices.com> References: <1386899355-17379-1-git-send-email-troy.kisky@boundarydevices.com> <1386899355-17379-6-git-send-email-troy.kisky@boundarydevices.com> Message-ID: <201312131248.32208.marex@denx.de> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Friday, December 13, 2013 at 02:49:09 AM, Troy Kisky wrote: > Don't use 0x80000000 to get default pad settings. What is the rationale behind this change please? Can you explain more in detail? > Signed-off-by: Troy Kisky > --- > arch/arm/boot/dts/imx6qdl-sabrelite.dtsi | 14 +++++++------- > 1 file changed, 7 insertions(+), 7 deletions(-) > > diff --git a/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi > b/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi index be899d3..b548647 100644 > --- a/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi > +++ b/arch/arm/boot/dts/imx6qdl-sabrelite.dtsi > @@ -114,13 +114,13 @@ > imx6q-sabrelite { > pinctrl_hog: hoggrp { > fsl,pins = < > -/* uSDHC4 CD */ MX6QDL_PAD_NANDF_D6__GPIO2_IO06 0x80000000 > -/* spi-nor CS */ MX6QDL_PAD_EIM_D19__GPIO3_IO19 0x80000000 > -/* otg power en */ MX6QDL_PAD_EIM_D22__GPIO3_IO22 0x80000000 > -/* ethernet phy reset */ MX6QDL_PAD_EIM_D23__GPIO3_IO23 0x80000000 > -/* USDHC3 CD */ MX6QDL_PAD_SD3_DAT5__GPIO7_IO00 0x80000000 > -/* USDHC3 WP */ MX6QDL_PAD_SD3_DAT4__GPIO7_IO01 0x1f0b0 > -/* SGTL5000 sys_mclk */ MX6QDL_PAD_GPIO_0__CCM_CLKO1 0x80000000 > +/* uSDHC4 CD */ MX6QDL_PAD_NANDF_D6__GPIO2_IO06 0x1b0b0 > +/* spi-nor CS */ MX6QDL_PAD_EIM_D19__GPIO3_IO19 0x1b0b0 > +/* otg power en */ MX6QDL_PAD_EIM_D22__GPIO3_IO22 0x1b0b0 > +/* ethernet phy reset */ MX6QDL_PAD_EIM_D23__GPIO3_IO23 0x000b0 > +/* USDHC3 CD */ MX6QDL_PAD_SD3_DAT5__GPIO7_IO00 0x1b0b0 > +/* USDHC3 WP */ MX6QDL_PAD_SD3_DAT4__GPIO7_IO01 0x1f0b0 > +/* SGTL5000 sys_mclk */ MX6QDL_PAD_GPIO_0__CCM_CLKO1 0x000b0 > > >; > > }; Best regards, Marek Vasut