Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

* Tony Lindgren [170111 08:29]: > * Linus Walleij [170111 07:34]: > > On Tue, Jan 10, 2017 at 8:19 PM, Tony Lindgren wrote: > > > > > Below is an experimental fix to intorduce pinctrl_start() that I've > > > tested with

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

* Linus Walleij [170111 07:34]: > On Tue, Jan 10, 2017 at 8:19 PM, Tony Lindgren wrote: > > > Below is an experimental fix to intorduce pinctrl_start() that I've > > tested with pinctrl-single. Then we should probably make all pin controller > >

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

On Tue, Jan 10, 2017 at 8:19 PM, Tony Lindgren wrote: > Below is an experimental fix to intorduce pinctrl_start() that I've > tested with pinctrl-single. Then we should probably make all pin controller > drivers call pinctrl_start() to properly fix the issue of struct

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

* Tony Lindgren [170110 07:32]: > * Geert Uytterhoeven [170110 06:09]: > > Hi Tony, > > > > On Tue, Dec 27, 2016 at 6:19 PM, Tony Lindgren wrote: > > > Having the pin control framework call pin controller functions > > > before it's

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

* Geert Uytterhoeven [170110 06:09]: > Hi Tony, > > On Tue, Dec 27, 2016 at 6:19 PM, Tony Lindgren wrote: > > Having the pin control framework call pin controller functions > > before it's probe has finished is not nice as the pin controller > > device

Re: [PATCH 1/5] pinctrl: core: Use delayed work for hogs

Hi Tony, On Tue, Dec 27, 2016 at 6:19 PM, Tony Lindgren wrote: > Having the pin control framework call pin controller functions > before it's probe has finished is not nice as the pin controller > device driver does not yet have struct pinctrl_dev handle. > > Let's fix this