On Mon, Apr 04, 2016 at 10:34:56PM +0300, Octavian Purdila wrote: > On Mon, Apr 4, 2016 at 7:03 PM, Mark Brown <broonie@xxxxxxxxxx> wrote: > > Why is probe different to hotplug? We don't need to do that in the > > normal driver model. > There might be some confusion with the term, I am referring to slave > hotplug, not controller hotplug. That's what I was talking about too. > The way I see it, there are two logical operations: probe of a > controller and the associated enumeration of the SPI slaves for that > bus and "hotplug" of new SPI slaves and the enumeration of those > particular slaves. I don't see a distinction here. The firmware finds some new slaves to tell the framework about. Quite why it decided to go looking shouldn't matter. > When a slave hotplug happens for device tree we get a device node > notification and we can instantiate the SPI slave based on that info. > In case of ACPI, (at this point) we get a global callback and in that > callback we need to iterate through *all* controllers. That's not really helping me understand why you need every bus to open code enumeration twice?
Attachment:
signature.asc
Description: PGP signature
