[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2mvkaq6c5.fsf@baylibre.com>
Date: Thu, 18 Aug 2016 13:28:58 -0500
From: Kevin Hilman <khilman@...libre.com>
To: Finlye Xiao <finley.xiao@...k-chips.com>
Cc: srinivas.kandagatla@...aro.org, maxime.ripard@...e-electrons.com,
heiko@...ech.de, robh+dt@...nel.org, frowand.list@...il.com,
sre@...nel.org, dbaryshkov@...il.com, dwmw2@...radead.org,
mark.rutland@....com, nm@...com, rjw@...ysocki.net,
viresh.kumar@...aro.org, sboyd@...eaurora.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org,
wxt@...k-chips.com, jay.xu@...k-chips.com,
rocky.hao@...k-chips.com, tim.chen@...k-chips.com,
tony.xie@...k-chips.com, ulysses.huang@...k-chips.com,
lin.huang@...k-chips.com
Subject: Re: [PATCH v2 1/4] nvmem: rockchip-efuse: Change initcall to subsys
Finlye Xiao <finley.xiao@...k-chips.com> writes:
> From: Finley Xiao <finley.xiao@...k-chips.com>
>
> 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@...k-chips.com>
Why can't this be handled with deferred probling? initcall ordering is
a can of worms.
Kevin
Powered by blists - more mailing lists