On Wed, Nov 14, 2018 at 10:51:20PM +0100, Uwe Kleine-König wrote: > Hello Thierry, > > On Wed, Nov 14, 2018 at 12:34:49PM +0100, Thierry Reding wrote: > > On Fri, Nov 09, 2018 at 05:55:55PM +0100, Uwe Kleine-König wrote: > > > On Fri, Nov 09, 2018 at 02:24:42PM +0000, Vokáč Michal wrote: > > > > On 8.11.2018 20:18, Uwe Kleine-König wrote: > > > > > Taking your example with the backlight device you specify an "init" and > > > > > a "default" pinctrl and only "default" contains the muxing for the PWM > > > > > pin everything should be as smooth as necessary: The pwm is only muxed > > > > > when the backlight device is successfully bound. > > > > > > > > Have you tried that Uwe? The bad news is I tested that before and now > > > > again and it does not work like that. We already discussed that earlier. > > > > > > The key is that the pinmux setting for the PWM pin should be part of the > > > bl pinctrl, not the pwm pinctrl. Then "default" is only setup when the > > > bl device is successfully bound which is after the bl's .probe callback > > > called pwm_apply(). > > > > No, that's not at all correct. Pinmux settings should reside with the > > consumer of the pin. In this case, the PWM is the consumer of the pin, > > whereas the backlight is the consumer of the *PWM*. > > This is news to me. Adding Linus W. to Cc, maybe he can comment?! > > Grepping through the arm device trees it really seems common to put the > pinctrl for the pwm pin into the pwm device. I didn't search in depth, > but I didn't find a counter example. > > For GPIOs it is common that the pinmuxing is included in the GPIO's > consumer pinctrl. Ditto for mdio busses whose pinctrl is included in the > ethernet pinctrl. GPIO is different from PWM in that the GPIO is already the pin itself and is otherwise generic. So typically you put the pinmuxing options into the device tree node for the consumer of the GPIO, because it is only when the consumer uses the GPIO that you need to configure that pin as GPIO. For PWM, however, the PWM consumer is only the consumer of the PWM, but the PWM device itself is the real consumer of the pin that outputs the PWM signal. So the PWM determines when the pinmux states need to be applied, whereas the consumer of the PWM only deals with the PWM. For MDIO busses, I think they are usually part of, and driven by, the ethernet controller, so again it makes sense to put the pinmux into the node of the ethernet controller, because the ethernet controller is the user of the pins. > > The problem with making the PWM mode the "default" pinctrl state is that > > the default state will be applied before the driver is even probed. That > > makes it unsuitable for this case. I think what we really want here is > > explicitly "active" and "inactive" states for pinctrl where the PWM > > driver controls when exactly each state is applied. > > Note that this problem goes away nicely if the pwm pin is attached to > the backlight. Because it's the backlight's driver that "knows" when the > pwm is configured correctly and so the already existing mechanisms that > setup the mux when the bl is correctly probed do the right thing at the > right time. Actually that's not exactly true. The default pinctrl state will be applied before the driver's ->probe() implementation, so the pinctrl state will be active some time before even the backlight driver gets around to setting up the PWM. If you look at drivers/base/dd.c you'll see that really_probe() calls pinctrl_bind_pins() before calling the driver's ->probe() and will select the default state (unless there's also an "init" state defined, in which case that will get applied and only after successful probe will the default state be selected). So if you use only a default state, then you could even get into a situation where ->probe() return -EPROBE_DEFER and it would potentially take several seconds before the driver is reprobed, during which time the pinmux will already be set up but the PWM not configured properly and potentially outputting the wrong level. > > This solves the problem quite nicely because by default the pinctrl > > state isn't touched. For the case where the bootloader didn't initialize > > the PWM pin at all, the driver core won't do anything and keep it at the > > 100k pull-up default. > > Ditto if the pwm pinctrl is attached to the consumer without having to > introduce new pwm-specific stuff. Well yes, but you'd obviously also have to avoid using the "default" state, otherwise you'd run into the issues that I described above. > > > > > No I meant the pwm. Well, it's as easy as that: Whenever with your > > > > > approach you configure the pin as GPIO with the output set to low, > > > > > instead configure the pwm with duty_cycle to zero (or disable it). > > > > > Whenever with your approach you configure the pin as GPIO with the > > > > > output set to high, configure the pwm with duty_cycle to 100%. (Keeping > > > > > out inverted PWMs for the ease of discussion, but the procedure can be > > > > > adapted accordingly.) The only difference then is that with your > > > > > approach you already "know" in pwm-imx's .probe the idle level and can > > > > > configure the GPIO accordingly. With my approach you just have to wait > > > > > until the first pwm_apply which (as described above) works just as well. > > > > > > > > While here I am quite confident you are talking about kernel code, right? > > > > If yes, then your approach is clear to me. > > > > > > > > The problem is I am quite sure your approach does not solve the cases > > > > the pinctrl solution does. And according to my tests so far it does not > > > > work at all because the "init" and "default" states does not work as you > > > > are saying. > > > > > > That's as pointed out above, because you're looking at the pwm's pinctrl > > > and I at the pwm-consumer's pinctrl. > > > > > > Note that a sysfs consumer cannot be operated smoothly here, because > > > there is no pinctrl node to add the PWM mode to that only gets active > > > after the first configuration. This however is something that should not > > > be addressed in the imx driver but in the pwm core (if at all). > > > > With the pinctrl-based solution outlined above you can even operate a > > sysfs consumer properly. The pinctrl states are where they belong, with > > the PWM device and therefore they can be properly set when the PWM is > > used, rather than waiting for a PWM consumer to muck with the pinmux. > > > > Note how all the pieces are suddenly falling into place. In my > > experience that's usually a good indication that you're on the right > > track. > > OK, sysfs is the only point where the "put pinctrl stuff into the pwm > core (or driver)" is superior to the already existing and otherwise > completely working status quo. (Apart from bugs that need fixing in > your scenario, too.) Nope, sorry. It's superior in all of the other cases as well. You've said elsewhere already that the prerequisite for the current solution to support inverse polarity with the i.MX driver is to keep the driver running, even after the PWM is no longer used. Sorry but that's just not an option for me. > Given that I would not want to encourage people to stick to the sysfs > interface for their use case, that's ok IMHO. (And note that with the > bootloader's help you can even do this in a smooth way today.) No it's not. sysfs is a supported interface, so we shouldn't treat it differently from the other in-kernel users. And we also shouldn't rely on bootloaders to always do the right thing. People may not always be able to update the bootloader, or they may not have a use to drive a PWM from the bootloader and hence choose to leave it uninitialized. > Other than that my approach looks more elegant to me (which obviously is > subjective). It works in all cases apart from sysfs (which is special > because it's not integrated into the device model) and there is no need > to teach the pwm framework about pinmuxing and invent new pinctrl modes > for it. Elegance is useless if what you have doesn't work consistently and reliably. I don't understand your resistance to the pinctrl work. It's not rocket science. Michal already posted patches showing how it can be done and they're not very complicated. Also we're not doing anything out of the ordinary here. This is exactly the purpose of the pinctrl framework, so let's use the best tool at hand. > Also dts writes don't need to lookup the needed GPIO numbers and pinctrl. Just to clarify: I don't think that we need to get the GPIO number involved in this case, because we don't have to reconfigure the pin as GPIO to make this work. The only reason that Michal's proposal did that is because that was believed to be necessary. But if the pin can just be configured with a 100k pull-up, that's enough to pull the pin high when we need it. Thierry
Attachment:
signature.asc
Description: PGP signature
