From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Amit Kucheria <amitk@kernel.org>,
Thara Gopinath <thara.gopinath@gmail.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-pm@vger.kernel.org,
devicetree@vger.kernel.org, linux-clk@vger.kernel.org,
quic_tdas@quicinc.com
Subject: [PATCH v4 0/3] arm: qcom: qcom-apq8064: add separate device node for tsens
Date: Tue, 26 Apr 2022 12:41:41 +0300 [thread overview]
Message-ID: <20220426094144.2958416-1-dmitry.baryshkov@linaro.org> (raw)
Currently gcc-msm8960 driver manually creates tsens device. Instantiate
the device using DT node instead. This makes the APQ8064 follow the
IPQ8064 device tree schema (which is also closer to the way tsens
devices are described on newer Qualcomm platforms).
Compatibility with the previous devices trees is kept intact.
Changes since v3:
- Fix a typo qcom,gcc-msm8060 -> qcom,gcc-msm8960 (noted by Krzyshtof)
- Fixed indentation in the example (also noted by Krzyshtof)
Changes since v2:
- Remove patches merged by Daniel
- Rephrase commit messages to emphasize that these changes make apq8064
follow ipq8064
Changes since v1:
- populate child devices in gcc-msm8960
- add syscon to the gcc device tree node
Dmitry Baryshkov (3):
clk: qcom: gcc-msm8960: create tsens device if there are no child
nodes
arm: dts: qcom-apq8064: create tsens device node
dt-bindings: clock: qcom,gcc-apq8064: split tsens to the child node
Dmitry Baryshkov (3):
clk: qcom: gcc-msm8960: create tsens device if there are no child
nodes
arm: dts: qcom-apq8064: create tsens device node
dt-bindings: clock: qcom,gcc-apq8064: split tsens to the child node
.../bindings/clock/qcom,gcc-apq8064.yaml | 45 +++++++------------
arch/arm/boot/dts/qcom-apq8064.dtsi | 25 +++++++----
drivers/clk/qcom/gcc-msm8960.c | 6 ++-
3 files changed, 39 insertions(+), 37 deletions(-)
base-commit: 3123109284176b1532874591f7c81f3837bbdc17
prerequisite-patch-id: b5aad2b1e0db4e6d77d6a2faa2fe95acf274b3c8
prerequisite-patch-id: a0c7dcfc85a1eac4969530b73230f226006d6e1a
prerequisite-patch-id: 775709cdc871c90669902f9b431ac7b4f51408b5
--
2.35.1
next reply other threads:[~2022-04-26 10:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 9:41 Dmitry Baryshkov [this message]
2022-04-26 9:41 ` [PATCH v4 1/3] clk: qcom: gcc-msm8960: create tsens device if there are no child nodes Dmitry Baryshkov
2022-04-26 9:41 ` [PATCH v4 2/3] arm: dts: qcom-apq8064: create tsens device node Dmitry Baryshkov
2022-04-26 9:41 ` [PATCH v4 3/3] dt-bindings: clock: qcom,gcc-apq8064: split tsens to the child node Dmitry Baryshkov
2022-04-26 18:24 ` Rob Herring
2022-04-26 20:20 ` Dmitry Baryshkov
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=20220426094144.2958416-1-dmitry.baryshkov@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=agross@kernel.org \
--cc=amitk@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=quic_tdas@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=thara.gopinath@gmail.com \
/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).