Re: [PATCH v2 3/4] ACPI / gpio: Add hogging support

On Thu, Oct 20, 2016 at 02:09:30PM +0200, Linus Walleij wrote: > On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg > wrote: > > > GPIO hogging means that the GPIO controller can "hog" and configure certain > > GPIOs without need for a driver or userspace to do

Re: [PATCH v2 3/4] ACPI / gpio: Add hogging support

On Thu, Oct 20, 2016 at 02:09:30PM +0200, Linus Walleij wrote: > On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg > wrote: > > > GPIO hogging means that the GPIO controller can "hog" and configure certain > > GPIOs without need for a driver or userspace to do that. This is useful in > >

Re: [PATCH v2 3/4] ACPI / gpio: Add hogging support

On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg wrote: > GPIO hogging means that the GPIO controller can "hog" and configure certain > GPIOs without need for a driver or userspace to do that. This is useful in > open-connected boards where BIOS cannot possibly

Re: [PATCH v2 3/4] ACPI / gpio: Add hogging support

On Thu, Sep 29, 2016 at 3:39 PM, Mika Westerberg wrote: > GPIO hogging means that the GPIO controller can "hog" and configure certain > GPIOs without need for a driver or userspace to do that. This is useful in > open-connected boards where BIOS cannot possibly know beforehand which > devices

[PATCH v2 3/4] ACPI / gpio: Add hogging support

GPIO hogging means that the GPIO controller can "hog" and configure certain GPIOs without need for a driver or userspace to do that. This is useful in open-connected boards where BIOS cannot possibly know beforehand which devices will be connected to the board. This adds GPIO hogging mechanism to

[PATCH v2 3/4] ACPI / gpio: Add hogging support

GPIO hogging means that the GPIO controller can "hog" and configure certain GPIOs without need for a driver or userspace to do that. This is useful in open-connected boards where BIOS cannot possibly know beforehand which devices will be connected to the board. This adds GPIO hogging mechanism to