On Mon, Dec 2, 2019 at 10:31 PM Peter Ujfalusi <peter.ujfalusi@xxxxxx> wrote: > On 28/11/2019 12.06, Linus Walleij wrote: > > The ambition to use refcounted GPIOs to solve this > > usecase is probably wrong, I would say try to go for a > > GPIO-based reset controller instead. > > I did that. A bit more lines of code than the gpio-shared. > Only works if all clients are converted to reset controller, all must > use reset_control_get_shared() I don't think that's too much to ask, the usecase needs to be expressed somewhere whether in code or DT properties. > But my biggest issue was that how would you put a resets/reset-names to > DT for a device where the gpio is used for enabling an output/input pin > and not to place the device or part of the device to reset. Rob suggest using GPIOs but represent them in the Linux kernel as resets. This would be a semantic effect of the line being named "reset-gpios" as Rob pointed out. Name implies usage. We can formalize it with DT YAML as well, these days, then it is impossible to get it wrong, as long as the bindings are correct. When you call the reset subsystem to create the reset handle it can be instructed to look for a GPIO, possibly shared, and this way replace the current explicit GPIO handling code in the driver. It will just look as a reset no matter how many other device or just this one is using it. > Sure, one can say that something is in 'reset' when it is not enabled, > but do you put the LCD backlight to 'reset' when you turn it off? > > Is your DC motor in 'reset' when it is not working? > > GPIO stands for General Purpose Input/Output, one of the purpose is to > enable/disable things, reset things, turn on/off things or anything one > could use 3.3V (or more/less). Answered by explict interpretation of DT bindings named "reset-gpios". Those are resets, nothing else. > > The fact that some Linux drivers are already using explicit > > GPIO's for their reset handling is maybe unfortunate, > > they will simply have to grow code to deal with a reset > > alternatively to GPIO, like first try to grab a reset > > handle and if that doesn't fall back to use a GPIO. > > Sure, it can be done, but when we hit a case when the reset framework is > not fitting for some devices use of the shared GPIO, then what we will do? That can be said about literally anything we do in any framework we design. Rough consensus and running code. Bad paths will be taken sometimes, hopefully not too much. We clean up the mess we create and refactor as we go along, it is always optimistic design. > How would it satisfy the regulator use case? We put the regulators to > 'reset' when they are turned off / disabled? We don't try to fix that now, if it's not broken don't fix it. Let's try to fix the reset problem instead. Yours, Linus Walleij
