[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ed6d7d9-4d3e-4bcb-8023-75bb52c2f272@lunn.ch>
Date: Fri, 17 Mar 2023 17:26:56 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Álvaro Fernández Rojas <noltari@...il.com>
Cc: Vladimir Oltean <olteanv@...il.com>, davem@...emloft.net,
edumazet@...gle.com, kuba@...nel.org, pabeni@...hat.com,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
f.fainelli@...il.com, jonas.gorski@...il.com, hkallweit1@...il.com,
linux@...linux.org.uk, netdev@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] net: dsa: b53: mmap: register MDIO Mux bus controller
> > The proposed solution is too radical for a problem that was not properly
> > characterized yet, so this patch set has my temporary NACK.
>
> Forgive me, but why do you consider this solution too radical?
I have to agree with Vladimir here. The problem is not the driver, but
when the driver is instantiated. It seems radical to remove a driver
just because it loads at the wrong time. Ideally you want the driver
to figure out now is not a good time and return -EPROBE_DEFER, because
a resource it requires it not available.
Andrew
Powered by blists - more mailing lists