From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Taniya Das <quic_tdas@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org
Subject: [PATCH v3 0/4] clk: qcom: rpm: drop platform names
Date: Fri, 2 Dec 2022 09:08:10 +0200 [thread overview]
Message-ID: <20221202070814.482470-1-dmitry.baryshkov@linaro.org> (raw)
The RPM clocks driver uses 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:
- Split from the RPMH patchset
- Dropped superfluous active-only clock names when there are no actual
clocks behind
- Removed the _clk and _a_clk suffixes, moving them to preprocessor
macro, no need to have them all over the code.
Dmitry Baryshkov (4):
clk: qcom: rpm: remove unused active-only clock names
clk: qcom: rpm: drop separate active-only names
clk: qcom: rpm: drop the _clk suffix completely
clk: qcom: rpm: drop the platform from clock definitions
drivers/clk/qcom/clk-rpm.c | 204 +++++++++++++++++--------------------
1 file changed, 94 insertions(+), 110 deletions(-)
--
2.35.1
next reply other threads:[~2022-12-02 7:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 7:08 Dmitry Baryshkov [this message]
2022-12-02 7:08 ` [PATCH v3 1/4] clk: qcom: rpm: remove unused active-only clock names Dmitry Baryshkov
2022-12-02 7:08 ` [PATCH v3 2/4] clk: qcom: rpm: drop separate active-only names Dmitry Baryshkov
2022-12-02 7:08 ` [PATCH v3 3/4] clk: qcom: rpm: drop the _clk suffix completely Dmitry Baryshkov
2022-12-02 7:08 ` [PATCH v3 4/4] clk: qcom: rpm: drop the platform from clock definitions Dmitry Baryshkov
2022-12-02 19:42 ` [PATCH v3 0/4] clk: qcom: rpm: drop platform names Bjorn Andersson
2022-12-02 20:58 ` Bjorn Andersson
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=20221202070814.482470-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.