|
Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2, v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1, v5.2.0, v5.3.0, v5.2.0rc, v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1, v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0 |
|
| #
d56572d4 |
| 30-Apr-2016 |
Imre Vadász <imre@vdsz.com> |
gpio_acpi: Add allocate/release functions for GpioIo pins.
* This slightly simplifies the read_pin and write_pin functions, and
configuration errors should now be found when allocating the pin,
gpio_acpi: Add allocate/release functions for GpioIo pins.
* This slightly simplifies the read_pin and write_pin functions, and
configuration errors should now be found when allocating the pin,
instead of causing a panic in read_pin() or write_pin().
show more ...
|
| #
ad9cd008 |
| 30-Apr-2016 |
Imre Vadász <imre@vdsz.com> |
gpio_intel: Use a cookie object for gpio interrupt allocation as well.
* This tries to improve the gpio_if.m api, e.g. only the interrupt pin
allocation can legitimately fail. The interrupt setup
gpio_intel: Use a cookie object for gpio interrupt allocation as well.
* This tries to improve the gpio_if.m api, e.g. only the interrupt pin
allocation can legitimately fail. The interrupt setup and teardown
functions can't really fail for proper input values (and for bogus
arguments it can just panic).
show more ...
|
| #
0b0166b0 |
| 29-Apr-2016 |
Imre Vadász <imre@vdsz.com> |
gpio_acpi: Introduce separate setup_intr and teardown_intr functions.
* This allows us to actually reserve the gpio pin before, and separately
from actually setting up the interrupt handler.
* XX
gpio_acpi: Introduce separate setup_intr and teardown_intr functions.
* This allows us to actually reserve the gpio pin before, and separately
from actually setting up the interrupt handler.
* XXX This interface is still a bit inconvenient to use, because the
code allows gpio_setup_intr to fail. Instead the gpio_alloc_intr
function should be returning a cookie to use for gpio_setup_intr
(which could obviously never fail then).
show more ...
|
|
Revision tags: v4.4.3 |
|
| #
bca7db71 |
| 27-Mar-2016 |
Imre Vadász <imre@vdsz.com> |
gpio_intel: Support integrated GPIO controllers of the Cherry Trail SoC.
* The gpio_acpi module takes care of probing and setting up the ACPI
GPIO-signaled events and the ACPI address space handle
gpio_intel: Support integrated GPIO controllers of the Cherry Trail SoC.
* The gpio_acpi module takes care of probing and setting up the ACPI
GPIO-signaled events and the ACPI address space handler, utilizing the
gpio interface provided by gpio_intel for the actual GPIO accesses.
* So far gpio_intel can only be used for the ACPI-5.0 GPIO features.
* This makes ACPI gpio events (which replace GPE interrupts on many
current x86 SoC devices) work, and provides a handler for the
GeneralPurposeIo Opregions of each GPIO controller.
* With this the HP x2 210 detachable correctly recognizes unplugging
of the power supply, and opening/closing of the lid.
* Further work is still needed to refactor gpio_intel to make adding
support for other SoC/CPU versions easier.
* The gpio_if.m interface is still a prototype that only provides a
minimum of functionality that is needed to get gpio_acpi working.
show more ...
|