public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: khilman@baylibre•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 1/4] nvmem: rockchip-efuse: Change initcall to subsys
Date: Thu, 18 Aug 2016 13:28:58 -0500	[thread overview]
Message-ID: <m2mvkaq6c5.fsf@baylibre.com> (raw)
In-Reply-To: <1471510341-63926-2-git-send-email-finley.xiao@rock-chips.com> (Finlye Xiao's message of "Thu, 18 Aug 2016 16:52:18 +0800")

Finlye Xiao <finley.xiao@rock-chips•com> writes:

> From: Finley Xiao <finley.xiao@rock-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@rock-chips•com>

Why can't this be handled with deferred probling?  initcall ordering is
a can of worms.

Kevin

  reply	other threads:[~2016-08-18 18:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-18  8:52 [PATCH v2 0/4] PM / AVS: add Rockchip cpu avs Finlye Xiao
2016-08-18  8:52 ` [PATCH v2 1/4] nvmem: rockchip-efuse: Change initcall to subsys Finlye Xiao
2016-08-18 18:28   ` Kevin Hilman [this message]
2016-08-18 22:29     ` Heiko Stuebner
2016-08-19 16:19       ` Kevin Hilman
2016-08-18  8:52 ` [PATCH v2 2/4] of: introduce of_property_read_s32_index Finlye Xiao
2016-08-18  8:52 ` [PATCH v2 3/4] dt-bindings: add binding document for Rockchip cpu avs Finlye Xiao
2016-08-18  8:52 ` [PATCH v2 4/4] PM / AVS: rockchip-cpu-avs: add driver handling " Finlye Xiao
2016-08-18 19:02   ` Kevin Hilman
2016-08-29  6:08   ` Viresh Kumar
2016-09-12 21:55     ` Stephen Boyd
2016-09-26  3:55       ` Viresh Kumar
2016-09-26  8:05         ` Heiko Stuebner
2016-09-27  8:40           ` Finley Xiao
2016-09-27 22:14           ` Stephen Boyd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2mvkaq6c5.fsf@baylibre.com \
    --to=khilman@baylibre$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox