From: Francesco Dolcini <francesco@dolcini.it>
To: Daniel Schultz <d.schultz@phytec.de>
Cc: 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, upstream@lists.phytec.de,
w.egorov@phytec.de
Subject: Re: [PATCH 2/4] arm64: dts: ti: k3-am625-*: Specify Temperature Grade
Date: Wed, 7 May 2025 09:57:34 +0200 [thread overview]
Message-ID: <20250507075734.GA10198@francesco-nb> (raw)
In-Reply-To: <20250507050847.912756-2-d.schultz@phytec.de>
On Tue, May 06, 2025 at 10:08:45PM -0700, Daniel Schultz wrote:
> Specify the temperature grade in the base device tree to ensure
> correct trip points are applied for each board.
At least for Verdin this is not correct.
Verdin AM62 is available in different variants, the correct
thermal thresholds should be set in firmware/bootloader, see for example
in u-boot, arch/arm/mach-k3/am62x/am625_fdt.c
Francesco
next prev parent reply other threads:[~2025-05-07 9:01 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 [this message]
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 ` [Upstream] " Primoz Fiser
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=20250507075734.GA10198@francesco-nb \
--to=francesco@dolcini.it \
--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 \
--cc=w.egorov@phytec.de \
/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