From: Michael Tretter <m.tretter@pengutronix.de>
To: Saravana Kannan <saravanak@google.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawnguo@kernel.org>,
kernel@pengutronix.de
Subject: Re: [PATCH] ARM: imx: drop devlinks to reset-controller node
Date: Thu, 23 Sep 2021 10:17:30 +0200 [thread overview]
Message-ID: <20210923081730.GA5613@pengutronix.de> (raw)
In-Reply-To: <d8db15c97cec691fc4537f9f8cbf13e4b0d90013.camel@pengutronix.de>
On Wed, 22 Sep 2021 18:31:17 +0200, Philipp Zabel wrote:
> On Wed, 2021-09-22 at 08:38 -0700, Saravana Kannan wrote:
[...]
> > remote-endpoints always point to each other. So they create dependency
> > cycles and fw_devlink stops enforcing ordering between them (because
> > it's a cycle and it has no way to know which one depends on the other
> > for probing). So for this specific case, you should get away without
> > writing platform drivers.
>
> Right, thank you, I assume there must have been a missing backlink then.
I looked into this and found that remote-endpoints are actually working as
expected. The issue that I was observing was also caused by the missing reset
controller driver.
Thanks,
Michael
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-09-23 8:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-21 12:50 [PATCH] ARM: imx: drop devlinks to reset-controller node Philipp Zabel
2021-09-21 13:19 ` Fabio Estevam
2021-09-21 15:19 ` Philipp Zabel
2021-09-21 15:38 ` Saravana Kannan
2021-09-21 14:45 ` Saravana Kannan
2021-09-21 15:04 ` Philipp Zabel
2021-09-21 15:45 ` Saravana Kannan
2021-09-21 16:47 ` Saravana Kannan
2021-09-22 14:12 ` Philipp Zabel
2021-09-22 15:38 ` Saravana Kannan
2021-09-22 16:31 ` Philipp Zabel
2021-09-22 17:30 ` Saravana Kannan
2021-09-23 8:17 ` Michael Tretter [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=20210923081730.GA5613@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=saravanak@google.com \
--cc=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.