1
1
This is a place for planning the ongoing long-term work in the GPIO
2
2
subsystem.
3
3
4
+ ===============================================================================
4
5
5
6
GPIO descriptors
6
7
@@ -48,6 +49,7 @@ Work items:
48
49
numberspace accessors from <linux/gpio.h> and eventually delete
49
50
<linux/gpio.h> altogether.
50
51
52
+ -------------------------------------------------------------------------------
51
53
52
54
Get rid of <linux/of_gpio.h>
53
55
@@ -75,6 +77,7 @@ Work items:
75
77
- Delete <linux/of_gpio.h> when all the above is complete and everything
76
78
uses <linux/gpio/consumer.h> or <linux/gpio/driver.h> instead.
77
79
80
+ -------------------------------------------------------------------------------
78
81
79
82
Get rid of <linux/gpio/legacy-of-mm-gpiochip.h>
80
83
@@ -85,6 +88,7 @@ Work items:
85
88
to_of_mm_gpio_chip(), of_mm_gpiochip_add_data(), of_mm_gpiochip_remove(),
86
89
CONFIG_OF_GPIO_MM_GPIOCHIP from the kernel.
87
90
91
+ -------------------------------------------------------------------------------
88
92
89
93
Collect drivers
90
94
@@ -99,6 +103,7 @@ At the same time it makes sense to get rid of code duplication in existing or
99
103
new coming drivers. For example, gpio-ml-ioh should be incorporated into
100
104
gpio-pch.
101
105
106
+ -------------------------------------------------------------------------------
102
107
103
108
Generic MMIO GPIO
104
109
@@ -119,13 +124,15 @@ Work items:
119
124
helpers (x86 inb()/outb()) and convert port-mapped I/O drivers to use
120
125
this with dry-coding and sending to maintainers to test
121
126
127
+ -------------------------------------------------------------------------------
122
128
123
129
Generic regmap GPIO
124
130
125
131
In the very similar way to Generic MMIO GPIO convert the users which can
126
132
take advantage of using regmap over direct IO accessors. Note, even in
127
133
MMIO case the regmap MMIO with gpio-regmap.c is preferable over gpio-mmio.c.
128
134
135
+ -------------------------------------------------------------------------------
129
136
130
137
GPIOLIB irqchip
131
138
@@ -135,6 +142,7 @@ try to cover any generic kind of irqchip cascaded from a GPIO.
135
142
- Look over and identify any remaining easily converted drivers and
136
143
dry-code conversions to gpiolib irqchip for maintainers to test
137
144
145
+ -------------------------------------------------------------------------------
138
146
139
147
Moving over to immutable irq_chip structures
140
148
0 commit comments