On Thursday 17 January 2013 4:02:06 am Greg Ungerer wrote:
> Hi Linus,
>
> (My g...@snapgear.com email no longer gets to me, g...@uclinux.org is
> the best direct email for me now).
>
> On 01/17/2013 09:15 PM, Linus Walleij wrote:
> > On Thu, Jan 10, 2013 at 11:08 AM, Arnd Bergmann wrote:
> >> I'v
Hi Linus,
(My g...@snapgear.com email no longer gets to me, g...@uclinux.org is
the best direct email for me now).
On 01/17/2013 09:15 PM, Linus Walleij wrote:
> On Thu, Jan 10, 2013 at 11:08 AM, Arnd Bergmann wrote:
>
>> I've tried to find platforms that don't yet use GPIOLIB and fortunately
>
On Sun, Jan 20, 2013 at 7:07 AM, Alex Courbot wrote:
> Actually the question of switching to GPIOlib is only worth being asked if
> you are making use of drivers that require GENERIC_GPIO. If this is not the
> case and your GPIOs are only used by your own platform code, you can always
> give up u
Hi Steven,
On 01/18/2013 01:50 AM, Steven King wrote:
Well, my concern is the small, single chip platforms with limited ram and
speeds measured in MHz. My goal was that these platforms that had very basic
gpio needs, no offboard gpio, just toggling a few pins for spi or whatever,
could do that
On Thursday 17 January 2013, Steven King wrote:
> I haven't been keeping up with the kernel list of late, can someone point me
> to what''s being discussed so I can see what were talking about here?
We are discussion about changes to the GPIO API, in particular about
adding a descriptor (i.e. poi
On Thu, Jan 10, 2013 at 11:08 AM, Arnd Bergmann wrote:
> On Thursday 10 January 2013, Alex Courbot wrote:
>> > Regarding the integration of pinctrl with gpio,
>> > I was thinking in the past that we could make pinctrl provide everything
>> > that gpiolib does, and have a generic gpiolib driver on
On Thu, Jan 10, 2013 at 11:08 AM, Arnd Bergmann wrote:
> I've tried to find platforms that don't yet use GPIOLIB and fortunately
> there are very few left:
>
> I found two that provide the generic gpio interfaces when gpiolib
> is disabled, but use gpiolib otherwise for the same hardware,
> arch/
On Monday 14 January 2013, Alex Courbot wrote:
> On 01/10/2013 07:08 PM, Arnd Bergmann wrote:
> > I found two that provide the generic gpio interfaces when gpiolib
> > is disabled, but use gpiolib otherwise for the same hardware,
> > arch/m68k/include/asm/mcfgpio.h and arch/blackfin/include/asm/gpi
On 01/10/2013 07:08 PM, Arnd Bergmann wrote:
I've tried to find platforms that don't yet use GPIOLIB and fortunately
there are very few left:
I found two that provide the generic gpio interfaces when gpiolib
is disabled, but use gpiolib otherwise for the same hardware,
arch/m68k/include/asm/mcfg
On Thursday 10 January 2013, Alex Courbot wrote:
> On Wednesday 09 January 2013 18:46:12 Arnd Bergmann wrote:
> >
> > Only legacy users did this. Initially there was only the header file,
> > with the API declared but several different implementations of it.
> > gpiolib was introduced later to red
On Wednesday 09 January 2013, Alexandre Courbot wrote:
> On Tue, Jan 8, 2013 at 10:06 PM, Arnd Bergmann wrote:
> > I like the interface, good idea!
>
> Great! This was initially suggested by Linus W.
>
> > A few questions:
> >
> > Is there a plan for migrating all the existing users of the curre
On Tuesday 08 January 2013, Alexandre Courbot wrote:
> This series introduce a first take at implementing the RFC for the new GPIO
> API
> that I submitted last month. It proposes a new, opaque descriptor-based GPIO
> API
> that becomes available when GPIOlib is compiled, and provides a safer, mo
12 matches
Mail list logo
