From: Johan Hovold <johan@kernel.org>
To: Jie Gan <quic_jiegan@quicinc.com>
Cc: Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Yushan Li <quic_yushli@quicinc.com>
Subject: Re: [PATCH RESEND v5] arm64: dts: qcom: Add coresight nodes for x1e80100
Date: Tue, 11 Feb 2025 17:20:53 +0100 [thread overview]
Message-ID: <Z6t45aOGDkotqM4Z@hovoldconsulting.com> (raw)
In-Reply-To: <fe6c7c26-91d6-402f-80b6-018ee40e9ed7@quicinc.com>
On Tue, Feb 11, 2025 at 09:37:43AM +0800, Jie Gan wrote:
> On 2/10/2025 9:47 PM, Johan Hovold wrote:
> > This patch is now in 6.14-rc1 and results in the logs being spammed with
> > 200+ messages about cyclic dependencies. I'd expect something like this
> > to at least be mentioned in the commit message:
> >
> > [ 0.250732] /soc@0/stm@10002000: Fixed dependency cycle(s) with /soc@0/funnel@10041000
> > [ 0.250854] /soc@0/tpda@10004000: Fixed dependency cycle(s) with /soc@0/funnel@10041000
> > ...
> > [ 0.301582] /soc@0/funnel@10d13000: Fixed dependency cycle(s) with /soc@0/funnel@10d04000
> > [ 0.301639] /soc@0/funnel@10d13000: Fixed dependency cycle(s) with /soc@0/tpda@10d12000
> >
> > [ 0.317624] Callback from call_rcu_tasks() invoked.
> >
> > Has anyone looked into what is causing this and if anything can be done
> > about it?
> These lines have been printed by following API,
> fw_devlink_create_devlink, it's pr_info:
>
> ...
> device_links_write_lock();
> if (__fw_devlink_relax_cycles(link->consumer, sup_handle)) {
> __fwnode_link_cycle(link);
> pr_debug("----- cycle: end -----\n");
> pr_info("%pfwf: Fixed dependency cycle(s) with %pfwf\n",
> link->consumer, sup_handle);
> }
> ...
Right, and we had a few of these already, but not several hundreds. I
meant to ask if anyone has looked into whether this indicates a problem
with the patch or binding (or devlink code) or if these notifications
are simply expected.
> I am not sure we can change it to pr_debug to decrease annoying messages.
That may be an option, but I assume the current printk level is used so
that people get a chance to spot potential issues. Otherwise, we should
definitely silence it.
Johan
prev parent reply other threads:[~2025-02-11 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 5:49 [PATCH RESEND v5] arm64: dts: qcom: Add coresight nodes for x1e80100 Jie Gan
2025-01-07 16:38 ` Bjorn Andersson
2025-02-10 13:47 ` Johan Hovold
2025-02-11 1:37 ` Jie Gan
2025-02-11 16:20 ` Johan Hovold [this message]
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=Z6t45aOGDkotqM4Z@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=quic_jiegan@quicinc.com \
--cc=quic_yushli@quicinc.com \
--cc=robh@kernel.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