public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Markus Pargmann <mpa@pengutronix.de>
To: Shawn Guo <shawn.guo@linaro.org>,
	Sascha Hauer <kernel@pengutronix.de>,
	Grant Likely <grant.likely@linaro.org>,
	Rob Herring <rob.herring@calxeda.com>,
	Linus Walleij <linus.walleij@linaro.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 4/7] ARM: dts: imx27 pinctrl
Date: Sat, 31 Aug 2013 08:29:37 +0200	[thread overview]
Message-ID: <20130831062937.GU20071@s25.your-server.de> (raw)
In-Reply-To: <20130820071411.GI31036@pengutronix.de>

Hi Sascha,

On Tue, Aug 20, 2013 at 09:14:11AM +0200, Sascha Hauer wrote:
> On Mon, Aug 19, 2013 at 04:07:11PM +0200, Markus Pargmann wrote:
> > Pinctrl driver node and pin group definitions for other driver nodes.
> > 
> > Signed-off-by: Markus Pargmann <mpa@pengutronix.de>
> > ---
> > +					pinctrl_uart_1: uart-1 {
> > +						fsl,pins = <
> > +							MX27_PAD_UART1_TXD__UART1_TXD 0x0
> > +							MX27_PAD_UART1_RXD__UART1_RXD 0x0
> > +							MX27_PAD_UART1_CTS__UART1_CTS 0x0
> > +							MX27_PAD_UART1_RTS__UART1_RTS 0x0
> > +						>;
> > +					};
> 
> The above either misses a group number or an uart number. We need
> pinctrl_uart<uartno>_<groupno>

Fixed.

> 
> Also this doesn't scale very good. For boards without RTS/CTS we would have
> to add a completely different group. For the FEC I've seen different
> groups with a dozen pins each which differ in only a single pin.
> 
> I therefore suggest (and Shawn acked the general idea already) to
> do this:
> 
> 	pinctrl_uart1_1: uart1-1 {
> 		fsl,pins = <
> 			MX27_PAD_UART1_TXD__UART1_TXD 0x0
> 			MX27_PAD_UART1_RXD__UART1_RXD 0x0
> 		>;
> 	};
> 
> 	pinctrl_uart1_rtscts_1: uart1-rtscts-1 {
> 		fsl,pins = <
> 			MX27_PAD_UART1_CTS__UART1_CTS 0x0
> 			MX27_PAD_UART1_RTS__UART1_RTS 0x0
> 		>;
> 	};

I changed the uart groups accordingly.

Thanks,

Markus

-- 
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 |

  parent reply	other threads:[~2013-08-31  6:29 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     ` Markus Pargmann [this message]
     [not found]   ` <20130821013035.GB30533@S2101-09.ap.freescale.net>
2013-08-31  6:31     ` [PATCH v2 4/7] ARM: dts: imx27 pinctrl 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     ` [PATCH v2 2/7] pinctrl: imx27: imx27 pincontrol driver Markus Pargmann

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=20130831062937.GU20071@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