Messages in this thread | | | Date | Thu, 22 Sep 2011 21:29:09 +0100 | From | Alan Cox <> | Subject | Re: [RFC PATCH v3] drivercore: Add driver probe deferral mechanism |
| |
Definitely what is needed for some of the x86 SoC stuff and would let us rip out some of the special case magic for the SCU discovery.
First thing that strikes me is driver_bound kicks the processing queue again. That seems odd - surely this isn't needed because any driver that does initialise this time and may allow something else to get going will queue the kick itself. Thus this seems to just add overhead.
It all looks a bit O(N²) if we don't expect the drivers that might trigger something else binding to just say 'hey I'm one of the troublemakers' -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |