From: "Lothar Waßmann" <LW@KARO-electronics.de>
To: devicetree@vger.kernel.org
Cc: Shawn Guo <shawn.guo@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Stephen Warren <swarren@wwwdotorg.org>
Subject: [PATCH v2 1/3] ARM: dts: mxs: add pinctrl header files
Date: Mon, 2 Sep 2013 15:03:53 +0200 [thread overview]
Message-ID: <1378127036-24861-1-git-send-email-LW@KARO-electronics.de> (raw)
In-Reply-To: <20130812072957.GB25061@S2101-09.ap.freescale.net>
Changes vs. v2:
- move header files to arch/arm/boot/dts
- update documentation file to use the defined names rather than
numeric values and remove the pinmux-id list
These patches add header files for the MXS arch to
arch/arm/boot/dts and convert the DTS files to use the pad
definitions from thoose files rather than hardcoding the pinctrl
values.
The conversion from numerical representation to symbolic names has
been done with a perl script that checked the definitions for
consistency of the pin function comments and the numerical values
used.
This revealed an inconsistency in:
arch/arm/boot/dts/imx28-apx4devkit.dts, which pretended to use
MX28_PAD_SSP2_SS0__GPIO_2_19 in the comment (equivalent to 0x2133),
but actually was using MX28_PAD_SSP2_SS0__AUART3_TX by the numerical
value 0x2131.
I decided to use the (probably wrong) assignment
MX28_PAD_SSP2_SS0__AUART3_TX because that is what is actually
configured without this patch. A comment stating the old setup has
been added to the .dts file.
next parent reply other threads:[~2013-09-02 13:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130812072957.GB25061@S2101-09.ap.freescale.net>
2013-09-02 13:03 ` Lothar Waßmann [this message]
2013-09-04 2:21 ` [PATCH v2 1/3] ARM: dts: mxs: add pinctrl header files Shawn Guo
2013-09-05 9:14 ` Lothar Waßmann
2013-09-06 8:42 ` Shawn Guo
2013-09-07 3:28 ` Shawn Guo
2013-09-02 13:03 ` [PATCH " Lothar Waßmann
2013-09-02 13:03 ` [PATCH 2/3] ARM: dts: mxs: modify mx23/mx28 dts files to use pinctrl headers Lothar Waßmann
2013-09-02 13:03 ` [PATCH 3/3] ARM: dts: mxs: modify mx23/mx28 dts files to use padconfig defines Lothar Waßmann
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=1378127036-24861-1-git-send-email-LW@KARO-electronics.de \
--to=lw@karo-electronics.de \
--cc=devicetree@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.org \
--cc=swarren@wwwdotorg.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