From: Markus Pargmann <mpa@pengutronix.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: devicetree@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Sascha Hauer <kernel@pengutronix.de>,
Grant Likely <grant.likely@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/7] pinctrl: imx27: imx27 pincontrol driver
Date: Sat, 31 Aug 2013 08:49:40 +0200 [thread overview]
Message-ID: <20130831064940.GW20071@s25.your-server.de> (raw)
In-Reply-To: <20130821012301.GA30533@S2101-09.ap.freescale.net>
On Wed, Aug 21, 2013 at 09:23:03AM +0800, Shawn Guo wrote:
> On Mon, Aug 19, 2013 at 04:07:09PM +0200, Markus Pargmann wrote:
> > imx27 pincontrol driver using the imx1 core driver. The DT bindings are
> > similar to other imx pincontrol drivers.
> >
> > Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> > ---
> > .../bindings/pinctrl/fsl,imx27-pinctrl.txt | 53 +++
> > drivers/pinctrl/Kconfig | 8 +
> > drivers/pinctrl/Makefile | 1 +
> > drivers/pinctrl/pinctrl-imx27.c | 477 +++++++++++++++++++++
> > 4 files changed, 539 insertions(+)
> > create mode 100644 Documentation/devicetree/bindings/pinctrl/fsl,imx27-pinctrl.txt
> > create mode 100644 drivers/pinctrl/pinctrl-imx27.c
> >
> > diff --git a/Documentation/devicetree/bindings/pinctrl/fsl,imx27-pinctrl.txt b/Documentation/devicetree/bindings/pinctrl/fsl,imx27-pinctrl.txt
> > new file mode 100644
> > index 0000000..016fc89
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/pinctrl/fsl,imx27-pinctrl.txt
> > @@ -0,0 +1,53 @@
> > +* Freescale IMX27 IOMUX Controller
> > +
> > +Please refer to fsl,imx-pinctrl.txt in this directory for common binding part
> > +and usage.
>
> Since imx-pinctrl and imx1-pinctrl are now two completely different
> drivers/bindings, is there actually anything from fsl,imx-pinctrl.txt
> could be referred to here?
No, fixed, thanks.
Regards,
Markus
>
> Shawn
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2013-08-31 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1376921234-26682-1-git-send-email-mpa@pengutronix.de>
[not found] ` <1376921234-26682-2-git-send-email-mpa@pengutronix.de>
[not found] ` <20130820125614.GE29114@S2101-09.ap.freescale.net>
2013-08-30 12:17 ` [PATCH v2 1/7] pinctrl: imx1 core driver Markus Pargmann
[not found] ` <1376921234-26682-5-git-send-email-mpa@pengutronix.de>
[not found] ` <20130820071411.GI31036@pengutronix.de>
2013-08-31 6:29 ` [PATCH v2 4/7] ARM: dts: imx27 pinctrl Markus Pargmann
[not found] ` <20130821013035.GB30533@S2101-09.ap.freescale.net>
2013-08-31 6:31 ` Markus Pargmann
[not found] ` <1376921234-26682-3-git-send-email-mpa@pengutronix.de>
[not found] ` <20130821012301.GA30533@S2101-09.ap.freescale.net>
2013-08-31 6:49 ` Markus Pargmann [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=20130831064940.GW20071@s25.your-server.de \
--to=mpa@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=rob.herring@calxeda.com \
--cc=shawn.guo@linaro.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