Thread (15 messages) 15 messages, 7 authors, 2022-06-28

Re: [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1

From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Date: 2022-06-23 16:39:25
Also in: linux-acpi, linux-gpio, linux-iommu, linux-pm, lkml, netdev

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

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help