From: Bryan Brattlof <bb@ti.com> To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: ARM Linux Mailing List <linux-arm-kernel@lists.infradead.org>, Device Tree Mailing List <devicetree@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Keerthy <j-keerthy@ti.com>, Bryan Brattlof <bb@ti.com> Subject: [PATCH v2 0/6] add VTM nodes to TI's K3 SoCs Date: Thu, 19 Jan 2023 18:30:45 -0600 [thread overview] Message-ID: <20230120003051.9100-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's exceeded a critical temperature. Changes from v1: - Fixed indexing of thermal nodes[0] [0] https://lore.kernel.org/all/20230119221322.12563-1-bb@ti.com/ Thanks for reviewing! ~Bryan Bryan Brattlof (6): arm64: dts: ti: k3-am64-main: add VTM node arm64: dts: ti: k3-am62-wakeup: add VTM node arm64: dts: ti: k3-j721e-mcu-wakeup: add VTM node arm64: dts: ti: k3-j721s2-mcu-wakeup: add VTM node arm64: dts: ti: k3-j7200-mcu-wakeup: add VTM node arm64: dts: ti: k3-am62a-wakeup: 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 | 6 +- 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 | 8 ++ 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 | 8 ++ arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi | 103 ++++++++++++++++++ arch/arm64/boot/dts/ti/k3-j721s2.dtsi | 2 + 18 files changed, 403 insertions(+), 1 deletion(-) 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 base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2 -- 2.39.0
WARNING: multiple messages have this Message-ID (diff)
From: Bryan Brattlof <bb@ti.com> To: Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>, Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org> Cc: ARM Linux Mailing List <linux-arm-kernel@lists.infradead.org>, Device Tree Mailing List <devicetree@vger.kernel.org>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Keerthy <j-keerthy@ti.com>, Bryan Brattlof <bb@ti.com> Subject: [PATCH v2 0/6] add VTM nodes to TI's K3 SoCs Date: Thu, 19 Jan 2023 18:30:45 -0600 [thread overview] Message-ID: <20230120003051.9100-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's exceeded a critical temperature. Changes from v1: - Fixed indexing of thermal nodes[0] [0] https://lore.kernel.org/all/20230119221322.12563-1-bb@ti.com/ Thanks for reviewing! ~Bryan Bryan Brattlof (6): arm64: dts: ti: k3-am64-main: add VTM node arm64: dts: ti: k3-am62-wakeup: add VTM node arm64: dts: ti: k3-j721e-mcu-wakeup: add VTM node arm64: dts: ti: k3-j721s2-mcu-wakeup: add VTM node arm64: dts: ti: k3-j7200-mcu-wakeup: add VTM node arm64: dts: ti: k3-am62a-wakeup: 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 | 6 +- 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 | 8 ++ 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 | 8 ++ arch/arm64/boot/dts/ti/k3-j721s2-thermal.dtsi | 103 ++++++++++++++++++ arch/arm64/boot/dts/ti/k3-j721s2.dtsi | 2 + 18 files changed, 403 insertions(+), 1 deletion(-) 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 base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2 -- 2.39.0 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-01-20 0:31 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-20 0:30 Bryan Brattlof [this message] 2023-01-20 0:30 ` [PATCH v2 0/6] add VTM nodes to TI's K3 SoCs Bryan Brattlof 2023-01-20 0:30 ` [PATCH v2 1/6] arm64: dts: ti: k3-am64-main: add VTM node Bryan Brattlof 2023-01-20 0:30 ` Bryan Brattlof 2023-04-03 13:02 ` Christian Gmeiner 2023-04-03 13:02 ` Christian Gmeiner 2023-01-20 0:30 ` [PATCH v2 2/6] arm64: dts: ti: k3-am62-wakeup: " Bryan Brattlof 2023-01-20 0:30 ` Bryan Brattlof 2023-01-28 5:23 ` Raghavendra, Vignesh 2023-01-28 5:23 ` Raghavendra, Vignesh 2023-01-31 1:57 ` Bryan Brattlof 2023-01-31 1:57 ` Bryan Brattlof 2023-04-03 13:04 ` Christian Gmeiner 2023-04-03 13:04 ` Christian Gmeiner 2023-04-03 14:09 ` Bryan Brattlof 2023-04-03 14:09 ` Bryan Brattlof 2023-01-20 0:30 ` [PATCH v2 3/6] arm64: dts: ti: k3-j721e-mcu-wakeup: " Bryan Brattlof 2023-01-20 0:30 ` Bryan Brattlof 2023-01-20 0:30 ` [PATCH v2 4/6] arm64: dts: ti: k3-j721s2-mcu-wakeup: " Bryan Brattlof 2023-01-20 0:30 ` Bryan Brattlof 2023-01-20 0:30 ` [PATCH v2 5/6] arm64: dts: ti: k3-j7200-mcu-wakeup: " Bryan Brattlof 2023-01-20 0:30 ` Bryan Brattlof 2023-01-20 0:30 ` [PATCH v2 6/6] arm64: dts: ti: k3-am62a-wakeup: " Bryan Brattlof 2023-01-20 0:30 ` Bryan Brattlof 2023-06-15 10:22 ` [PATCH v2 0/6] add VTM nodes to TI's K3 SoCs Vignesh Raghavendra 2023-06-15 10:22 ` Vignesh Raghavendra
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=20230120003051.9100-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: linkBe 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.