From: Johan Hovold <johan@kernel.org>
To: Songwei Chai <songwei.chai@oss.qualcomm.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
songchai@qti.qualcomm.com, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, coresight@lists.linaro.org,
devicetree@vger.kernel.org,
Saravana Kannan <saravanak@kernel.org>
Subject: Re: [PATCH v1] driver core: Demote "Fixed dependency cycle(s)" message to debug level
Date: Fri, 6 Nov 2026 09:50:22 +0100 [thread overview]
Message-ID: <au2UzljzfMaiL7F6@hovoldconsulting.com> (raw)
In-Reply-To: <20261106084034.1579494-1-songwei.chai@oss.qualcomm.com>
[ +CC: Saravana ]
On Fri, Nov 06, 2026 at 04:40:34PM +0800, Songwei Chai wrote:
> fw_devlink detects and relaxes dependency cycles automatically, so this
> is not an error condition requiring user action. On complex DT
> topologies (e.g. CoreSight), this message can fire for many node
> pairs and adds noise to the boot log, even though it's primarily
> useful for debugging. Switch pr_info() to pr_debug() so it stays
> available via dynamic debug when actually needed, without cluttering
> default boot logs.
>
> For example, on sm8750 this produces 125 such lines in the boot log in
> total, 80 of which are CoreSight-related, e.g.:
>
> [ 0.057190] /soc@0/funnel@10041000: Fixed dependency cycle(s) with /soc@0/stm@10002000
> [ 0.057211] /soc@0/stm@10002000: Fixed dependency cycle(s) with /soc@0/funnel@10041000
> [ 0.057229] /soc@0/funnel@10041000: Fixed dependency cycle(s) with /soc@0/tpda@10004000
> [ 0.057249] /soc@0/tpda@10004000: Fixed dependency cycle(s) with /soc@0/funnel@10041000
> [ 0.057254] /soc@0/tpdm@1000f000: Fixed dependency cycle(s) with /soc@0/tpda@10004000
> [ 0.057260] /soc@0/tpda@10004000: Fixed dependency cycle(s) with /soc@0/tpdm@1000f000
I reported this elsewhere a while back:
https://lore.kernel.org/all/Z6t45aOGDkotqM4Z@hovoldconsulting.com/
Are you sure it's not the coresight bindings that should be fixed?
Johan
prev parent reply other threads:[~2026-11-06 8:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 8:40 Songwei Chai
2026-11-06 8:50 ` 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=au2UzljzfMaiL7F6@hovoldconsulting.com \
--to=johan@kernel.org \
--cc=coresight@lists.linaro.org \
--cc=dakr@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=saravanak@kernel.org \
--cc=songchai@qti.qualcomm.com \
--cc=songwei.chai@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®