On Mon, Aug 19, 2013 at 01:43:59PM -0600, Stephen Warren wrote: > On 08/17/2013 05:17 AM, Thierry Reding wrote: > ... > > Well, the most obvious cases where early initialization is needed > > are interrupt controllers and clocks. > > ... and IOMMUs, which apparently need to initialize before any devices > whose transactions are routed through the IOMMU, in order to set > themselves up as the IOMMU for the relevant devices. > > It's possible that the CPU-visible bus structure isn't a strict > inverse/reverse of the device-visible bus-structure. A device may have > CPU-visible registers on one bus segment, but inject master > transactions onto an unrelated bus segment. So it may not be as simple > as making a bus driver for the bus segment affected by the IOMMU, and > having that driver trigger instantiation of all its children. Well, perhaps that can be handled via deferred probing? The only thing preventing that right now is that drivers aren't actively aware of the IOMMUs existence. If we can make it a requirement that each driver needing the services of an IOMMU actively requests that service, then deferred probing should be able to deal with it. That doesn't necessarily mean that drivers need to be doing it manually. It strikes me as the kind of thing that could easily be done by the core. In fact I've been thinking of doing something similar to resolve devicetree IRQ references at probe time, rather than at device creation time to remove the need for interrupt chips to register early. Thierry
Attachment:
pgpGoVSffqVew.pgp
Description: PGP signature
