Re: [RFC] driver core: don't hold dev's parent lock when using async probe

2018-05-24 Thread Martin Liu
On Thu, May 24, 2018 at 11:02:57AM -0400, Alan Stern wrote: > On Thu, 24 May 2018, Martin Liu wrote: > > > On Tue, May 22, 2018 at 01:09:44PM -0400, Alan Stern wrote: > > > On Tue, 22 May 2018, martin_liu wrote: > > > > > > > not sure if we still need 'bf74ad5bc417 ("[PATCH] Hold the > > > > devi

Re: [RFC] driver core: don't hold dev's parent lock when using async probe

2018-05-24 Thread Alan Stern
On Thu, 24 May 2018, Martin Liu wrote: > On Tue, May 22, 2018 at 01:09:44PM -0400, Alan Stern wrote: > > On Tue, 22 May 2018, martin_liu wrote: > > > > > not sure if we still need 'bf74ad5bc417 ("[PATCH] Hold the > > > device's parent's lock during probe and remove")' since it has > > > been ther

Re: [RFC] driver core: don't hold dev's parent lock when using async probe

2018-05-24 Thread Martin Liu
On Tue, May 22, 2018 at 01:09:44PM -0400, Alan Stern wrote: > On Tue, 22 May 2018, martin_liu wrote: > > > not sure if we still need 'bf74ad5bc417 ("[PATCH] Hold the > > device's parent's lock during probe and remove")' since it has > > been there over 10 years. If we still need it and hard to fix

Re: [RFC] driver core: don't hold dev's parent lock when using async probe

2018-05-22 Thread Alan Stern
On Tue, 22 May 2018, martin_liu wrote: > SOC have internal I/O buses that can't be probed for devices. The > devices on the buses can be accessed directly without additinal > configuration required. This type of bus is represented as > "simple-bus". In some platforms, we name "soc" with "simple-bu

[RFC] driver core: don't hold dev's parent lock when using async probe

2018-05-22 Thread martin_liu
SOC have internal I/O buses that can't be probed for devices. The devices on the buses can be accessed directly without additinal configuration required. This type of bus is represented as "simple-bus". In some platforms, we name "soc" with "simple-bus" attribute and many devices are hooked under a