On Wed, Dec 14, 2016 at 02:54:02PM -0600, Rob Herring wrote: > On Mon, Dec 12, 2016 at 12:39 PM, Jason Gunthorpe > <jgunthorpe@xxxxxxxxxxxxxxxxxxxx> wrote: > > If the DT has inter-dependencies, then the devices need to be removed > > in the right order to avoid removal problems. > > > > Assuming the DT is constructed so that EPROBE_DEFER doesn't happen > > during creating then a good way to avoid removal problems is reversing > > the order during depopulation. > > I assume you mean by sorting the nodes to get lucky with the init > order. Not quite, the init order doesn't matter, just that the device list/DT is ordered topologically. The driver bind order can still be randomized. No luck needed. > > In my specific case I have a gpio driver, followed by a i2c bitbang > > using that driver. So gpiolib prints an error if it the gpio driver is > > removed before the gpio client.. > > Good news, functional dependencies are going into 4.10. Let's fix GPIO > and use that. Sure, but it will be some time until that is used everwhere.. You don't think there is some value in 'hiding' the problem with ordering until that work is done? IIRC that was essentially how EPROBE_DEFER was introduced? Jason -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
