MIME-Version: 1.0
References: <20230317113427.302162-1-noltari@gmail.com> <20230317113427.302162-3-noltari@gmail.com>
 <20230317115115.s32r52rz3svuj4ed@skbuf> <CAKR-sGe3xHkN-1+aLn0ixnskctPK4GTzfXu8O_dkFhHyY1nTeg@mail.gmail.com>
 <20230317130434.7cbzk5gxx5guarcz@skbuf> <CAKR-sGeFZLnuqH=4Gok1URJEvrQKxbk203Q8zdMd9830G_XD7A@mail.gmail.com>
 <1ed6d7d9-4d3e-4bcb-8023-75bb52c2f272@lunn.ch>
In-Reply-To: <1ed6d7d9-4d3e-4bcb-8023-75bb52c2f272@lunn.ch>
From:   =?UTF-8?B?w4FsdmFybyBGZXJuw6FuZGV6IFJvamFz?= <noltari@gmail.com>
Date:   Fri, 17 Mar 2023 17:30:38 +0100
Message-ID: <CAKR-sGfMF+UtL4kY2hJ9gw4=jQu1JAqqF3N0obeUE=vGj8R-yA@mail.gmail.com>
Subject: Re: [PATCH 2/3] net: dsa: b53: mmap: register MDIO Mux bus controller
To:     Andrew Lunn <andrew@lunn.ch>
Cc:     Vladimir Oltean <olteanv@gmail.com>, davem@davemloft.net,
        edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
        robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
        f.fainelli@gmail.com, jonas.gorski@gmail.com, hkallweit1@gmail.com,
        linux@armlinux.org.uk, netdev@vger.kernel.org,
        devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

El vie, 17 mar 2023 a las 17:27, Andrew Lunn (<andrew@lunn.ch>) escribi=C3=
=B3:
>
> > > The proposed solution is too radical for a problem that was not prope=
rly
> > > 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.

Ok, I'm open to suggestions.
Any ideas on how exactly to figure out when it's a good time to probe
or return -EPROBE_DEFER instead?

>
>   Andrew

--
=C3=81lvaro.