From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: sascha hauer <sha@pengutronix.de>
Cc: Saravana Kannan <saravanak@google.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Daniel Scally <djrscally@gmail.com>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Len Brown <lenb@kernel.org>, peng fan <peng.fan@nxp.com>,
kevin hilman <khilman@kernel.org>,
ulf hansson <ulf.hansson@linaro.org>,
len brown <len.brown@intel.com>, pavel machek <pavel@ucw.cz>,
joerg roedel <joro@8bytes.org>, will deacon <will@kernel.org>,
andrew lunn <andrew@lunn.ch>,
heiner kallweit <hkallweit1@gmail.com>,
russell king <linux@armlinux.org.uk>,
"david s. miller" <davem@davemloft.net>,
eric dumazet <edumazet@google.com>,
jakub kicinski <kuba@kernel.org>, paolo abeni <pabeni@redhat.com>,
linus walleij <linus.walleij@linaro.org>,
hideaki yoshifuji <yoshfuji@linux-ipv6.org>,
david ahern <dsahern@kernel.org>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org, iommu@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-gpio@vger.kernel.org,
kernel@pengutronix.de, devicetree@vger.kernel.org,
linux-acpi@vger.kernel.org
Subject: Re: [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1
Date: Thu, 23 Jun 2022 19:39:06 +0300 [thread overview]
Message-ID: <YrSXKkYfr+Hinsuu@smile.fi.intel.com> (raw)
In-Reply-To: <20220623100421.GY1615@pengutronix.de>
On Thu, Jun 23, 2022 at 12:04:21PM +0200, sascha hauer wrote:
> On Thu, Jun 23, 2022 at 01:03:43AM -0700, Saravana Kannan wrote:
...
> I wonder if it wouldn't be a better approach to just probe all devices
> and record the device(node) they are waiting on. Then you know that you
> don't need to probe them again until the device they are waiting for
> is available.
There may be no device, but resource. And we become again to the something like
deferred probe ugly hack.
The real solution is to rework device driver model in the kernel that it will
create a graph of dependencies and then simply follow it. But actually it should
be more than 1 graph, because there are resources and there are power, clock and
resets that may be orthogonal to the higher dependencies (like driver X provides
a resource to driver Y).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2022-06-23 16:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 8:03 [PATCH v2 0/2] Fix console probe delay due to fw_devlink Saravana Kannan
2022-06-23 8:03 ` [PATCH v2 1/2] driver core: fw_devlink: Allow firmware to mark devices as best effort Saravana Kannan
2022-06-23 8:03 ` [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1 Saravana Kannan
2022-06-23 10:04 ` sascha hauer
2022-06-23 16:39 ` Andy Shevchenko [this message]
2022-06-23 17:22 ` Rafael J. Wysocki
2022-06-23 17:30 ` Saravana Kannan
2022-06-23 17:26 ` Saravana Kannan
2022-06-23 17:35 ` Ahmad Fatoum
2022-06-23 18:17 ` Saravana Kannan
2022-06-23 20:37 ` sascha hauer
2022-06-23 23:13 ` Saravana Kannan
2022-06-27 17:50 ` Rob Herring
2022-06-27 18:20 ` Saravana Kannan
2022-06-28 13:41 ` Linus Walleij
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=YrSXKkYfr+Hinsuu@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=djrscally@gmail.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=frowand.list@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=hkallweit1@gmail.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=kernel@pengutronix.de \
--cc=khilman@kernel.org \
--cc=kuba@kernel.org \
--cc=len.brown@intel.com \
--cc=lenb@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavel@ucw.cz \
--cc=peng.fan@nxp.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=saravanak@google.com \
--cc=sha@pengutronix.de \
--cc=ulf.hansson@linaro.org \
--cc=will@kernel.org \
--cc=yoshfuji@linux-ipv6.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;
as well as URLs for NNTP newsgroup(s).