Re: [PATCH v3 1/2] ARM: dts: imx25-pinfunc: Use consistent naming for eSDHC

2018-02-05 Thread Shawn Guo
On Wed, Jan 31, 2018 at 10:35:43PM +0100, Benoît Thébaudeau wrote: > This file had several naming inconsistencies for eSDHC: > - the instances were named sometimes SDn, sometimes SDHCn, whereas they >are named ESDHCn in the reference manual, e.g.: > MX25_PAD_SD1_CMD__SD1_CMD > MX25_P

Re: [PATCH v3 1/2] ARM: dts: imx25-pinfunc: Use consistent naming for eSDHC

2018-02-04 Thread Rob Herring
On Wed, Jan 31, 2018 at 10:35:43PM +0100, Benoît Thébaudeau wrote: > This file had several naming inconsistencies for eSDHC: > - the instances were named sometimes SDn, sometimes SDHCn, whereas they >are named ESDHCn in the reference manual, e.g.: > MX25_PAD_SD1_CMD__SD1_CMD > MX25_P

Re: [PATCH v3 1/2] ARM: dts: imx25-pinfunc: Use consistent naming for eSDHC

2018-01-31 Thread Fabio Estevam
On Wed, Jan 31, 2018 at 7:35 PM, Benoît Thébaudeau wrote: > This file had several naming inconsistencies for eSDHC: > - the instances were named sometimes SDn, sometimes SDHCn, whereas they >are named ESDHCn in the reference manual, e.g.: > MX25_PAD_SD1_CMD__SD1_CMD > MX25_PAD_D15__

[PATCH v3 1/2] ARM: dts: imx25-pinfunc: Use consistent naming for eSDHC

2018-01-31 Thread Benoît Thébaudeau
This file had several naming inconsistencies for eSDHC: - the instances were named sometimes SDn, sometimes SDHCn, whereas they are named ESDHCn in the reference manual, e.g.: MX25_PAD_SD1_CMD__SD1_CMD MX25_PAD_D15__SDHC1_DAT7 - the data ports were named sometimes DATAn, sometimes DA