From: sashiko-bot@kernel.org
To: "Gaurav Kohli" <gaurav.kohli@oss.qualcomm.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH v3 5/6] arm64: dts: qcom: kodiak: use thermal hw-bin trips
Date: Fri, 13 Nov 2026 08:59:31 +0000 [thread overview]
Message-ID: <sashiko-outbox-212488@kernel.org> (raw)
In-Reply-To: <20261113-thermal_bin-v3-5-878df6eef8bc@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] arm64: dts: qcom: kodiak: duplicate @180 unit-address in qfprom
--
commit e6d4eae865bd91c0bd0f76066337d957b0861f51
Author: Amit Kucheria <amit.kucheria@oss.qualcomm.com>
arm64: dts: qcom: kodiak: use thermal hw-bin trips
This commit adds jtag-id and feat-id nvmem cells to the tsens nodes in
kodiak.dtsi and converts passive mitigation trip points to per-bin
temperature values.
> diff --git a/arch/arm64/boot/dts/qcom/kodiak.dtsi b/arch/arm64/boot/dts/qcom/kodiak.dtsi
> index 10e9a5279ed60..79553bf43a7a2 100644
> --- a/arch/arm64/boot/dts/qcom/kodiak.dtsi
> +++ b/arch/arm64/boot/dts/qcom/kodiak.dtsi
> @@ -1028,6 +1028,18 @@ gpu_speed_bin: gpu-speed-bin@1e9 {
> reg = <0x1e9 0x2>;
> bits = <5 8>;
> };
> +
> + jtag_id: jtag-id@180 {
> + reg = <0x180 0x4>;
> + /* bits = <offset width>: 20 bits at offset 0 */
> + bits = <0 20>;
> + };
> +
> + feat_id: feat-id@180 {
> + reg = <0x180 0x4>;
> + /* bits = <offset width>: 8 bits at offset 20 */
> + bits = <20 8>;
> + };
> };
[Severity: Low]
Does giving both jtag-id@180 and feat-id@180 the same @180 unit-address
trigger a dtc unique_unit_address warning when building DTBs with W=1?
qfprom_fixup_dt_cell_info() aligns byte-addressed QFPROM cells to 4-byte
words at runtime, so feat-id can be described at its starting byte offset
(feat-id@182 with reg = <0x182 0x2> and bits = <4 8>, and jtag-id@180 with
reg = <0x180 0x3>), placed before gpu-speed-bin@1e9 in ascending
unit-address order.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-thermal_bin-v3-0-878df6eef8bc@oss.qualcomm.com?part=5
next prev parent reply other threads:[~2026-11-13 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 8:43 [PATCH v3 0/6] thermal: Add hardware-binned trip point support Gaurav Kohli
2026-11-13 8:43 ` [PATCH v3 1/6] dt-bindings: thermal: thermal-zones: add hardware-binning trip properties Gaurav Kohli
2026-11-13 8:43 ` [PATCH v3 2/6] thermal: add hardware-binning trip-point filtering support Gaurav Kohli
2026-11-13 9:01 ` sashiko-bot
2026-11-13 8:43 ` [PATCH v3 3/6] dt-bindings: thermal: qcom-tsens: document qcm6490 tsens Gaurav Kohli
2026-11-13 8:43 ` [PATCH v3 4/6] thermal: qcom: tsens: add hardware-bin trip-point filtering Gaurav Kohli
2026-11-13 8:55 ` sashiko-bot
2026-11-13 8:43 ` [PATCH v3 5/6] arm64: dts: qcom: kodiak: use thermal hw-bin trips Gaurav Kohli
2026-11-13 8:59 ` sashiko-bot [this message]
2026-11-13 8:43 ` [PATCH v3 6/6] arm64: dts: qcom: hamoa: add thermal hw-bin support Gaurav Kohli
2026-11-13 9:00 ` 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-212488@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gaurav.kohli@oss.qualcomm.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.