On Tue, Oct 08, 2013 at 09:26:14AM -0700, Alexandre Courbot wrote: > On Tue, Oct 8, 2013 at 3:36 AM, Mika Westerberg > <mika.westerberg@xxxxxxxxxxxxxxx> wrote: > > On Tue, Oct 08, 2013 at 11:45:08AM +0300, Mika Westerberg wrote: > >> > I also wonder whether you could also avoid exporting acpi_get_gpiod* > >> > (which allow GPIO consumers to shortcut gpiolib) by implementing > >> > acpi_get_gpio* into the C file (maybe even using gpiod_get()). I see a > >> > "char *path" parameter though, so maybe that would not be possible at > >> > the moment. > >> > >> Good point, I'll check if we can do that. > > > > Looks like we can get rid of acpi_get_gpio() and acpi_get_gpiod() as there > > are no users for those outside gpiolib-acpi. I'm going to do that in the > > next revision. > > That's good news. If you can make it such that ACPI GPIO consumers > don't need to include acpi_gpio.h anymore, then this would make my > day. :) We can get rid of the whole apci_gpio.h eventually. But before doing that I would like to have something that supports both the ACPI way and gpiod way in v3.13 if possible. Once we have gpiod_get_index() in mainline, we can convert the existing user to it and drop acpi_gpio.h completely. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
