From: Bjorn Andersson <andersson@kernel.org>
To: dmitry.baryshkov@linaro.org, sboyd@kernel.org,
quic_tdas@quicinc.com, Konrad Dybcio <konrad.dybcio@linaro.org>,
agross@kernel.org, mturquette@baylibre.com
Cc: linux-arm-msm@vger.kernel.org, elder@linaro.org,
linux-clk@vger.kernel.org
Subject: Re: [PATCH v3 0/8] clk: qcom: rpm/rpmh: drop platform names
Date: Fri, 2 Dec 2022 14:58:46 -0600 [thread overview]
Message-ID: <167001472432.2721945.15938867197458182832.b4-ty@kernel.org> (raw)
In-Reply-To: <20221202185843.721673-1-dmitry.baryshkov@linaro.org>
On Fri, 2 Dec 2022 20:58:35 +0200, Dmitry Baryshkov wrote:
> Both RPM and RPMH clocks use platform (SoC) as a part of the clock
> definition. However there is nothing really SoC-specific in this
> part. Using it just leads to confusion and sometimes to duplication of
> definitions. Drop the SoC name where it is logical.
>
> Changes since v2:
> - Additional rework of ARC/VRM clock handling as suggested by Alex
>
> [...]
Applied, thanks!
[1/8] clk: qcom: rpmh: group clock definitions together
commit: 82349cc0d1f70df9436da2f565ec10aadf1c3680
[2/8] clk: qcom: rpmh: reuse common duplicate clocks
commit: 65b0c564a34f38832b25b0f5769e9cdf9e5faefd
[3/8] clk: qcom: rpmh: drop all _ao names
commit: 012c226fc68afe32acd7da01a0c2d2e483143bd4
[4/8] clk: qcom: rpmh: remove platform names from BCM clocks
commit: fe20294f4b7b180acc1ab7dcb7feff8601c76d7d
[5/8] clk: qcom: rpmh: support separate symbol name for the RPMH clocks
commit: 49e4aa233c6c239f814e8872d6757455e49e8106
[6/8] clk: qcom: rpmh: rename ARC clock data
commit: 166eb3eb3bb394255a9a8aa4cadbba5567ba184a
[7/8] clk: qcom: rpmh: rename VRM clock data
commit: 6ad844d739ee57779d3814fe3c9f97dff68719b2
[8/8] clk: qcom: rpmh: remove usage of platform name
commit: ec304d02b988132ac037c5b41fe375950c55de87
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2022-12-02 20:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 18:58 [PATCH v3 0/8] clk: qcom: rpm/rpmh: drop platform names Dmitry Baryshkov
2022-12-02 18:58 ` [PATCH v3 1/8] clk: qcom: rpmh: group clock definitions together Dmitry Baryshkov
2022-12-02 18:58 ` [PATCH v3 2/8] clk: qcom: rpmh: reuse common duplicate clocks Dmitry Baryshkov
2022-12-02 18:58 ` [PATCH v3 3/8] clk: qcom: rpmh: drop all _ao names Dmitry Baryshkov
2022-12-02 18:58 ` [PATCH v3 4/8] clk: qcom: rpmh: remove platform names from BCM clocks Dmitry Baryshkov
2022-12-02 18:58 ` [PATCH v3 5/8] clk: qcom: rpmh: support separate symbol name for the RPMH clocks Dmitry Baryshkov
2022-12-02 19:29 ` Alex Elder
2022-12-02 18:58 ` [PATCH v3 6/8] clk: qcom: rpmh: rename ARC clock data Dmitry Baryshkov
2022-12-02 19:29 ` Alex Elder
2022-12-02 18:58 ` [PATCH v3 7/8] clk: qcom: rpmh: rename VRM " Dmitry Baryshkov
2022-12-02 19:29 ` Alex Elder
2022-12-02 18:58 ` [PATCH v3 8/8] clk: qcom: rpmh: remove usage of platform name Dmitry Baryshkov
2022-12-02 19:30 ` Alex Elder
2022-12-02 19:55 ` [PATCH v3 0/8] clk: qcom: rpm/rpmh: drop platform names Bjorn Andersson
2022-12-02 20:58 ` 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=167001472432.2721945.15938867197458182832.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=elder@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