Le 12/19/17 à 23:24, Linus Walleij a écrit : > On Mon, Dec 11, 2017 at 12:38 AM, Florian Fainelli <f.faine...@gmail.com> > wrote: >> On 12/02/2017 04:48 AM, Linus Walleij wrote: > >>> This should solve your problem without having to alter the semantics >>> of pinctrl_select_state() for everyone. >> >> This was exactly what I proposed initially here: >> >> http://patchwork.ozlabs.org/patch/734326/ >> >> I really want to get this fixed, but I can't do that if we keep losing >> the context of the discussion (pun intended) :). > > Oh sorry man. I am clearly too stupid for this job...
No need to slap yourself! > > In accordance with things needing to be intuitive, something named > *force_* should of course force the setting into the hardware. > > The original patch didn't mention the fact that it was hogs > and hogs only that was causing the trouble and that is why I > got lost. (I guess.) I have been going about this as if it was > something generic that affect all states in all devices, and to > me hogs is just an abscure corner of pin controlling... > > I applied the patchwork patch from above, and elaborated > a bit on that it pertains to hogs, let's see what > happens. > > For the case where a driver (not hog) needs to handle > suspend/resume transitions, proper states can hopefully > be used. Your commit message makes that clear now, thanks for applying the patch and gott nytt år! -- Florian
