From: Bryan Brattlof <bb@ti.com>
To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Keerthy <j-keerthy@ti.com>,
Device Tree Mailing List <devicetree@vger.kernel.org>,
ARM Linux Mailing List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bryan Brattlof <bb@ti.com>
Subject: [PATCH v3 0/7] add VTM nodes to TI's K3 SoCs
Date: Wed, 5 Apr 2023 16:53:21 -0500 [thread overview]
Message-ID: <20230405215328.3755561-1-bb@ti.com> (raw)
Hello again everyone!
This patch series adds in basic VTM nodes for all of TI's K3 SoCs. As of
right now these do not do much other than add thermal entries into the
sysfs directory and power down the device once it exceeds a critical
temperature.
Changes from v1: [0]
- Fixed indexing of thermal nodes[0]
Changes from v2: [1]
- Updated unit address for am62x's &cbass_wakeup
- Dropped my j7* patches and cherry-picked Keerthy's
[0] https://lore.kernel.org/all/20230119221322.12563-1-bb@ti.com/
[1] https://lore.kernel.org/all/20230120003051.9100-1-bb@ti.com/
Thanks for reviewing!
~Bryan
Bryan Brattlof (3):
arm64: dts: ti: k3-am64-main: add VTM node
arm64: dts: ti: k3-am62-wakeup: add VTM node
arm64: dts: ti: k3-am62a-wakeup: add VTM node
Keerthy (4):
arm64: dts: ti: j784s4: Add VTM node
arm64: dts: ti: j721e: Add VTM node
arm64: dts: ti: j7200: Add VTM node
arm64: dts: ti: j721s2: Add VTM node
arch/arm64/boot/dts/ti/k3-am62-thermal.dtsi | 33 ++++++
arch/arm64/boot/dts/ti/k3-am62-wakeup.dtsi | 8 ++
arch/arm64/boot/dts/ti/k3-am62.dtsi | 8 +-
arch/arm64/boot/dts/ti/k3-am62a-thermal.dtsi | 47 ++++++++
arch/arm64/boot/dts/ti/k3-am62a-wakeup.dtsi | 8 ++
arch/arm64/boot/dts/ti/k3-am62a.dtsi | 2 +
arch/arm64/boot/dts/ti/k3-am64-main.dtsi | 8 ++
arch/arm64/boot/dts/ti/k3-am64-thermal.dtsi | 33 ++++++
arch/arm64/boot/dts/ti/k3-am64.dtsi | 3 +
.../boot/dts/ti/k3-j7200-mcu-wakeup.dtsi | 9 ++
arch/arm64/boot/dts/ti/k3-j7200-thermal.dtsi | 47 ++++++++
arch/arm64/boot/dts/ti/k3-j7200.dtsi | 2 +
.../boot/dts/ti/k3-j721e-mcu-wakeup.dtsi | 9 ++
arch/arm64/boot/dts/ti/k3-j721e-thermal.dtsi | 75 +++++++++++++
arch/arm64/boot/dts/ti/k3-j721e.dtsi | 2 +
.../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 9 ++
arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi | 101 ++++++++++++++++++
arch/arm64/boot/dts/ti/k3-j721s2.dtsi | 4 +
.../boot/dts/ti/k3-j784s4-mcu-wakeup.dtsi | 9 ++
arch/arm64/boot/dts/ti/k3-j784s4-thermal.dtsi | 101 ++++++++++++++++++
arch/arm64/boot/dts/ti/k3-j784s4.dtsi | 4 +
21 files changed, 520 insertions(+), 2 deletions(-)
create mode 100644 arch/arm64/boot/dts/ti/k3-am62-thermal.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-am62a-thermal.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-am64-thermal.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-j7200-thermal.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-j721e-thermal.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi
create mode 100644 arch/arm64/boot/dts/ti/k3-j784s4-thermal.dtsi
base-commit: 891db0c48efb48c3af334006f9d7ea6a0aa49cb9
--
2.40.0
next reply other threads:[~2023-04-05 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 21:53 Bryan Brattlof [this message]
2023-04-05 21:53 ` [PATCH v3 1/7] arm64: dts: ti: k3-am64-main: add VTM node Bryan Brattlof
2023-04-05 21:53 ` [PATCH v3 2/7] arm64: dts: ti: k3-am62-wakeup: " Bryan Brattlof
2023-04-05 21:53 ` [PATCH v3 3/7] arm64: dts: ti: k3-am62a-wakeup: " Bryan Brattlof
2023-04-05 21:53 ` [PATCH v3 4/7] arm64: dts: ti: j784s4: Add " Bryan Brattlof
2023-04-05 21:53 ` [PATCH v3 5/7] arm64: dts: ti: j721e: " Bryan Brattlof
2023-04-05 21:53 ` [PATCH v3 6/7] arm64: dts: ti: j7200: " Bryan Brattlof
2023-04-05 21:53 ` [PATCH v3 7/7] arm64: dts: ti: j721s2: " Bryan Brattlof
2023-05-22 12:01 ` [PATCH v3 0/7] add VTM nodes to TI's K3 SoCs Christian Gmeiner
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=20230405215328.3755561-1-bb@ti.com \
--to=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-keerthy@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.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).