From: Primoz Fiser <primoz.fiser@norik.com>
To: Daniel Schultz <d.schultz@phytec.de>,
nm@ti.com, vigneshr@ti.com, kristo@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, robertcnelson@gmail.com,
francesco.dolcini@toradex.com
Cc: upstream@lists.phytec.de
Subject: Re: [Upstream] [PATCH 4/4] arm64: dts: ti: k3-am62a7-*: Specify Temperature Grade
Date: Wed, 7 May 2025 08:17:12 +0200 [thread overview]
Message-ID: <4b8d4232-0e7f-4dc6-a76e-705bdc952db7@norik.com> (raw)
In-Reply-To: <20250507050847.912756-4-d.schultz@phytec.de>
Hi Daniel,
On 7. 05. 25 07:08, Daniel Schultz wrote:
> Specify the temperature grade in the base device tree to ensure
> correct trip points are applied for each board.
>
> Signed-off-by: Daniel Schultz <d.schultz@phytec.de>
> ---
> arch/arm64/boot/dts/ti/k3-am62a7-phyboard-lyra-rdk.dts | 1 +
> arch/arm64/boot/dts/ti/k3-am62a7-sk.dts | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am62a7-phyboard-lyra-rdk.dts b/arch/arm64/boot/dts/ti/k3-am62a7-phyboard-lyra-rdk.dts
> index 77e5fef618ba..7d2e4694ed8e 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62a7-phyboard-lyra-rdk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62a7-phyboard-lyra-rdk.dts
> @@ -10,6 +10,7 @@
> #include "k3-am62a7.dtsi"
> #include "k3-am62a-phycore-som.dtsi"
> #include "k3-am62x-phyboard-lyra.dtsi"
> +#include "k3-am62a-thermal-industrial.dtsi"
>
> / {
> compatible = "phytec,am62a7-phyboard-lyra-rdk",
> diff --git a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
> index 1c9d95696c83..125e812fbb86 100644
> --- a/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am62a7-sk.dts
> @@ -11,6 +11,7 @@
> #include <dt-bindings/gpio/gpio.h>
> #include <dt-bindings/net/ti-dp83867.h>
> #include "k3-am62a7.dtsi"
> +#include "k3-am62a-thermal-automative.dtsi"
You have a typo here... should be *automotive*.
BR,
Primoz
>
> / {
> compatible = "ti,am62a7-sk", "ti,am62a7";
--
Primoz Fiser
phone: +386-41-390-545
email: primoz.fiser@norik.com
--
Norik systems d.o.o.
Your embedded software partner
Slovenia, EU
phone: +386-41-540-545
email: info@norik.com
next prev parent reply other threads:[~2025-05-07 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 5:08 [PATCH 1/4] arm64: dts: ti: k3-am62-thermal: Add Files for each Temp. Grade Daniel Schultz
2025-05-07 5:08 ` [PATCH 2/4] arm64: dts: ti: k3-am625-*: Specify Temperature Grade Daniel Schultz
2025-05-07 7:57 ` Francesco Dolcini
2025-05-07 5:08 ` [PATCH 3/4] arm64: dts: ti: k3-am62a-thermal: Add Files for each Temp. Grade Daniel Schultz
2025-05-07 5:08 ` [PATCH 4/4] arm64: dts: ti: k3-am62a7-*: Specify Temperature Grade Daniel Schultz
2025-05-07 6:17 ` Primoz Fiser [this message]
2025-05-08 8:39 ` kernel test robot
2025-05-07 15:41 ` [PATCH 1/4] arm64: dts: ti: k3-am62-thermal: Add Files for each Temp. Grade Rob Herring (Arm)
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=4b8d4232-0e7f-4dc6-a76e-705bdc952db7@norik.com \
--to=primoz.fiser@norik.com \
--cc=conor+dt@kernel.org \
--cc=d.schultz@phytec.de \
--cc=devicetree@vger.kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robertcnelson@gmail.com \
--cc=robh@kernel.org \
--cc=upstream@lists.phytec.de \
--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