All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tudor Ambarus" <tudor.ambarus@linaro.org>
Cc: conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 1/5] dt-bindings: thermal: Add Google GS101 TMU
Date: Mon, 25 May 2026 12:54:54 +0000	[thread overview]
Message-ID: <20260525125455.AF31A1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260525-acpm-tmu-v5-1-85fde739752e@linaro.org>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The `samsung,acpm-ipc` property is missing from the `required` list despite being functionally mandatory for device operation.
--

commit f4129715b1366153f8c291ba713ab0836fdf5768
Author: Tudor Ambarus <tudor.ambarus@linaro.org>

dt-bindings: thermal: Add Google GS101 TMU

Document the Thermal Management Unit found on the Google GS101 SoC.
This hardware uses a hybrid control model where the Application Processor
delegates high-level functional tasks to the ACPM firmware via IPC.

> diff --git a/Documentation/devicetree/bindings/thermal/google,gs101-tmu-top.yaml b/Documentation/devicetree/bindings/thermal/google,gs101-tmu-top.yaml
> new file mode 100644
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/thermal/google,gs101-tmu-top.yaml

[ ... ]

> +  samsung,acpm-ipc:
> +    $ref: /schemas/types.yaml#/definitions/phandle
> +    description: Phandle to the ACPM IPC node.
> +
> +required:
> +  - compatible
> +  - reg
> +  - clocks
> +  - interrupts
> +  - "#thermal-sensor-cells"

[Severity: Medium]
Since the commit message and binding description indicate that the
Application Processor relies entirely on the ACPM firmware for all
functional TMU tasks, shouldn't samsung,acpm-ipc be included in this
required list?

Without it, incomplete device tree nodes might silently pass schema
validation.

> +
> +additionalProperties: false

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260525-acpm-tmu-v5-0-85fde739752e@linaro.org?part=1

  reply	other threads:[~2026-05-25 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-25 12:50 [PATCH v5 0/5] thermal: samsung: Add support for Google GS101 TMU Tudor Ambarus
2026-05-25 12:50 ` [PATCH v5 1/5] dt-bindings: thermal: Add " Tudor Ambarus
2026-05-25 12:54   ` sashiko-bot [this message]
2026-05-25 13:06     ` Tudor Ambarus
2026-05-26  9:39       ` Krzysztof Kozlowski
2026-05-26 10:02         ` Tudor Ambarus
2026-05-26 14:34           ` Krzysztof Kozlowski
2026-05-26 14:36             ` Tudor Ambarus
2026-05-25 12:50 ` [PATCH v5 2/5] thermal: samsung: Add Exynos ACPM TMU driver GS101 Tudor Ambarus
2026-05-25 13:21   ` sashiko-bot
2026-05-25 12:50 ` [PATCH v5 3/5] MAINTAINERS: Add entry for Samsung Exynos ACPM thermal driver Tudor Ambarus
2026-05-25 12:50 ` [PATCH v5 4/5] arm64: dts: exynos: gs101: Add thermal management unit Tudor Ambarus
2026-05-25 12:50 ` [PATCH v5 5/5] arm64: defconfig: enable Exynos ACPM thermal support Tudor Ambarus
2026-05-26  9:42   ` Krzysztof Kozlowski
2026-05-25 13:15 ` [PATCH v5 0/5] thermal: samsung: Add support for Google GS101 TMU Krzysztof Kozlowski

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=20260525125455.AF31A1F000E9@smtp.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=tudor.ambarus@linaro.org \
    /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.