[PATCH v2 0/5] gpio / ACPI: Rework ACPI GPIO events and add support for operation regions

From: Mika Westerberg
Date: Mon Mar 10 2014 - 08:55:13 EST


This is second revision of the patch series. The first version is available
for example here [1].

This series tries to add support for two new ACPI 5.0 features that were
either missing on incomplete in the current Linux kernel:

* ACPI GPIO signaled events
* ACPI GPIO operation regions

The current ACPI GPIO support code already added preliminary support for
GPIO signaled events but at the time we didn't have real hardware with real
GPIO triggered events so it was never properly tested. Now there are
devices like Asus T100TA transformer that uses these events so we were able
to see that the ASL code is being executed when a GPIO interrupt is
triggered.

Changes to the previous version:

* Moved module refcount manipulation to gpiod_request().
* Call achip acpi_gpio instead.
* Fold patches [2,4/6] into one [2/5].
* Update changelog for [3/5] to state that no functional changes, it is
rename only.
* Explain ACPI operations regions a bit better in [5/5].

These patches apply on top of two patches from Alexandre Courbot [2] which
introduce gpiochip_get_desc() function.

[1] http://linux-kernel.2935.n7.nabble.com/PATCH-0-6-gpio-ACPI-Rework-ACPI-GPIO-events-and-add-support-for-operation-regions-td811694.html
[2] https://lkml.org/lkml/2014/2/9/24

Mika Westerberg (5):
gpiolib: Allow GPIO chips to request their own GPIOs
gpio / ACPI: Allocate ACPI specific data directly in acpi_gpiochip_add()
gpio / ACPI: Rename acpi_gpio_evt_pin to acpi_gpio_event
gpio / ACPI: Rework ACPI GPIO event handling
gpio / ACPI: Add support for ACPI GPIO operation regions

drivers/gpio/gpiolib-acpi.c | 465 ++++++++++++++++++++++++++++++++------------
drivers/gpio/gpiolib.c | 103 +++++++---
drivers/gpio/gpiolib.h | 3 +
3 files changed, 421 insertions(+), 150 deletions(-)

--
1.9.0

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/