From: Johan Hovold <johan@kernel.org>
To: Sibi Sankar <quic_sibis@quicinc.com>
Cc: sudeep.holla@arm.com, cristian.marussi@arm.com,
ulf.hansson@linaro.org, jassisinghbrar@gmail.com,
linux-kernel@vger.kernel.org, arm-scmi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, konradybcio@kernel.org,
linux-pm@vger.kernel.org, tstrudel@google.com, rafael@kernel.org
Subject: Re: [PATCH V3 0/4] firmware: arm_scmi: Misc Fixes
Date: Wed, 23 Oct 2024 18:26:16 +0200 [thread overview]
Message-ID: <ZxkjqEmkBAsC6UkL@hovoldconsulting.com> (raw)
In-Reply-To: <ae5eaef9-301f-7d3f-c973-faa22ae780ee@quicinc.com>
On Wed, Oct 23, 2024 at 01:16:47PM +0530, Sibi Sankar wrote:
> On 10/10/24 20:32, Johan Hovold wrote:
> > On Mon, Oct 07, 2024 at 11:36:38AM +0530, Sibi Sankar wrote:
> >> The series addresses the kernel warnings reported by Johan at [1] and are
> >> are required to X1E cpufreq device tree changes [2] to land.
> >>
> >> [1] - https://lore.kernel.org/lkml/ZoQjAWse2YxwyRJv@hovoldconsulting.com/
> >> [2] - https://lore.kernel.org/lkml/20240612124056.39230-1-quic_sibis@quicinc.com/
> >>
> >> The following warnings remain unadressed:
> >> arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16
> >> arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16
> >
> > Are there any plans for how to address these?
> Sorry missed replying to this. The error implies that duplicate
> opps are reported by the SCP firmware and appear once during probe.
I only see it at boot, but it shows up four times here with the CRD:
[ 8.098452] arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16
[ 8.109647] arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16
[ 8.128970] arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16
[ 8.142455] arm-scmi arm-scmi.0.auto: Failed to add opps_by_lvl at 3417600 for NCC - ret:-16
> This particular error can be fixed only by a firmware update and you
> should be able to test it out soon on the CRD first.
Can you explain why this can only be fixed by a firmware update? Why
can't we suppress these warnings as well, like we did for the other
warnings related to the duplicate entries?
IIUC the firmware is not really broken, but rather describes a feature
that Linux does not (yet) support, right?
Johan
next prev parent reply other threads:[~2024-10-23 16:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 6:06 [PATCH V3 0/4] firmware: arm_scmi: Misc Fixes Sibi Sankar
2024-10-07 6:06 ` [PATCH V3 1/4] firmware: arm_scmi: Ensure that the message-id supports fastchannel Sibi Sankar
2024-10-09 13:46 ` Sudeep Holla
2024-10-10 14:55 ` Johan Hovold
2024-10-07 6:06 ` [PATCH V3 2/4] firmware: arm_scmi: Skip adding bad duplicates Sibi Sankar
2024-10-07 6:06 ` [PATCH V3 3/4] pmdomain: core: Fix debugfs node creation failure Sibi Sankar
2024-10-07 17:33 ` Dmitry Baryshkov
2024-10-09 11:11 ` Ulf Hansson
2024-10-10 12:47 ` Dmitry Baryshkov
2024-10-07 6:06 ` [PATCH V3 4/4] mailbox: qcom-cpucp: Mark the irq with IRQF_NO_SUSPEND flag Sibi Sankar
2024-10-07 13:14 ` Konrad Dybcio
2024-10-10 14:58 ` Johan Hovold
2024-10-09 11:14 ` [PATCH V3 0/4] firmware: arm_scmi: Misc Fixes Ulf Hansson
2024-10-10 15:02 ` Johan Hovold
2024-10-23 7:46 ` Sibi Sankar
2024-10-23 16:26 ` Johan Hovold [this message]
2024-10-25 6:08 ` Sibi Sankar
2024-10-25 6:14 ` Dmitry Baryshkov
2024-10-25 6:45 ` Sibi Sankar
2024-10-25 8:28 ` Cristian Marussi
2024-10-25 10:11 ` Dmitry Baryshkov
2024-10-25 10:29 ` Cristian Marussi
2024-10-25 11:37 ` Dmitry Baryshkov
2024-10-25 13:32 ` Johan Hovold
2024-10-25 13:48 ` Cristian Marussi
2024-10-25 13:23 ` Johan Hovold
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=ZxkjqEmkBAsC6UkL@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=jassisinghbrar@gmail.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=quic_sibis@quicinc.com \
--cc=rafael@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tstrudel@google.com \
--cc=ulf.hansson@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox