From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Stijn Devriendt <highguy@gmail.com>,
Grant Likely <grant.likely@secretlab.ca>,
Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Lee Jones <lee.jones@linaro.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Kyungmin Park <kmpark@infradead.org>,
Kurt Van Dijck <kurt.van.dijck@eia.be>,
Ben Nizette <bn@niasdigital.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Rohit Vaswani <rvaswani@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>,
H Hartley Sweeten <hartleys@visionengravers.com>
Subject: Re: [PATCH 0/2] RFC: gpio: driver-local pin configuration
Date: Mon, 27 Jun 2011 13:02:57 +0100 [thread overview]
Message-ID: <20110627120256.GA19531@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <BANLkTimMSChGFUSnFWFHv3nNUca_Fyawaw@mail.gmail.com>
On Mon, Jun 27, 2011 at 01:44:43PM +0200, Linus Walleij wrote:
> Yes. To make the driver platform neutral, it needs to for example
> provide a callback in the platform data like (* set_pin_bias) or so,
> and then your platform has to implement this biasing.
> In this specific case that kind of stuff would likely be preferable
> to have in the platform anyway, but I understand what you mean.
How about device tree usage? I guess there we'd end up doing it by
putting the configuration on the GPIO end of things rather than on the
GPIO user side?
next prev parent reply other threads:[~2011-06-27 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 8:48 Linus Walleij
2011-06-23 10:54 ` Linus Walleij
2011-06-27 10:57 ` Stijn Devriendt
2011-06-27 11:44 ` Linus Walleij
2011-06-27 12:02 ` Mark Brown [this message]
2011-06-27 12:37 ` Linus Walleij
2011-06-28 11:53 ` Stijn Devriendt
2011-06-29 6:18 ` Linus Walleij
2011-06-29 7:39 ` Stijn Devriendt
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=20110627120256.GA19531@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bn@niasdigital.com \
--cc=grant.likely@secretlab.ca \
--cc=haojian.zhuang@gmail.com \
--cc=hartleys@visionengravers.com \
--cc=highguy@gmail.com \
--cc=kmpark@infradead.org \
--cc=kurt.van.dijck@eia.be \
--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 \
--cc=linux@arm.linux.org.uk \
--cc=rvaswani@codeaurora.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
all inboxes | Powered by JetHome®