From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Stephen Boyd <swboyd@chromium.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v2 0/2] dt-bindings: clock: sourt out gcc-apq8064 compats
Date: Tue, 26 Apr 2022 12:36:06 +0300 [thread overview]
Message-ID: <20220426093608.2957210-1-dmitry.baryshkov@linaro.org> (raw)
Move qcom,gcc-apq8084 to clock/qcom,gcc-other.yaml as it follows a generic
bindings rather than qcom,gcc-apq8064 one. Also while we are at it, move
qcom,gcc-msm8960 in the other direction: from qcom,gcc-other.yaml to
qcom,gcc-apq8064.yaml as MSM8960 shares the design and the driver with
APQ8064 platform.
Changes since v1:
- Split the msm8960 change into a separate patch
- Remove qcom,gcc-msm8960 compat from qcom,gcc-other.yaml
Dmitry Baryshkov (2):
dt-bindings: clock: gcc-apq8064: move qcom,apq8084 back to
gcc-other.yaml
dt-bindings: clock/qcom,gcc-apq8064: move msm8960 compat from
gcc-other.yaml
.../devicetree/bindings/clock/qcom,gcc-apq8064.yaml | 8 ++++----
.../devicetree/bindings/clock/qcom,gcc-other.yaml | 8 +++++---
2 files changed, 9 insertions(+), 7 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-26 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 9:36 Dmitry Baryshkov [this message]
2022-04-26 9:36 ` [PATCH v2 1/2] dt-bindings: clock: gcc-apq8064: move qcom,apq8084 back to gcc-other.yaml Dmitry Baryshkov
2022-04-26 14:35 ` Rob Herring
2022-04-26 9:36 ` [PATCH v2 2/2] dt-bindings: clock/qcom,gcc-apq8064: move msm8960 compat from gcc-other.yaml Dmitry Baryshkov
2022-04-26 14:36 ` Rob Herring
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=20220426093608.2957210-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).