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: Wed, 29 Jan 2014 11:42:11 +0100 [thread overview]
Message-ID: <8644666.oTYOihNRNU@phil> (raw)
In-Reply-To: <20140128112047.GC20583@S2101-09.ap.freescale.net>
On Tuesday, 28. January 2014 19:20:49 Shawn Guo wrote:
> On Tue, Jan 28, 2014 at 11:17:22AM +0100, Heiko St?bner wrote:
> > [... 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;
>
> Yes, my for-next branch was excluded from linux-next temporarily for
> some reason. I will ask Stephen to add it back once v3.14-rc1 is out.
> That said, you can see nothing we developed in this cycle on linux-next
> for now.
>
> > 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?
>
> No. That will bring back the problem we try to solve from the
> beginning [1].
>
> [1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/275912/
Thanks for the pointer, I think I understand the issue now :-) .
So for the short term, I should probably also define the pingroups in my board-
dts then.
But as an insane idea that I just had, because the issue will probably affect
more architectures at some point when their pingroups or other common-nodes
grow, how about introducing something like a "/delete-if-unreferenced/" prefix
in dtc?
As I could see in [0], adding something to dtc is not as far off as I thought.
In essence one would add the pingroups to the soc dtsi, like
ecspi1 {
/delete-if-unreferenced/ pinctrl_ecspi1_1: ecspi1grp-1 {
fsl,pins = <
MX6SL_PAD_ECSPI1_MISO__ECSPI1_MISO 0x100b1
MX6SL_PAD_ECSPI1_MOSI__ECSPI1_MOSI 0x100b1
MX6SL_PAD_ECSPI1_SCLK__ECSPI1_SCLK 0x100b1
>;
};
};
and dtc would then be tasked with checking if the node gets referenced in a
phandle somewhere in the dts and if not removing it.
I don't know if this is at all sane to think about or doable in dtc.
Heiko
[0] http://www.spinics.net/lists/arm-kernel/msg300936.html
next prev parent reply other threads:[~2014-01-29 10:42 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
2014-01-28 11:03 ` Sascha Hauer
2014-01-28 11:20 ` Shawn Guo
2014-01-29 10:42 ` Heiko Stübner [this message]
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=8644666.oTYOihNRNU@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).