Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 15 Nov 2022 11:16:53 +0000
From:   Mark Brown <broonie@kernel.org>
To:     "Russell King (Oracle)" <linux@armlinux.org.uk>
Cc:     Corentin LABBE <clabbe@baylibre.com>, andrew@lunn.ch,
        calvin.johnson@oss.nxp.com, davem@davemloft.net,
        edumazet@google.com, hkallweit1@gmail.com,
        jernej.skrabec@gmail.com, krzysztof.kozlowski+dt@linaro.org,
        kuba@kernel.org, lgirdwood@gmail.com, pabeni@redhat.com,
        robh+dt@kernel.org, samuel@sholland.org, wens@csie.org,
        devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
        linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev,
        netdev@vger.kernel.org, linux-sunxi@googlegroups.com
Subject: Re: [PATCH v4 1/3] regulator: Add of_regulator_bulk_get_all
Message-ID: <Y3N1JYVx9tB9pisR@sirena.org.uk>
References: <20221115073603.3425396-1-clabbe@baylibre.com>
 <20221115073603.3425396-2-clabbe@baylibre.com>
 <Y3Nj4pA2+WRFvSNd@sirena.org.uk>
 <Y3NnirK0bN71IgCo@Red>
 <Y3NrQffcdGIjS64a@sirena.org.uk>
 <Y3NtKgb0LpWs0RkB@shell.armlinux.org.uk>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="khsmKj4b0178bR6g"
Content-Disposition: inline
In-Reply-To: <Y3NtKgb0LpWs0RkB@shell.armlinux.org.uk>
Precedence: bulk


--khsmKj4b0178bR6g
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Nov 15, 2022 at 10:42:50AM +0000, Russell King (Oracle) wrote:
> On Tue, Nov 15, 2022 at 10:34:41AM +0000, Mark Brown wrote:

> > Well, it's not making this maintainer happy :/  If we know what
> > PHY is there why not just look up the set of supplies based on
> > the compatible of the PHY?

> It looks to me like this series fetches the regulators before the PHY
> is bound to the driver, so what you're proposing would mean that the
> core PHY code would need a table of all compatibles (which is pretty
> hard to do, they encode the vendor/device ID, not some descriptive
> name) and then a list of the regulator names. IMHO that doesn't scale.

Oh, PHYs have interesting enough drivers to dynamically load
here? The last time I was looking at MDIO stuff it was all
running from generic class devices but that was quite a while
ago.

--khsmKj4b0178bR6g
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmNzdSUACgkQJNaLcl1U
h9Dunwf/UIC8Fi+irHTQ/olw2gqDv6691gO5hJTGM3xepy7LuVjmp0NUgHJR3q8G
NPWdNrz0GP3bdx61XL1FlajcfnM/JU5RoMiFAyQmnceuK7P2hmLboHcW85BFGjtc
FP8wgwBiWyrAfZnEePrZcPwxKFpdyUxtX3pkhTWy5+MYsc8H+fBiEpmpOhPu+FYb
gZwx/FeE0fxZQKnViJddT5naB61EZ7OR5EsGjuZP2+AVG8D5c9seFd81V1ulkQKe
IPwRZGjre5377b3iy3gVbtrJ6ol4nN0YmaEkW2eL0BVcDwCCVSkf7nP5rK8QIiAM
8HFyYYD6WtCEjnUU1tyFcRLYPLKJwA==
=KltA
-----END PGP SIGNATURE-----

--khsmKj4b0178bR6g--