On 27 January 2013 21:55, Andrew Lunn <andrew@xxxxxxx> wrote: > So when we have a multiplatform kernel with many of these drivers > built in, all but one are going to notice they are not on the hardware > they support, and return -ENODEV. > > By making it a platform driver, the kirkwood cpufreq driver will only > get loaded on kirkwood systems, and won't slow down the boot for > everybody else. I tried to grep platform_driver in drivers/cpufreq/ and got only: drivers/cpufreq/dbx500-cpufreq.c Now, the counter argument to your explanation is, multiplatform kernel would be built only for testing purpose and not for real product. So, even this kind of delay is really not a big issue. On the other hand with platform driver too, we will hit lot of other code and would consume some extra memory for keeping its structures :) -- viresh -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
