Lines Matching +full:full +full:- +full:custom

1 This is a place for planning the ongoing long-term work in the GPIO
8 to move away from the global GPIO numberspace and toward a descriptor-based
17 unmanageable: machine board files tend to become full of macros trying to
18 establish the numberspace at compile-time, making it hard to add any numbers
26 The runtime-assigned GPIO numberspace (what you get if you assign the GPIO
27 base as -1 in struct gpio_chip) has also became unpredictable due to factors
28 such as probe ordering and the introduction of -EPROBE_DEFER making probe
37 - Convert all GPIO device drivers to only #include <linux/gpio/driver.h>
39 - Convert all consumer drivers to only #include <linux/gpio/consumer.h>
41 - Convert all machine descriptors in "boardfiles" to only
46 - When this work is complete (will require some of the items in the
58 the device tree back-end. It is legacy and should not be used in new code.
62 - Get rid of struct of_mm_gpio_chip altogether: use the generic  MMIO
67 - Change all consumer drivers that #include <linux/of_gpio.h> to
68   #include <linux/gpio/consumer.h> and stop doing custom parsing of the
72 - Pull semantics for legacy device tree (OF) GPIO lookups into
73   gpiolib-of.c: in some cases subsystems are doing custom flags and
80 - Delete <linux/of_gpio.h> when all the above is complete and everything
96 in drivers/gpio/gpio-*. Augment platforms to create platform devices or
103 new coming drivers. For example, gpio-ml-ioh should be incorporated into
104 gpio-pch.
111 drivers. (drivers/gpio/gpio-mmio.c)
115 - Look over and identify any remaining easily converted drivers and
116   dry-code conversions to MMIO GPIO for maintainers to test
118 - Expand the MMIO GPIO or write a new library for regmap-based I/O
122 - Expand the MMIO GPIO or write a new library for port-mapped I/O
123   helpers (x86 inb()/outb()) and convert port-mapped I/O drivers to use
124   this with dry-coding and sending to maintainers to test
132 - Look over and identify any remaining easily converted drivers and
133   dry-code conversions to gpiolib irqchip for maintainers to test
138 There are already ways to use pin control as back-end for GPIO and
177 discussed but the idea is to provide a low-level access point
187 from being made read-only and forcing duplication of structures that