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
Subject: [PATCH 0/4] arm: qcom: qcom-apq8064: add separate device node for tsens
Date: Wed, 6 Apr 2022 02:59:06 +0300 [thread overview]
Message-ID: <20220405235910.373107-1-dmitry.baryshkov@linaro.org> (raw)
Currently gcc-msm8960 driver manually creates tsens device. Instantiate
the device using DT node instead. This follow the IPQ8064 device tree
schema.
Compatibility with the previous devices trees is kept intact.
Dmitry Baryshkov (4):
dt-bindings: thermal: qcom-tsens.yaml: add msm8960 compat string
thermal/drivers/tsens: add compat string for the qcom,msm8960
clk: qcom: gcc-msm8960: create tsens device if there are no child
nodes
arm: dts: qcom-apq8064: create tsens device node
.../bindings/thermal/qcom-tsens.yaml | 4 +++-
arch/arm/boot/dts/qcom-apq8064.dtsi | 23 +++++++++++++------
drivers/clk/qcom/gcc-msm8960.c | 18 +++++++++------
drivers/thermal/qcom/tsens.c | 3 +++
4 files changed, 33 insertions(+), 15 deletions(-)
--
2.35.1
next reply other threads:[~2022-04-06 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 23:59 Dmitry Baryshkov [this message]
2022-04-05 23:59 ` [PATCH 1/4] dt-bindings: thermal: qcom-tsens.yaml: add msm8960 compat string Dmitry Baryshkov
2022-04-05 23:59 ` [PATCH 2/4] thermal/drivers/tsens: add compat string for the qcom,msm8960 Dmitry Baryshkov
2022-04-05 23:59 ` [PATCH 3/4] clk: qcom: gcc-msm8960: create tsens device if there are no child nodes Dmitry Baryshkov
2022-04-05 23:59 ` [PATCH 4/4] arm: dts: qcom-apq8064: create tsens device node 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=20220405235910.373107-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=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).