All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v6 02/11] arm64: dts: qcom: ipq5210: Introduce RDP504 common DT file
Date: Thu, 08 Oct 2026 09:21:40 +0000	[thread overview]
Message-ID: <sashiko-outbox-163927@kernel.org> (raw)
In-Reply-To: <20261008-08-dts-v6-2-f9c4ec8664d8@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] arm64: dts: qcom: undocumented SoC-wide thermal limit reduction
--

commit 0651d4639f9454796e2f9ce2439efba04746c6c9
Author: Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>

arm64: dts: qcom: ipq5210: Introduce RDP504 common DT file

This commit refactors the RDP504 board configuration to extract common settings
into a new shared file. It enables board-specific peripherals like USB, PCIe,
and SPI NAND.

> diff --git a/arch/arm64/boot/dts/qcom/ipq5210.dtsi b/arch/arm64/boot/dts/qcom/ipq5210.dtsi
> index 161b5bb5a7f74..3183182d1cc71 100644
> --- a/arch/arm64/boot/dts/qcom/ipq5210.dtsi
> +++ b/arch/arm64/boot/dts/qcom/ipq5210.dtsi
> @@ -823,7 +823,7 @@ ethphy-thermal {
>  
>  			trips {
>  				ethphy-critical {
> -					temperature = <125000>;
> +					temperature = <120000>;

[Severity: Medium]
The commit message solely describes extracting common board configurations for
the RDP504 board and enabling board-specific peripherals.

Is it intentional that this modifies the base SoC device tree file to lower the
critical temperature trip point for ethphy-thermal?

This alters the thermal characteristics for all IPQ5210-based boards. Should
this undocumented SoC-wide thermal limit reduction be separated into its own
commit to avoid unexpected regressions on other boards?

[ ... ]

> @@ -859,13 +859,13 @@ cpu0-thermal {
>  
>  			trips {
>  				cpu-critical {
> -					temperature = <120000>;
> +					temperature = <115000>;

[Severity: Medium]
Does this intentionally lower the critical temperature for cpu0-thermal in
ipq5210.dtsi?

This impacts performance throttling and shutdown limits for all boards using
this SoC, rather than just the RDP504 board described in the commit message.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261008-08-dts-v6-0-f9c4ec8664d8@oss.qualcomm.com?part=2

  reply	other threads:[~2026-10-08  9:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-08  9:14 [PATCH v6 00/11] Enable mutliple peripherals in IPQ5210 Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 01/11] arm64: dts: qcom: ipq5210: Add nodes for multiple peripherals Varadarajan Narayanan
2026-10-08  9:31   ` sashiko-bot
2026-10-08  9:14 ` [PATCH v6 02/11] arm64: dts: qcom: ipq5210: Introduce RDP504 common DT file Varadarajan Narayanan
2026-10-08  9:21   ` sashiko-bot [this message]
2026-10-08 10:48   ` Dmitry Baryshkov
2026-10-08  9:14 ` [PATCH v6 03/11] arm64: dts: qcom: ipq5210: Introduce RDP504 NAND variant " Varadarajan Narayanan
2026-10-08  9:26   ` sashiko-bot
2026-10-08  9:14 ` [PATCH v6 04/11] arm64: dts: qcom: ipq5210: Add support for WPS button Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 05/11] arm64: dts: qcom: ipq5210: Add C3 CPU idle state Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 06/11] arm64: dts: qcom: ipq5210: Add ICE support to SDHCI Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 07/11] arm64: dts: qcom: ipq5210: Enable download mode support Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 08/11] arm64: dts: qcom: ipq5210: Enable the PWM block Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 09/11] arm64: dts: qcom: ipq5210: Add I2C nodes Varadarajan Narayanan
2026-10-08  9:14 ` [PATCH v6 10/11] arm64: dts: qcom: ipq5210: Add SPI node definitions Varadarajan Narayanan
2026-10-08  9:18   ` sashiko-bot
2026-10-08  9:14 ` [PATCH v6 11/11] arm64: dts: qcom: ipq5210: Add random number generator node Varadarajan Narayanan
2026-10-08  9:20   ` sashiko-bot

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=sashiko-outbox-163927@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=varadarajan.narayanan@oss.qualcomm.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 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.