From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/9] ARM: dts: imx6sl: remove the use of pingrp macros
Date: Tue, 28 Jan 2014 11:17:22 +0100 [thread overview]
Message-ID: <5923680.sl3G3EgCsY@phil> (raw)
In-Reply-To: <1390668191-20289-3-git-send-email-shawn.guo@linaro.org>
Hi Shawn,
On Sunday, 26. January 2014 00:43:04 Shawn Guo wrote:
> We created the pingrp macros in imx6sl-pingrp.h for purpose of less LOC
> when same pin group is used by multiple boards. However, DT maintainers
> take it as an abuse of DTC macro support. So let's get rid of it to
> make the pins used by given device more intuitive.
>
> Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> ---
> arch/arm/boot/dts/imx6sl-evk.dts | 120 ++++++++++++++++++++++++++----
> arch/arm/boot/dts/imx6sl-pingrp.h | 148
> ------------------------------------- arch/arm/boot/dts/imx6sl.dtsi |
> 1 -
> 3 files changed, 107 insertions(+), 162 deletions(-)
> delete mode 100644 arch/arm/boot/dts/imx6sl-pingrp.h
>
> diff --git a/arch/arm/boot/dts/imx6sl-evk.dts
> b/arch/arm/boot/dts/imx6sl-evk.dts index f5e4513..8594d13 100644
> --- a/arch/arm/boot/dts/imx6sl-evk.dts
> +++ b/arch/arm/boot/dts/imx6sl-evk.dts
> @@ -86,55 +86,149 @@
> };
>
> pinctrl_ecspi1: ecspi1grp {
> - fsl,pins = <MX6SL_ECSPI1_PINGRP1>;
> + fsl,pins = <
> + MX6SL_PAD_ECSPI1_MISO__ECSPI1_MISO 0x100b1
> + MX6SL_PAD_ECSPI1_MOSI__ECSPI1_MOSI 0x100b1
> + MX6SL_PAD_ECSPI1_SCLK__ECSPI1_SCLK 0x100b1
> + >;
> };
>
> pinctrl_fec: fecgrp {
> - fsl,pins = <MX6SL_FEC_PINGRP1>;
> + fsl,pins = <
> + MX6SL_PAD_FEC_MDC__FEC_MDC 0x1b0b0
> + MX6SL_PAD_FEC_MDIO__FEC_MDIO 0x1b0b0
> + MX6SL_PAD_FEC_CRS_DV__FEC_RX_DV 0x1b0b0
> + MX6SL_PAD_FEC_RXD0__FEC_RX_DATA0 0x1b0b0
> + MX6SL_PAD_FEC_RXD1__FEC_RX_DATA1 0x1b0b0
> + MX6SL_PAD_FEC_TX_EN__FEC_TX_EN 0x1b0b0
> + MX6SL_PAD_FEC_TXD0__FEC_TX_DATA0 0x1b0b0
> + MX6SL_PAD_FEC_TXD1__FEC_TX_DATA1 0x1b0b0
> + MX6SL_PAD_FEC_REF_CLK__FEC_REF_OUT 0x4001b0a8
> + >;
> };
[... and so on for the other groups ... ]
I'm confused now :-) . Current linux-next [0] shows the pin-settings as part
of imx6sl.dtsi - a way a lot of other architectures organize their pingroups
too, with the board file only referencing the relevant pingroups from the
predefined ones of the soc.
So I guess your move to the pingrp-header moved them out of the imx6sl.dtsi to
the .h and is not part of linux-next; but this patch (and the others in this
series) now moves the definitions into the individual board files. Can't you
just move them back to the soc-dtsi files to prevent each board duplicating
them?
Or I've simply missed previous discussions about this ;-) .
Thanks
Heiko
[0] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/arch/arm/boot/dts/imx6sl.dtsi#n640
next prev parent reply other threads:[~2014-01-28 10:17 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 16:43 [PATCH 0/9] ARM: dts: imx: remove the use of pingrp macros Shawn Guo
2014-01-25 16:43 ` [PATCH 1/9] ARM: dts: imx6qdl: " Shawn Guo
2014-01-27 14:37 ` Russell King - ARM Linux
2014-01-27 15:05 ` Shawn Guo
2014-01-27 15:16 ` Russell King - ARM Linux
2014-01-27 15:22 ` Shawn Guo
2014-01-28 10:30 ` Shawn Guo
2014-01-25 16:43 ` [PATCH 2/9] ARM: dts: imx6sl: " Shawn Guo
2014-01-28 10:17 ` Heiko Stübner [this message]
2014-01-28 11:03 ` Sascha Hauer
2014-01-28 11:20 ` Shawn Guo
2014-01-29 10:42 ` Heiko Stübner
2014-01-25 16:43 ` [PATCH 3/9] ARM: dts: imx53: " Shawn Guo
2014-01-25 16:43 ` [PATCH 4/9] ARM: dts: imx51: " Shawn Guo
2014-01-25 16:43 ` [PATCH 5/9] ARM: dts: imx50: " Shawn Guo
2014-01-25 16:43 ` [PATCH 6/9] ARM: dts: imx35: " Shawn Guo
2014-01-25 16:43 ` [PATCH 7/9] ARM: dts: imx25: " Shawn Guo
2014-01-25 16:43 ` [PATCH 8/9] ARM: dts: imx27: " Shawn Guo
2014-01-25 16:43 ` [PATCH 9/9] ARM: dts: vf610: " Shawn Guo
2014-01-27 14:04 ` [PATCH 0/9] ARM: dts: imx: " Rob Herring
2014-01-27 17:47 ` Olof Johansson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5923680.sl3G3EgCsY@phil \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).