From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: DT include files (was: [GIT PULL 2/2] ARM: imx: device tree changes for 3.14)
Date: Thu, 2 Jan 2014 12:21:08 -0800 [thread overview]
Message-ID: <20140102202108.GF19720@quad.lixom.net> (raw)
In-Reply-To: <20131231054427.GA22383@S2101-09.ap.freescale.net>
Hi,
On Tue, Dec 31, 2013 at 01:44:29PM +0800, Shawn Guo wrote:
> This pull-request has the following two dependencies:
>
> - The first pull-request, i.e. [GIT PULL 1/2] ARM: imx: soc changes for 3.14
>
> - The pinctrl 'devel' branch below.
>
> git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git devel
>
> Linus Walleij promised that the branch will be stable at least from
> the point I pulled into my tree, that is commit 31d610f (pinctrl:
> imx1-core populate subdevices).
>
> Please pull, thanks.
>
> Shawn
>
> .../devicetree/bindings/vendor-prefixes.txt | 3 +
> arch/arm/boot/dts/imx25-pinfunc.h | 494 +++++++++++
> arch/arm/boot/dts/imx25-pingrp.h | 81 ++
> arch/arm/boot/dts/imx27-pinfunc.h | 526 +++++++++++
> arch/arm/boot/dts/imx27-pingrp.h | 151 ++++
> arch/arm/boot/dts/imx35-pingrp.h | 104 +++
> arch/arm/boot/dts/imx50-pinfunc.h | 923 ++++++++++++++++++++
> arch/arm/boot/dts/imx50-pingrp.h | 146 ++++
> arch/arm/boot/dts/imx51-pingrp.h | 249 ++++++
> arch/arm/boot/dts/imx53-pingrp.h | 352 ++++++++
> arch/arm/boot/dts/imx6dl-pinfunc.h | 2 +
> arch/arm/boot/dts/imx6q-pinfunc.h | 2 +
> arch/arm/boot/dts/imx6qdl-pingrp.h | 532 +++++++++++
> arch/arm/boot/dts/imx6sl-pingrp.h | 148 ++++
> arch/arm/boot/dts/vf610-pingrp.h | 127 +++
Hm, these don't quite use include files the way include files were
originally meant to be used -- initially the idea was to use them to
define mostly simple constants instead of full properties like this.
I'm not against the idea of using it this way, but I also want to make sure the
DT maintainers are OK with it. So I've cc:d them on this reply.
I'm also not crazy about the insanely long identifiers used here, but I guess
they correlate with some user manual tables?
-Olof
next prev parent reply other threads:[~2014-01-02 20:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 5:44 [GIT PULL 2/2] ARM: imx: device tree changes for 3.14 Shawn Guo
2014-01-02 20:21 ` Olof Johansson [this message]
2014-01-03 2:32 ` DT include files (was: [GIT PULL 2/2] ARM: imx: device tree changes for 3.14) Shawn Guo
2014-01-03 2:41 ` Olof Johansson
2014-01-03 3:04 ` Shawn Guo
2014-01-03 19:29 ` Olof Johansson
2014-01-04 1:10 ` Shawn Guo
2014-01-10 2:41 ` Shawn Guo
2014-01-10 2:41 ` Olof Johansson
2014-01-10 13:28 ` DT include files Tomasz Figa
2014-01-10 15:30 ` Rob Herring
2014-01-10 17:03 ` Gerhard Sittig
2014-01-13 16:48 ` Stephen Warren
2014-01-13 18:10 ` Gerhard Sittig
2014-01-10 18:37 ` Olof Johansson
2014-01-11 3:12 ` Shawn Guo
2014-01-11 13:15 ` Arnd Bergmann
2014-01-12 3:25 ` Shawn Guo
2014-01-12 20:21 ` Arnd Bergmann
2014-01-12 23:16 ` Linus Walleij
2014-01-13 2:31 ` Shawn Guo
2014-01-13 2:19 ` Shawn Guo
2014-01-24 8:02 ` Heiko Stübner
2014-01-25 2:25 ` Shawn Guo
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=20140102202108.GF19720@quad.lixom.net \
--to=olof@lixom.net \
--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).