Lines Matching refs:GPIO
1 This is a place for planning the ongoing long-term work in the GPIO
5 GPIO descriptors
7 Starting with commit 79a9becda894 the GPIO subsystem embarked on a journey
8 to move away from the global GPIO numberspace and toward a decriptor-based
9 approach. This means that GPIO consumers, drivers and machine descriptions
10 ideally have no use or idea of the global GPIO numberspace that has/was
11 used in the inception of the GPIO subsystem.
15 - Convert all GPIO device drivers to only #include <linux/gpio/driver.h>
22 implicitly does not use global GPIO numbers.
33 driver infrastructure for doing simpler MMIO GPIO devices and there was
41 GPIO for all current users (see below). Delete struct of_mm_gpio_chip,
47 GPIO lines from the device tree. This can be tricky and often ivolves
50 - Pull semantics for legacy device tree (OF) GPIO lookups into
64 Collect GPIO drivers from arch/* and other places that should be placed
68 In some cases it makes sense to create a GPIO chip from the local driver
72 Generic MMIO GPIO
74 The GPIO drivers can utilize the generic MMIO helper library in many
81 dry-code conversions to MMIO GPIO for maintainers to test
83 - Expand the MMIO GPIO or write a new library for port-mapped I/O
91 try to cover any generic kind of irqchip cascaded from a GPIO.
136 - Support generic hierarchical GPIO interrupts: these are for the
137 non-cascading case where there is one IRQ per GPIO line, there is
143 There are already ways to use pin control as back-end for GPIO and
146 use of the global GPIO numbers. Once the above is complete, it may
148 multiplexing, pin configuration, GPIO, etc selectable options in one
149 and the same pin control and GPIO subsystem.