From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Taniya Das <quic_tdas@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH 0/4] clk: qcom: use module_platform_driver() to register drivers
Date: Tue, 6 Feb 2024 22:46:15 -0600 [thread overview]
Message-ID: <170728117675.479358.3901878809237532059.b4-ty@kernel.org> (raw)
In-Reply-To: <20240206-clk-module-platform-driver-v1-0-db799bd2feeb@linaro.org>
On Tue, 06 Feb 2024 17:25:11 +0200, Dmitry Baryshkov wrote:
> Several Qualcomm clock controller drivers use subsys_initcall to
> register the driver early. This makes sense for GCC or TCSRcc. However
> there is no need to register camera, display, GPU or venus clocks
> earlier. Shift registration to driver init level, where they belong.
>
> Note, I didn't touch lpass clock drivers, they need to be analysed
> separately.
>
> [...]
Applied, thanks!
[1/4] clk: qcom: camcc-*: switch to module_platform_driver
commit: 0ac31d8c2bb90312071e299a23b3299adde13736
[2/4] clk: qcom: dispcc-*: switch to module_platform_driver
commit: f4ccb184940247c784e229a739344678e487046d
[3/4] clk: qcom: gpucc-*: switch to module_platform_driver
commit: a5119f7dbf90d12d169f3e3088908ead1955c1b0
[4/4] clk: qcom: videocc-*: switch to module_platform_driver
commit: 95dd41487aecd1e8feeca9e10c6b28243b2f6145
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-02-07 4:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-06 15:25 [PATCH 0/4] clk: qcom: use module_platform_driver() to register drivers Dmitry Baryshkov
2024-02-06 15:25 ` [PATCH 1/4] clk: qcom: camcc-*: switch to module_platform_driver Dmitry Baryshkov
2024-02-06 19:05 ` Konrad Dybcio
2024-02-06 15:25 ` [PATCH 2/4] clk: qcom: dispcc-*: " Dmitry Baryshkov
2024-02-06 19:06 ` Konrad Dybcio
2024-02-06 15:25 ` [PATCH 3/4] clk: qcom: gpucc-*: " Dmitry Baryshkov
2024-02-06 19:06 ` Konrad Dybcio
2024-02-06 15:25 ` [PATCH 4/4] clk: qcom: videocc-*: " Dmitry Baryshkov
2024-02-06 19:06 ` Konrad Dybcio
2024-02-07 4:46 ` 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=170728117675.479358.3901878809237532059.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=sboyd@kernel.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