On Wed, Dec 3, 2025 at 6:01 PM Greg KH <[email protected]> wrote: > > > > I hope that explains it better. > > Yes it does, thanks. > > > To answer your question: the caller can't tell GPIO about this relationship, > > GPIO would have to ask reset about it but having a dedicated symbol for this > > doesn't really sound like the best approach. > > Ah, ick, no it doesn't. I really don't know what to suggest here, > sorry. >
I found a viable workaround inside GPIO where I create another GPIO shared proxy for the potential reset-gpio device. So that if there are two users of the same "reset-gpios", we create three proxies in total: one for user 1, one for user 2 and another one for the reset-gpio device which may or may not be instantiated. I think that the best approach would still be having access to device_is_dependent(). I don't quite get why read-only inspecting device links outside of PM or driver core should really be a bad thing, but I can live without it, I guess. Bart
