From: sashiko-bot@kernel.org
To: "Ronald Claveau via B4 Relay"
<devnull+linux-kernel-dev.aliel.fr@kernel.org>
Cc: neil.armstrong@linaro.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v3] thermal: amlogic: add missing dependency on MESON_SM
Date: Tue, 02 Jun 2026 14:34:00 +0000 [thread overview]
Message-ID: <20260602143400.8E5571F00893@smtp.kernel.org> (raw)
In-Reply-To: <20260602-fix-missing-meson_sm-symbol-v3-1-6f7f69cd7d6c@aliel.fr>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [High] The commit introduces a spurious `depends on MESON_SM` dependency for `CONFIG_AMLOGIC_THERMAL` based on the false premise that the driver calls `meson_sm_get()` and `meson_sm_get_thermal_calib()`. An analysis of `drivers/thermal/amlogic_thermal.c` confirms it relies on a syscon regmap (`amlogic,ao-secure`) for its calibration data and makes no calls to the secure monitor driver. Crucially, `MESON_SM` strictly depends on `ARM64_4K_PAGES`. Thus, this patch inadvertently disables thermal management on all Amlogic systems using 16K or 64K page sizes, or those intentionally omitting `MESON_SM`.
--
commit f9c3b9097ac770542e726a379a07047abb369bae
Author: Ronald Claveau <linux-kernel-dev@aliel.fr>
thermal: amlogic: add missing dependency on MESON_SM
This commit adds a dependency on MESON_SM to the Amlogic thermal driver
configuration to address reported undefined references.
Link: https://lore.kernel.org/oe-kbuild-all/202605291530.en7aGn7w-lkp@intel.com/
> diff --git a/drivers/thermal/Kconfig b/drivers/thermal/Kconfig
> --- a/drivers/thermal/Kconfig
> +++ b/drivers/thermal/Kconfig
> @@ -436,6 +436,7 @@ config AMLOGIC_THERMAL
> tristate "Amlogic Thermal Support"
> default ARCH_MESON
> depends on OF && ARCH_MESON
> + depends on MESON_SM
[Severity: High]
The commit message states that the amlogic thermal driver calls
meson_sm_get() and meson_sm_get_thermal_calib(). Is this description
accurate?
Looking at drivers/thermal/amlogic_thermal.c, the driver appears to rely on a
syscon regmap (amlogic,ao-secure) for its calibration data, rather than making
direct calls to the secure monitor.
Since MESON_SM has a strict dependency on ARM64_4K_PAGES, wouldn't adding
this dependency inadvertently disable thermal management on all Amlogic
systems using 16K or 64K page sizes, or those intentionally omitting MESON_SM?
Without thermal management, these systems might suffer from a lack of
active cooling or thermal throttling.
> help
> If you say yes here you get support for Amlogic Thermal
> for G12 SoC Family.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260602-fix-missing-meson_sm-symbol-v3-1-6f7f69cd7d6c@aliel.fr?part=1
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2026-06-02 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 14:19 Ronald Claveau via B4 Relay
2026-06-02 14:34 ` sashiko-bot [this message]
2026-06-02 16:01 ` Daniel Lezcano
2026-06-02 16:26 ` linux-kernel-dev
2026-06-02 21:08 ` Daniel Lezcano
2026-06-03 5:36 ` linux-kernel-dev
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=20260602143400.8E5571F00893@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=devnull+linux-kernel-dev.aliel.fr@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=neil.armstrong@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox