Messages in this thread | | | Date | Thu, 17 Sep 2015 15:21:03 -0400 (EDT) | From | Alan Stern <> | Subject | Re: [PATCH] driver core: Ensure proper suspend/resume ordering |
| |
On Thu, 17 Sep 2015, Rafael J. Wysocki wrote:
> Hi, > > On Thu, Sep 17, 2015 at 7:40 AM, Tomeu Vizoso > <tomeu.vizoso@collabora.com> wrote: > > On 17 September 2015 at 02:27, Rafael J. Wysocki <rjw@rjwysocki.net> wrote: > >> On Wednesday, September 16, 2015 03:22:37 PM Alan Stern wrote: > >>> > >>> It would also help if your patch checked to see if the device has any > >>> children, and avoided moving it to the end of the list if it does. In > >>> fact, that might be sufficient to avoid almost all problems. > >> > >> I agree. > >> > >> In any case if a device that already has children is about to be probed, > >> this is sort of a corner case anyway and should be handled as such. > > > > Just wanted to mention that it's very common in platforms that make > > use of DT to have some devices registered before their parents have probed. > > If I grep for DTS with simple-bus and simple-mfd I get 802 matches. > > > This is good to know, thanks!
Hmmm. In view of this, maybe it's not worthwhile to try looking for such things. Given that they exist all over the place, we will definitely need to handle them correctly.
Alan Stern
| |