From: sashiko-bot@kernel.org
To: "Alex Tran" <alex.tran@oss.qualcomm.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 1/5] powercap: arm_scmi_powercap: Log number of powercap domains
Date: Thu, 14 May 2026 08:00:05 +0000 [thread overview]
Message-ID: <20260514080006.0E7F1C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260513-scmi-client-probe-log-v2-1-36607e9dd540@oss.qualcomm.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Medium] The log message incorrectly reports the number of 'Initialized' domains using the count of 'Discovered' domains, leading to inaccurate and contradictory logs.
- [Low] Format string type mismatch for `pr->num_zones`.
--
commit bbfaa4d885154a2acd690976aeb604fa1c8f0eb4
Author: Alex Tran <alex.tran@oss.qualcomm.com>
powercap: arm_scmi_powercap: Log number of powercap domains
This commit adds a debug log to report the number of powercap domains
discovered from the firmware during probe. This helps confirm the firmware
exposed powercap resources.
> diff --git a/drivers/powercap/arm_scmi_powercap.c b/drivers/powercap/arm_scmi_powercap.c
> index ab66e9a3b1e2c..3efe3743cce0a 100644
> --- a/drivers/powercap/arm_scmi_powercap.c
> +++ b/drivers/powercap/arm_scmi_powercap.c
[ ... ]
> @@ -496,6 +496,7 @@ static int scmi_powercap_probe(struct scmi_device *sdev)
> return ret;
>
> dev_set_drvdata(dev, pr);
> + dev_dbg(dev, "Initialized %d powercap domains\n", pr->num_zones);
Are all of these domains actually initialized?
During the probe process, domains using an abstract power scale are
explicitly skipped and marked as invalid (spz->invalid = true).
scmi_zones_register() also tracks and logs the actual successfully
registered count.
If there are skipped domains, this will produce confusing logs, such as
"Registered 3 SCMI Powercap domains !" from scmi_zones_register() followed
by "Initialized 5 powercap domains" here.
Should the log message say "Discovered" instead of "Initialized" to match
the commit message?
Also, this isn't a bug, but does this code use the correct format specifier
for pr->num_zones? Since num_zones is an unsigned int in struct
scmi_powercap_root, should this use %u instead of %d?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-scmi-client-probe-log-v2-0-36607e9dd540@oss.qualcomm.com?part=1
next prev parent reply other threads:[~2026-05-14 8:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 17:16 [PATCH v2 0/5] scmi: Log client subsystem entity counts Alex Tran
2026-05-13 17:16 ` [PATCH v2 1/5] powercap: arm_scmi_powercap: Log number of powercap domains Alex Tran
2026-05-14 8:00 ` sashiko-bot [this message]
2026-05-13 17:16 ` [PATCH v2 2/5] cpufreq: scmi-cpufreq: Log number of perf domains Alex Tran
2026-05-14 8:42 ` sashiko-bot
2026-05-13 17:16 ` [PATCH v2 3/5] hwmon: scmi-hwmon: Log number of sensors Alex Tran
2026-05-14 9:29 ` sashiko-bot
2026-05-13 17:16 ` [PATCH v2 4/5] reset: reset-scmi: Log number of reset domains Alex Tran
2026-05-14 9:43 ` sashiko-bot
2026-05-13 17:16 ` [PATCH v2 5/5] pinctrl: pinctrl-scmi: Log number of pins, groups, functions Alex Tran
2026-05-13 18:06 ` Andy Shevchenko
2026-05-14 10:22 ` sashiko-bot
2026-05-13 18:04 ` [PATCH v2 0/5] scmi: Log client subsystem entity counts Andy Shevchenko
2026-05-14 15:44 ` Jonathan Cameron
2026-05-14 18:42 ` Sudeep Holla
2026-05-14 21:23 ` Alex Tran
2026-05-15 8:29 ` Sudeep Holla
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=20260514080006.0E7F1C2BCB7@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=alex.tran@oss.qualcomm.com \
--cc=linux-hwmon@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox