On Mon, Oct 6, 2025 at 11:55 PM Srinivas Kandagatla <[email protected]> wrote: > > > > > If they were called "reset-gpios" then we could (and should) use > > Krzysztof's reset-gpio driver here, but we have many cases where > > that's not the case and the names (and implied functions) are > > Yes, these codec drivers are due to be moved to use reset-gpios. >
You will still need to keep support for the current "powerdown-gpios" property in existing device tree sources so that doesn't change anything. And what about shared pins other than reset? 'dc-gpios' for display, other 'powerdown' instances, 'enable-gpios', all kinds of uncommon names like: `dlg,cs`, `wlf,ldo2ena`, `speaker-enable`, `maxim,enable`? It's not likely we will create a separate abstraction for each of them. What I'm proposing is a sane, catch-all mechanism for shared GPIOs that right now use a rather wonky hack. Also: the drivers have no business knowing that they request GPIOs that can be shared. This is why I want to hide it inside GPIOLIB. Bartosz
