On 1/29/20 12:17 PM, Mark Brown wrote: > On Wed, Jan 29, 2020 at 10:52:40AM +0100, Greg KH wrote: > >> It just needs to be part of the bus logic for the specific bus that this >> "firewall" is on. Just like we do the same thing for USB or thunderbolt >> devices. Put this in the bus-specific code please. > I'd expect that this is going to affect at least platform and AMBA > buses. Correct me if I'm wrong but creating a new type of bus would mean that all the drivers living on this bus must be changed to register themselves on this bus ? Or does a solution exist to let them live on the platform bus and call firewalled bus before been probed ? All the impacted drivers could work on the existing bus with or without the firewall so I don't want to break that. Benjamin