linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/4 v4] drivers: create a pin control subsystem
Date: Thu, 25 Aug 2011 14:07:45 +0200	[thread overview]
Message-ID: <20110825120745.GV31404@pengutronix.de> (raw)
In-Reply-To: <CACRpkdbV_Hgj=x5J3wYCtPcnZ++xMCqY91J2_i75c0G8OtYk5A@mail.gmail.com>

On Thu, Aug 25, 2011 at 01:58:12PM +0200, Linus Walleij wrote:
> On Thu, Aug 25, 2011 at 1:04 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> > Not really. UART2_CTS can't be routed to arbitrary pads, but it can be
> > routed to more than one pad:
> >
> > #define _MX51_PAD_EIM_D16__UART2_CTS ? ? ? ? ? ?IOMUX_PAD(0x3f0, 0x5c, 3, 0x0000, 0, 0)
> > #define _MX51_PAD_EIM_D25__UART2_CTS ? ? ? ? ? ?IOMUX_PAD(0x414, 0x80, 4, 0x0000, 0, 0)
> > #define _MX51_PAD_USBH1_DATA0__UART2_CTS ? ? ? ?IOMUX_PAD(0x688, 0x288, 1, 0x0000, 0, 0)
> 
> Aha!
> 
> Is it typically a few pads like this, say 2,3,4 alternatives,
> sometimes just one?
> 
> So the actual relation is not 1..1 nor 1...* but 1..<a few>?

Yes.

Sascha

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

  reply	other threads:[~2011-08-25 12:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-19  9:53 [PATCH 1/4 v4] drivers: create a pin control subsystem Linus Walleij
2011-08-19 10:48 ` Jamie Iles
2011-08-19 14:04   ` Linus Walleij
2011-08-19 14:26     ` Jamie Iles
2011-08-21 14:24       ` Jamie Iles
2011-08-22 12:38         ` Linus Walleij
2011-08-22 12:54           ` Jamie Iles
2011-08-19 14:36     ` Arnd Bergmann
2011-08-19 16:52       ` Greg KH
2011-08-22 12:29         ` Linus Walleij
2011-08-21 14:53 ` Barry Song
2011-08-24  6:24 ` Barry Song
2011-08-24  7:41   ` Linus Walleij
2011-08-24 18:29 ` Stephen Warren
2011-08-25 10:12   ` Linus Walleij
2011-08-25 11:04     ` Sascha Hauer
2011-08-25 11:58       ` Linus Walleij
2011-08-25 12:07         ` Sascha Hauer [this message]
2011-08-25 15:12     ` David Brown
2011-08-25 18:14       ` Gregory Bean
2011-08-25 19:13     ` Stephen Warren
2011-08-26  8:35       ` Linus Walleij
2011-08-26 17:33         ` Stephen Warren
2011-08-29  8:40           ` Linus Walleij
2011-08-26  3:12 ` Barry Song
2011-08-26  8:36   ` Linus Walleij
2011-09-02  7:02 ` Stijn Devriendt
2011-09-02  7:57   ` Linus Walleij

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=20110825120745.GV31404@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --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).