[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYTJ_JQvFmf+AuCxmk5kGGw_CLGn0-xnO+PqGav45Se3Q@mail.gmail.com>
Date: Wed, 16 Oct 2013 10:11:08 +0200
From: Linus Walleij <linus.walleij@...aro.org>
To: Alexandre Courbot <acourbot@...dia.com>
Cc: Arnd Bergmann <arnd@...db.de>,
Grant Likely <grant.likely@...aro.org>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Alexandre Courbot <gnurou@...il.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Mathias Nyman <mathias.nyman@...ux.intel.com>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>
Subject: Re: [PATCH v2 1/3] gpiolib: export descriptor-based GPIO interface
On Fri, Oct 11, 2013 at 8:14 PM, Alexandre Courbot <acourbot@...dia.com> wrote:
> This patch exports the gpiod_* family of API functions, a safer
> alternative to the legacy GPIO interface. Differences between the gpiod
> and legacy gpio APIs are:
>
> - gpio works with integers, whereas gpiod operates on opaque handlers
> which cannot be forged or used before proper acquisition
> - gpiod get/set functions are aware of the active low state of a GPIO
> - gpio consumers should now include <linux/gpio/consumer.h> to access
> the new interface, whereas chips drivers will use
> <linux/gpio/driver.h>
>
> The legacy gpio API is now built as inline functions on top of gpiod.
>
> Signed-off-by: Alexandre Courbot <acourbot@...dia.com>
Typically I have applied the patch adding gpio_[un]lock_as_irq()
and it conflicts with this. And it requires adding gpiod_* accessors
for these functions too...
Would you mind rebasing this on top of my "devel" branch?
Sorry for the moving target, but after this I think we are ready to
merge the gpiod* interface.
Yours,
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