From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Stephen Warren <swarren@nvidia.com>,
Igor Grinberg <grinberg@compulab.co.il>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 1/2] gpiolib: introduce gpio_set_pullup
Date: Mon, 5 Dec 2011 15:56:35 +0000 [thread overview]
Message-ID: <20111205155634.GW11150@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20111205154011.GE9192@game.jcrosoft.org>
On Mon, Dec 05, 2011 at 04:40:11PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 08:51 Tue 29 Nov , Stephen Warren wrote:
> > I believe the pinctrl subsystem should be applicable to any chip, be it
> > the main SoC/CPU in the system, or any other chip. We don't currently
> > have any non-SoC drivers, but that's just because nobody has written them
> > yet; there's no technical reason they couldn't exist.
> sorry pinmux for gpio specific management i's overkill
If it's a GPIO-only device then probaby but lots of devices have a
fairly large range of signals that can be brought out on the pins (often
even more than a typical SoC actually).
prev parent reply other threads:[~2011-12-05 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 14:08 [PATCH 1/2] gpiolib: introduce gpio_set_pullup Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:08 ` [PATCH 2/2] gpiolib: introduce gpio_set_deglitch Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:14 ` Felipe Balbi
2011-11-25 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:16 ` [PATCH 1/2] gpiolib: introduce gpio_set_pullup Felipe Balbi
2011-11-25 14:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:59 ` Felipe Balbi
2011-11-25 15:34 ` Mark Brown
2011-11-27 9:35 ` Igor Grinberg
2011-11-29 2:37 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-29 16:51 ` Stephen Warren
2011-12-05 15:40 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-05 15:56 ` Mark Brown [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=20111205155634.GW11150@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=grant.likely@secretlab.ca \
--cc=grinberg@compulab.co.il \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.com \
--cc=swarren@nvidia.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