[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTikpMdakfTU+RRsXQVnpO4-KGkOGJQ@mail.gmail.com>
Date: Mon, 27 Jun 2011 14:37:32 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc: Stijn Devriendt <highguy@...il.com>,
Grant Likely <grant.likely@...retlab.ca>,
Linus Walleij <linus.walleij@...ricsson.com>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Lee Jones <lee.jones@...aro.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Kyungmin Park <kmpark@...radead.org>,
Kurt Van Dijck <kurt.van.dijck@....be>,
Ben Nizette <bn@...sdigital.com>,
Haojian Zhuang <haojian.zhuang@...il.com>,
Rohit Vaswani <rvaswani@...eaurora.org>,
Russell King <linux@....linux.org.uk>,
H Hartley Sweeten <hartleys@...ionengravers.com>
Subject: Re: [PATCH 0/2] RFC: gpio: driver-local pin configuration
On Mon, Jun 27, 2011 at 2:02 PM, Mark Brown
<broonie@...nsource.wolfsonmicro.com> wrote:
> 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?
Sorry I can't quite understand that, please elaborate!
Thanks,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists