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>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v6 0/4] arm: qcom: qcom-apq8064: add separate device node for tsens
Date: Sat, 21 May 2022 18:14:33 +0300 [thread overview]
Message-ID: <20220521151437.1489111-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 v5:
- Inherited the gcc-msm8960 patch from another patchseries.
- Marked old nvmem/thermal sensor properties as deprecated (Krzyshtof).
Changes since v4:
- Added thermal-sensor description to the qcom,gcc-apq8064 schema
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 (4):
dt-bindings: clock: qcom,gcc-apq8064: move msm8960 compat from
gcc-other.yaml
dt-bindings: clock: qcom,gcc-apq8064: split tsens to the child node
clk: qcom: gcc-msm8960: create tsens device if there are no child
nodes
arm: dts: qcom-apq8064: create tsens device node
.../bindings/clock/qcom,gcc-apq8064.yaml | 40 ++++++++++++++-----
.../bindings/clock/qcom,gcc-other.yaml | 5 +--
arch/arm/boot/dts/qcom-apq8064.dtsi | 25 ++++++++----
drivers/clk/qcom/gcc-msm8960.c | 6 ++-
4 files changed, 55 insertions(+), 21 deletions(-)
--
2.35.1
next reply other threads:[~2022-05-21 15:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-21 15:14 Dmitry Baryshkov [this message]
2022-05-21 15:14 ` [PATCH v6 1/4] dt-bindings: clock: qcom,gcc-apq8064: move msm8960 compat from gcc-other.yaml Dmitry Baryshkov
2022-05-21 15:23 ` Krzysztof Kozlowski
2022-05-21 15:14 ` [PATCH v6 2/4] dt-bindings: clock: qcom,gcc-apq8064: split tsens to the child node Dmitry Baryshkov
2022-05-21 15:24 ` Krzysztof Kozlowski
2022-05-21 15:14 ` [PATCH v6 3/4] clk: qcom: gcc-msm8960: create tsens device if there are no child nodes Dmitry Baryshkov
2022-05-21 15:14 ` [PATCH v6 4/4] arm: dts: qcom-apq8064: create tsens device node Dmitry Baryshkov
2022-07-16 15:18 ` (subset) " Bjorn Andersson
2022-07-07 2:31 ` (subset) [PATCH v6 0/4] arm: qcom: qcom-apq8064: add separate device node for tsens Bjorn Andersson
2022-07-15 15:12 ` 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=20220521151437.1489111-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=krzk@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 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.