> Date: Mon, 28 Mar 2016 21:49:39 +1100
> From: Jonathan Gray
>
> On Sun, Mar 27, 2016 at 09:28:25PM +0200, Mark Kettenis wrote:
> > The diff below is a first stab at adding support for GPIOs as defined
> > in ACPI 5.0. The primary target for this new ACPI feature is hardware
> > reduced platfor
> Date: Sun, 27 Mar 2016 20:29:29 -0700
> From: Philip Guenther
>
> On Sun, Mar 27, 2016 at 12:28 PM, Mark Kettenis
> wrote:
> > The diff below is a first stab at adding support for GPIOs as defined
> > in ACPI 5.0. The primary target for this new ACPI feature is hardware
> > reduced platforms
On Sun, Mar 27, 2016 at 09:28:25PM +0200, Mark Kettenis wrote:
> The diff below is a first stab at adding support for GPIOs as defined
> in ACPI 5.0. The primary target for this new ACPI feature is hardware
> reduced platforms like those based on Intel's Bay Trail SoC. The diff
> adds a bytgpio(4
On Sun, Mar 27, 2016 at 12:28 PM, Mark Kettenis wrote:
> The diff below is a first stab at adding support for GPIOs as defined
> in ACPI 5.0. The primary target for this new ACPI feature is hardware
> reduced platforms like those based on Intel's Bay Trail SoC. The diff
> adds a bytgpio(4) drive
The diff below is a first stab at adding support for GPIOs as defined
in ACPI 5.0. The primary target for this new ACPI feature is hardware
reduced platforms like those based on Intel's Bay Trail SoC. The diff
adds a bytgpio(4) driver for the hardware found on that SoC. This
driver registers its
