linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] Pinmux subsystem
Date: Mon, 2 May 2011 23:57:08 +0100	[thread overview]
Message-ID: <20110502225708.GD28001@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1304363768-30338-1-git-send-email-linus.walleij@stericsson.com>

On Mon, May 02, 2011 at 09:16:08PM +0200, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
> 
> This patchset creates a pinmux subsystem and switches U300 to use that new
> subsystem as an example. The problem is not that fantastically hard to
> solve in a general way, nobody got around to it because it requires some
> upfront code I believe, and this is my stab at it.

While I like the idea of consolidating the pinmuxing stuff, I'm not sure
about having a struct pin_mux pointer in each bus types device structure.
It'd mean this would have to be added to platform devices as well...

Then there's SA1100 (and PXA?) to consider with its IrDA setup, where its
necessary to switch the pin muxing during driver operation, when switching
between SIR and FIR modes (SIR uses the UART, FIR uses a separate hardware
block.)

So any per-device pinmuxing subsystem also needs a way that a driver can
change the pinmuxing of its associated pins on the fly too.

  reply	other threads:[~2011-05-02 22:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 19:16 [PATCH 0/4] Pinmux subsystem Linus Walleij
2011-05-02 22:57 ` Russell King - ARM Linux [this message]
2011-05-10 21:25   ` Linus Walleij
2011-05-10 21:45     ` Russell King - ARM Linux
2011-05-10 23:15       ` Linus Walleij
2011-05-03 17:27 ` Andrew Lunn
2011-05-03 19:29   ` Valdis.Kletnieks at vt.edu
2011-05-10 21:42   ` Linus Walleij
2011-05-11  9:50     ` Andrew Lunn
2011-05-12  0:41       ` Linus Walleij
2011-05-12  7:00         ` Andrew Lunn
2011-05-15 13:33     ` Andrew Lunn
2011-05-15 17:50       ` Linus Walleij
2011-05-17  1:57         ` Kyungmin Park
2011-05-18 20:02           ` Linus Walleij
2011-05-18 21:21             ` Mark Brown
2011-05-12  7:44 ` Sascha Hauer
2011-05-12  9:40   ` Tony Lindgren
2011-05-12 14:02   ` Linus Walleij
2011-05-12 21:17     ` Matthieu Castet
2011-05-13  7:05       ` Linus Walleij
2011-05-13 16:03         ` Matthieu CASTET
2011-05-14  7:57           ` Linus Walleij
2011-05-13  9:59     ` Sascha Hauer

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=20110502225708.GD28001@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).