[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YSlG4XRGrq5D1/WU@lunn.ch>
Date: Fri, 27 Aug 2021 22:11:13 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Saravana Kannan <saravanak@...gle.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Linus Walleij <linus.walleij@...aro.org>,
Vivien Didelot <vivien.didelot@...il.com>,
Florian Fainelli <f.fainelli@...il.com>,
Vladimir Oltean <olteanv@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>, Len Brown <lenb@...nel.org>,
Alvin Sipraga <ALSI@...g-olufsen.dk>, kernel-team@...roid.com,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
linux-acpi@...r.kernel.org
Subject: Re: [PATCH v1 1/2] driver core: fw_devlink: Add support for
FWNODE_FLAG_BROKEN_PARENT
> > I've not yet looked at plain Ethernet drivers. This pattern could also
> > exist there. And i wonder about other complex structures, i2c bus
> > multiplexors, you can have interrupt controllers as i2c devices,
> > etc. So the general case could exist in other places.
>
> I haven't seen any generic issues like this reported so far. It's only
> after adding phy-handle that we are hitting these issues with DSA
> switches.
Can you run your parser over the 2250 DTB blobs and see how many
children have dependencies on a parent? That could give us an idea how
many moles need whacking. And maybe, where in the tree they are
hiding?
Andrew
Powered by blists - more mailing lists