> The interrupt controller _has_ been set up. The trouble is that the > interrupt controller has the same OF node as the switch itself, and the > same OF node. Therefore, fw_devlink waits for the _entire_ switch to > finish probing, it doesn't have insight into the fact that the > dependency is just on the interrupt controller. That seems to be the problem. fw_devlink appears to think probe is an atomic operation. A device is not probed, or full probed. Where as the drivers are making use of it being non atomic. Maybe fw_devlink needs the third state, probing. And when deciding if a device can be probed and depends on a device which is currently probing, it looks deeper, follows the phandle and see if the resource is actually available? Andrew