[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZyThAFbOHKaBIgLg@hovoldconsulting.com>
Date: Fri, 1 Nov 2024 15:09:04 +0100
From: Johan Hovold <johan@...nel.org>
To: Sibi Sankar <quic_sibis@...cinc.com>
Cc: sudeep.holla@....com, cristian.marussi@....com, ulf.hansson@...aro.org,
jassisinghbrar@...il.com, dmitry.baryshkov@...aro.org,
linux-kernel@...r.kernel.org, arm-scmi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, linux-arm-msm@...r.kernel.org,
konradybcio@...nel.org, linux-pm@...r.kernel.org,
tstrudel@...gle.com, rafael@...nel.org,
Johan Hovold <johan+linaro@...nel.org>
Subject: Re: [PATCH V5 3/6] firmware: arm_scmi: Report duplicate opps as
firmware bugs
On Wed, Oct 30, 2024 at 06:25:09PM +0530, Sibi Sankar wrote:
> Duplicate opps reported by buggy SCP firmware currently show up
> as warnings even though the only functional impact is that the
> level/index remain inaccessible. Make it less scary for the end
> user by using dev_info instead, along with FW_BUG tag.
>
> Suggested-by: Johan Hovold <johan+linaro@...nel.org>
> Signed-off-by: Sibi Sankar <quic_sibis@...cinc.com>
> ---
> drivers/firmware/arm_scmi/perf.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/firmware/arm_scmi/perf.c b/drivers/firmware/arm_scmi/perf.c
> index 32f9a9acd3e9..c7e5a34b254b 100644
> --- a/drivers/firmware/arm_scmi/perf.c
> +++ b/drivers/firmware/arm_scmi/perf.c
> @@ -387,7 +387,7 @@ process_response_opp(struct device *dev, struct perf_dom_info *dom,
>
> ret = xa_insert(&dom->opps_by_lvl, opp->perf, opp, GFP_KERNEL);
> if (ret) {
> - dev_warn(dev, "Failed to add opps_by_lvl at %d for %s - ret:%d\n",
> + dev_info(dev, FW_BUG "Failed to add opps_by_lvl at %d for %s - ret:%d\n",
> opp->perf, dom->info.name, ret);
I was hoping you could make the error message a bit more informative as
well, for example, by saying that a duplicate opp level was ignored:
arm-scmi arm-scmi.0.auto: [Firmware Bug]: Ignoring duplicate OPP 3417600 for NCC
or similar (e.g. as the current message looks like an error, with errno
and all, that indeed warrants warning level).
Perhaps with such a message you could even keep the warning level to
make it stand out more (if that's desirable) without the risk of scaring
users.
Johan
Powered by blists - more mailing lists