Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-31 Thread Johan Hovold
On Thu, Oct 31, 2013 at 06:30:37AM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote: > On 09:19 Thu 31 Oct , Bo Shen wrote: > > Hi Arnd, > > > > On 10/31/2013 04:46, Arnd Bergmann wrote: > > >On Wednesday 30 October 2013, Johan Hovold wrote: > > >>>I really hate this type of patch, as it's paper

Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-31 Thread Johan Hovold
On Wed, Oct 30, 2013 at 09:46:17PM +0100, Arnd Bergmann wrote: > On Wednesday 30 October 2013, Johan Hovold wrote: > > > I really hate this type of patch, as it's papering over the real > > > problem. What happens when someone else moves their driver to this > > > level? Then you are back to the

Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-30 Thread Jean-Christophe PLAGNIOL-VILLARD
On 09:19 Thu 31 Oct , Bo Shen wrote: > Hi Arnd, > > On 10/31/2013 04:46, Arnd Bergmann wrote: > >On Wednesday 30 October 2013, Johan Hovold wrote: > >>>I really hate this type of patch, as it's papering over the real > >>>problem. What happens when someone else moves their driver to this > >>

Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-30 Thread Bo Shen
Hi Arnd, On 10/31/2013 04:46, Arnd Bergmann wrote: On Wednesday 30 October 2013, Johan Hovold wrote: I really hate this type of patch, as it's papering over the real problem. What happens when someone else moves their driver to this level? Then you are back to the original problem. Yes, it'

Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-30 Thread Arnd Bergmann
On Wednesday 30 October 2013, Johan Hovold wrote: > > I really hate this type of patch, as it's papering over the real > > problem. What happens when someone else moves their driver to this > > level? Then you are back to the original problem. > > Yes, it's crude, but it's currently the only way

Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-30 Thread Johan Hovold
On Tue, Oct 29, 2013 at 04:22:49PM -0700, Greg KH wrote: > On Tue, Oct 22, 2013 at 06:32:40PM +0200, Johan Hovold wrote: > > Even with the atmel_pwm driver and the atmel-pwm-bl backlight driver > > supporting deferred probing, we still want to make sure that any > > pwm-device is available when the

Re: [PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-29 Thread Greg Kroah-Hartman
On Tue, Oct 22, 2013 at 06:32:40PM +0200, Johan Hovold wrote: > Even with the atmel_pwm driver and the atmel-pwm-bl backlight driver > supporting deferred probing, we still want to make sure that any > pwm-device is available when the backlight devices are probed to avoid > any unnecessary delays b

[PATCH 2/2] misc: atmel_pwm: set initcall level to subsys

2013-10-22 Thread Johan Hovold
Even with the atmel_pwm driver and the atmel-pwm-bl backlight driver supporting deferred probing, we still want to make sure that any pwm-device is available when the backlight devices are probed to avoid any unnecessary delays before enabling the backlight. Signed-off-by: Johan Hovold --- drive