Heiko Stuebner <heiko@xxxxxxxxx> writes: > Am Donnerstag, 18. August 2016, 13:28:58 CEST schrieb Kevin Hilman: >> Finlye Xiao <finley.xiao@xxxxxxxxxxxxxx> writes: >> > From: Finley Xiao <finley.xiao@xxxxxxxxxxxxxx> >> > >> > We will register a cpufreq notifier for adjusting opp's voltage, and it >> > need to fetch cpu's leakage from efuse in the notifier_call. so the efuse >> > driver should probe before cpufreq driver. >> > >> > Signed-off-by: Finley Xiao <finley.xiao@xxxxxxxxxxxxxx> >> >> Why can't this be handled with deferred probling? initcall ordering is >> a can of worms. > > I think the issue is less between efuse and avs driver, but more between avs > driver and cpufreq. The avs driver aims to modify the opp table and thus wants > to do that / register the notifier before cpufreq starts. > > And as there is no direct connection between cpufreq and the avs driver, > making cpufreq defer probing is probably not really easy. Thanks for the explanation. Sounds like something that belongs in the changelog. Kevin -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
