From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Maulik Shah <quic_mkshah@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
quic_lsrao@quicinc.com
Subject: Re: (subset) [PATCH 0/2] Update init level for cmd-db, rpmh-rsc and psci cpuidle domains
Date: Sun, 17 Mar 2024 11:27:19 -0500 [thread overview]
Message-ID: <171069283520.134123.11587509643696857617.b4-ty@kernel.org> (raw)
In-Reply-To: <20240217-init_level-v1-0-bde9e11f8317@quicinc.com>
On Sat, 17 Feb 2024 19:27:06 +0530, Maulik Shah wrote:
> cmd-db and rpmh-rsc are used by clients like regulators, interconnects and
> clocks for resource voting. These clients are in core_initcall() while
> cmd-db and rpmh-rsc are in arch_initcall(). Update init level for these
> drivers also to core_initcall() to avoid unnecessary probe defer during
> boot up.
>
> Similarly psci cpuidle psci power domains are used by rpmh-rsc driver and
> they are in subsys_initcall(). Update it to core_initcall().
>
> [...]
Applied, thanks!
[1/2] soc: qcom: Update init level to core_initcall() for cmd-db and rpmh-rsc
commit: 15ec7c641dd3a33f4d7b7c0cc59369d87edcec5c
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-03-17 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 13:57 [PATCH 0/2] Update init level for cmd-db, rpmh-rsc and psci cpuidle domains Maulik Shah
2024-02-17 13:57 ` [PATCH 1/2] soc: qcom: Update init level to core_initcall() for cmd-db and rpmh-rsc Maulik Shah
2024-02-28 15:40 ` Ulf Hansson
2024-04-04 11:06 ` Ulf Hansson
2024-02-17 13:57 ` [PATCH 2/2] cpuidle: psci: Update init level to core_initcall() Maulik Shah
2024-02-28 15:40 ` Ulf Hansson
2024-04-04 11:06 ` Ulf Hansson
2024-03-17 16:27 ` Bjorn Andersson [this message]
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=171069283520.134123.11587509643696857617.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_lsrao@quicinc.com \
--cc=quic_mkshah@quicinc.com \
--cc=rafael@kernel.org \
--cc=ulf.hansson@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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