Received-SPF: pass (google.com: domain of linux-kernel+bounces-162609-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Tue, 30 Apr 2024 00:47:52 +0900
From: Mark Brown <broonie@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Kory Maincent <kory.maincent@bootlin.com>,
	Oleksij Rempel <o.rempel@pengutronix.de>,
	Kyle Swenson <kyle.swenson@est.tech>,
	Liam Girdwood <lgirdwood@gmail.com>, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: PoE complex usage of regulator API
Message-ID: <Zi_BKFa4Sk3IAFFU@finisterre.sirena.org.uk>
References: <20240426124253.56fd0933@kmaincent-XPS-13-7390>
 <57a79abd-722c-4907-b0e7-2396392ae675@lunn.ch>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="z0k5BVdQYkZbQzID"
Content-Disposition: inline
In-Reply-To: <57a79abd-722c-4907-b0e7-2396392ae675@lunn.ch>


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

On Sat, Apr 27, 2024 at 12:41:19AM +0200, Andrew Lunn wrote:

> I'm assuming this is mostly about book keeping? When a regulator is
> created, we want to say is can deliver up to X Kilowatts. We then want
> to allocate power to ports. So there needs to be a call asking it to
> allocate part of X to a consumer, which could fail if there is not
> sufficient power budget left. And there needs to be a call to release
> such an allocation.

The current limits for regulators are generally imposed in hardware as a
safety measure, this also happens for example with USB where there's
regulators in the PHYs.  Whatever is providing the power is very likely
to have reasonable headroom for robustness.

> We are probably not so much interested in what the actual current
> power draw is, assuming there is no wish to over provision?

One of the goals is to protect the system in the case that something
malfunctions and tries to draw more current than can be sustained.  A
system that is overprovisioned might choose to allow excessive draw,
especially transiently to cover bootsrapping issues, though there's
tradeoffs with system protection vs interoperability with poor quality
implementations there.

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmYvwScACgkQJNaLcl1U
h9BE5wf/eGMbGuMBrgTE/BBGw7ZPtzshbhPpItvoGiNej1Aa8AeY6iPc6OJy3g27
Ara8ZgQ0qWxv1hkOrgzlgNEq/BxkG5pGcNIRp68dJWM31xI2YkGAH4FiI0Yo74eD
3fnt5adFdZzVVA/jHguYIzzdXp5AK32YEfZ4mbdaPO+gLM4VakFWiRVOU/P3jQoa
asM2b9FLIFjMKtzlHYefDMUIC28WMbkVcpq9YJUy2Sr4goqJFObKFzIZhe2B7rmA
kGEBGEh3c/vjcYGepZ2ivGD5yInwRK5njcTGgGI8kZ3YnyQOIX63Y0Ep+RaawToJ
D3uv6/3i/nbUBM1TetHgPEjcafc+WQ==
=I9We
-----END PGP SIGNATURE-----

--z0k5BVdQYkZbQzID--