On Mon, 19 Sep 2016 10:52:51 -0700 Doug Anderson <dianders at chromium.org> wrote: > Hi, > > On Mon, Sep 19, 2016 at 10:48 AM, Boris Brezillon > <boris.brezillon at free-electrons.com> wrote: > > The PWM chip has always claimed the pins and muxed them to the PWM IP. > > So, this means it's broken from the beginning, and my patch is only > > uncovering the problem (unless the pins stay configured as input until > > the PWM is enabled, which I'm not sure is the case). > > Such a solution is achievable with the pinctrl APIs pretty easily. > You might not be able to use the automatic "init" state but you can do > something similar and switch to an "active" state once the PWM is > actually turned on the first time. But is it really the case here (I don't see any code requesting a specific pinmux depending on the PWM state)? Anyway, we really need to handle this case, we should define the typical voltage when the PWM is disabled. Same as what you suggested with voltage-when-input, but with a different naming (since the concept of pinmux is PWM hardware/driver specific). voltage-when-pwm-disabled = <...>;
