Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Alex Tran" <alex.tran@oss.qualcomm.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v2 2/5] cpufreq: scmi-cpufreq: Log number of perf domains
Date: Thu, 14 May 2026 08:42:46 +0000	[thread overview]
Message-ID: <20260514084246.F03A5C2BCB7@smtp.kernel.org> (raw)
In-Reply-To: <20260513-scmi-client-probe-log-v2-2-36607e9dd540@oss.qualcomm.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Misleading debug log message contradicts driver behavior and commit message.
--

commit 1a4bf472420109c67d582c98f4a85ffbf1fdd048
Author: Alex Tran <alex.tran@oss.qualcomm.com>

cpufreq: scmi-cpufreq: Log number of perf domains

This commit adds a debug log to the SCMI cpufreq driver to report the
number of performance domains discovered from firmware.

> diff --git a/drivers/cpufreq/scmi-cpufreq.c b/drivers/cpufreq/scmi-cpufreq.c
> index 4edb4f7a8aa97..f4cf59d862c61 100644
> --- a/drivers/cpufreq/scmi-cpufreq.c
> +++ b/drivers/cpufreq/scmi-cpufreq.c
> @@ -468,9 +468,12 @@ static int scmi_cpufreq_probe(struct scmi_device *sdev)

[ ... ]

>  	if (ret) {
>  		dev_err(dev, "%s: registering cpufreq failed, err: %d\n",
>  			__func__, ret);
> +		return ret;
>  	}
>  
> -	return ret;
> +	dev_dbg(dev, "Initialized %d performance domains\n",
> +		 perf_ops->num_domains_get(ph));

The commit message states the intent is to log the number of domains
"discovered from firmware". Does the wording "Initialized" in this log
message accurately reflect the driver's behavior?

The driver primarily registers the cpufreq driver and does not actually
initialize the SCMI performance domains. Additionally, num_domains_get()
returns the total count of SCMI performance domains exposed by the
firmware, which may also include non-CPU domains like GPUs.

Would a word like "Discovered" be more appropriate here?

> +	return 0;
>  }

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260513-scmi-client-probe-log-v2-0-36607e9dd540@oss.qualcomm.com?part=2

  reply	other threads:[~2026-05-14  8:42 UTC|newest]

Thread overview: 16+ 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
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 [this message]
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

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=20260514084246.F03A5C2BCB7@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