From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ben Nizette <bn@niasdigital.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org,
Grant Likely <grant.likely@secretlab.ca>,
linux-arm-kernel@lists.infradead.org,
Lee Jones <lee.jones@linaro.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib
Date: Mon, 18 Apr 2011 23:31:08 +0100 [thread overview]
Message-ID: <20110418223108.GA5935@sirena.org.uk> (raw)
In-Reply-To: <34EB51B7-AF3B-4DCE-A402-953B2DBC0474@niasdigital.com>
On Tue, Apr 19, 2011 at 08:16:12AM +1000, Ben Nizette wrote:
> On 18/04/2011, at 9:59 PM, Mark Brown wrote:
> > Even if it ends up being the board code using these APIs it seems
> > sensible to have a standard API that GPIO drivers can use to expose the
> > functionality. This will help with getting control into code Linux owns
> > (since people don't have to implement custom APIs) and will mean we can
> > do things like add control of this for device tree based boards.
> Oh I'm all for platform-specific libraries abstracting this away from the
> board code if that helps, that's certainly the way that, eg, AVR32 does it.
> It just doesn't make sense to me to bounce from the board code in to
> 'generic' gpio code then back to platform-specific implementations when
> you could cut out the middle man.
We have cross platform abstractions for lots of things - device tree,
which I mentioned, is the obvious example - and many of the GPIO
controllers are themselves cross platform as they're for off-SoC chips.
next prev parent reply other threads:[~2011-04-18 22:31 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-17 21:37 Linus Walleij
2011-04-17 21:48 ` Alan Cox
2011-04-17 21:58 ` Linus Walleij
2011-04-17 22:03 ` Alan Cox
2011-04-18 0:09 ` Kyungmin Park
2011-04-18 7:17 ` Kurt Van Dijck
2011-04-18 8:04 ` Ben Nizette
2011-04-18 8:19 ` Alan Cox
2011-04-18 8:50 ` Ben Nizette
2011-04-18 11:59 ` Mark Brown
2011-04-18 22:16 ` Ben Nizette
2011-04-18 22:31 ` Mark Brown [this message]
2011-04-19 4:50 ` Ben Nizette
2011-04-20 12:11 ` Linus Walleij
2011-04-18 12:26 ` Alan Cox
2011-04-18 22:26 ` Ben Nizette
2011-04-19 8:38 ` Alan Cox
2011-04-19 8:51 ` Kyungmin Park
2011-04-20 12:32 ` Linus Walleij
2011-04-20 12:38 ` Kyungmin Park
2011-04-20 14:54 ` Alan Cox
2011-04-20 14:26 ` Haojian Zhuang
2011-04-20 14:40 ` Kyungmin Park
2011-04-20 15:04 ` Haojian Zhuang
2011-04-20 15:17 ` Linus Walleij
2011-04-20 15:32 ` Alan Cox
2011-04-20 15:45 ` Linus Walleij
2011-04-27 21:55 ` Russell King - ARM Linux
2011-04-27 22:16 ` H Hartley Sweeten
2011-04-20 15:13 ` Linus Walleij
2011-04-20 15:29 ` Alan Cox
2011-04-20 15:39 ` Linus Walleij
2011-04-20 15:43 ` Alan Cox
2011-04-27 21:58 ` Russell King - ARM Linux
2011-04-20 0:09 ` Ben Nizette
2011-04-20 9:45 ` Alan Cox
2011-04-20 12:38 ` Linus Walleij
2011-04-20 14:55 ` Alan Cox
2011-04-20 12:21 ` Linus Walleij
2011-04-20 23:32 ` Ben Nizette
2011-04-21 6:48 ` Linus Walleij
2011-04-23 8:25 ` Ben Nizette
2011-04-21 0:29 ` Ben Nizette
2011-04-20 12:19 ` Linus Walleij
2011-04-20 12:22 ` Alan Cox
2011-04-20 12:04 ` Linus Walleij
2011-04-20 23:24 ` Ben Nizette
2011-04-21 15:39 ` Stijn Devriendt
2011-04-22 11:36 ` Linus Walleij
2011-04-22 11:56 ` Alan Cox
2011-04-23 8:35 ` Ben Nizette
2011-04-25 18:52 ` Rohit Vaswani
2011-04-26 7:48 ` 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=20110418223108.GA5935@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bn@niasdigital.com \
--cc=grant.likely@secretlab.ca \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome