lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 23 Jun 2022 19:39:06 +0300 From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com> To: sascha hauer <sha@...gutronix.de> Cc: Saravana Kannan <saravanak@...gle.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "Rafael J. Wysocki" <rafael@...nel.org>, Rob Herring <robh+dt@...nel.org>, Frank Rowand <frowand.list@...il.com>, Daniel Scally <djrscally@...il.com>, Heikki Krogerus <heikki.krogerus@...ux.intel.com>, Sakari Ailus <sakari.ailus@...ux.intel.com>, Len Brown <lenb@...nel.org>, peng fan <peng.fan@....com>, kevin hilman <khilman@...nel.org>, ulf hansson <ulf.hansson@...aro.org>, len brown <len.brown@...el.com>, pavel machek <pavel@....cz>, joerg roedel <joro@...tes.org>, will deacon <will@...nel.org>, andrew lunn <andrew@...n.ch>, heiner kallweit <hkallweit1@...il.com>, russell king <linux@...linux.org.uk>, "david s. miller" <davem@...emloft.net>, eric dumazet <edumazet@...gle.com>, jakub kicinski <kuba@...nel.org>, paolo abeni <pabeni@...hat.com>, linus walleij <linus.walleij@...aro.org>, hideaki yoshifuji <yoshfuji@...ux-ipv6.org>, david ahern <dsahern@...nel.org>, kernel-team@...roid.com, linux-kernel@...r.kernel.org, linux-pm@...r.kernel.org, iommu@...ts.linux-foundation.org, netdev@...r.kernel.org, linux-gpio@...r.kernel.org, kernel@...gutronix.de, devicetree@...r.kernel.org, linux-acpi@...r.kernel.org Subject: Re: [PATCH v2 2/2] of: base: Avoid console probe delay when fw_devlink.strict=1 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
Powered by blists - more mailing lists