From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
Martin Persson <martin.persson@stericsson.com>,
Joe Perches <joe@perches.com>,
Russell King <linux@arm.linux.org.uk>,
Linaro Dev <linaro-dev@lists.linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] drivers: create a pinmux subsystem v3
Date: Sat, 9 Jul 2011 11:23:37 +0100 [thread overview]
Message-ID: <20110709102337.GD9247@sirena.org.uk> (raw)
In-Reply-To: <BANLkTi=r=N5OwfsVLRuBsNRSpv91pTgeKA@mail.gmail.com>
On Mon, Jun 13, 2011 at 01:57:36PM -0600, Grant Likely wrote:
> On Mon, Jun 13, 2011 at 10:58 AM, Linus Walleij
> > +This get/enable/disable/put sequence can just as well be handled by bus drivers
> > +if you don't want each and every driver to handle it and you know the
> > +arrangement on your bus.
> I would *strongly* recommend against individual device drivers
> accessing the pinmux api. This is system level configuration code,
> and should be handled at the system level.
There can also be advantages to putting the pin into the designed mode
without the driver being loaded from the electrical point of view. For
example, selecting appropriate pull values for pads can cut down on
power consumption.
next prev parent reply other threads:[~2011-07-09 10:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 16:58 [PATCH 1/2] drivers: create a pinmux subsystem v3 Linus Walleij
2011-06-13 18:11 ` Joe Perches
2011-06-14 9:19 ` Linus Walleij
2011-06-13 19:57 ` Grant Likely
2011-06-14 11:33 ` Linus Walleij
2011-07-09 10:23 ` Mark Brown [this message]
2011-08-19 11:59 ` Linus Walleij
2011-06-13 23:28 ` Stephen Warren
2011-06-14 14:25 ` Linus Walleij
2011-06-14 22:11 ` Stephen Warren
2011-06-16 12:47 ` Linus Walleij
2011-06-16 19:10 ` Stephen Warren
2011-06-27 14:34 ` Linus Walleij
2011-06-29 21:23 ` Stephen Warren
2011-08-19 12:34 ` Linus Walleij
2011-07-14 5:57 ` Barry Song
2011-08-08 2:28 ` Barry Song
2011-08-19 11:53 ` 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=20110709102337.GD9247@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=joe@perches.com \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=martin.persson@stericsson.com \
/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