On Wednesday 08 January 2014 21:24:08 Thierry Reding wrote: > > The problem with devres, or any other solution for that matter, is that > for the cases where we'd need something like this (that is, statically > allocated devices in board setup code) we don't have a fully initialized > struct device. We need at least device_initialize() to have been called > before devres can be used. Therefore we still need some sort of lookup > table that can be used to seed devres objects. Also devres will go away > completely when a driver is unloaded, so it'll have to be repopulated > everytime. > > I don't think that would buy us much over a simple table lookup. I would think we can come up with a way to add data to a device that ends up in devres by the time the device gets registered. The question is more whether you want a global table (or a set of global tables for that matter) or rather have all the data local to the devices you register. I generally prefer the latter. There is an interesting question about what subsystems you'd want to include in this mechanism. We have a growing number of subsystems that want data represented in DT (clock, regulator, dmaengine, reset, led, pwm, irq, iommu, ...), most of which don't have a 'struct resource' equivalent. We could either try to create something generic enough to easily cover all of them, or we declare that if you actually want to use all of them you should really use DT, and we make it hard to add another subsystem specific lookup mechanism. Arnd -- 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
