From: Shawn Guo <shawn.guo-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
To: "Lothar Waßmann" <LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
Cc: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-arm-kernel-bounces-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>,
Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Subject: Re: [PATCH RESEND 0/3] ARM: dts: mxs: add pinctrl header files
Date: Sun, 22 Sep 2013 14:11:43 +0800 [thread overview]
Message-ID: <20130922061140.GA31787@S2101-09.ap.freescale.net> (raw)
In-Reply-To: <1379573990-27556-1-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
On Thu, Sep 19, 2013 at 08:59:46AM +0200, Lothar Waßmann wrote:
> These patches add header files for the MXS arch and convert the DTS
> files to use the pad definitions from those files rather than
> hardcoding the numerical 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 (equivalent to 0x2133) in the comment,
> but actually was using MX28_PAD_SSP2_SS0__AUART3_TX by the numerical
> value 0x2131.
>
> I decided to use the (possibly unintended) assignment
> MX28_PAD_SSP2_SS0__AUART3_TX because that is what is actually
> configured without this patch.
Applied these 3 patches, thanks.
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2013-09-22 6:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 6:59 [PATCH RESEND 0/3] ARM: dts: mxs: add pinctrl header files Lothar Waßmann
[not found] ` <1379573990-27556-1-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
2013-09-19 6:59 ` [PATCH RESEND 1/3] " Lothar Waßmann
2013-09-19 6:59 ` [PATCH RESEND 2/3] ARM: dts: mxs: modify mx23/mx28 dts files to use pinctrl headers Lothar Waßmann
2013-09-19 6:59 ` [PATCH RESEND 3/3] ARM: dts: mxs: modify mx23/mx28 dts files to use padconfig defines Lothar Waßmann
2013-09-19 6:59 ` [PATCH RESEND] ARM: dts: tx28: restructure and update DTS file Lothar Waßmann
[not found] ` <1379573990-27556-5-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
2013-09-22 6:41 ` Shawn Guo
[not found] ` <20130922064124.GB31787-rvtDTF3kK1ictlrPMvKcciBecyulp+rMXqFh9Ls21Oc@public.gmane.org>
2013-09-23 9:37 ` Lothar Waßmann
2013-09-23 10:20 ` [PATCH v4] " Lothar Waßmann
[not found] ` <1379931648-12448-1-git-send-email-LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org>
2013-09-24 14:27 ` Shawn Guo
2013-09-22 6:11 ` Shawn Guo [this message]
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=20130922061140.GA31787@S2101-09.ap.freescale.net \
--to=shawn.guo-qsej5fyqhm4dnm+yrofe0a@public.gmane.org \
--cc=LW-bxm8fMRDkQLDiMYJYoSAnRvVK+yQ3ZXh@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-arm-kernel-bounces-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org \
--cc=swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.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