Received-SPF: pass (google.com: domain of linux-kernel+bounces-162636-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:58:22 +0900
From: Mark Brown <broonie@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
	Kory Maincent <kory.maincent@bootlin.com>,
	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_Dnr9ye0IGoVMT@finisterre.sirena.org.uk>
References: <20240426124253.56fd0933@kmaincent-XPS-13-7390>
 <57a79abd-722c-4907-b0e7-2396392ae675@lunn.ch>
 <20240429145203.219bee06@kmaincent-XPS-13-7390>
 <Zi-vhKx-WlYPQe3c@pengutronix.de>
 <5063429d-5dca-4538-b240-50c35cbf5e93@lunn.ch>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="bo8r1wdIHpgK6ehz"
Content-Disposition: inline
In-Reply-To: <5063429d-5dca-4538-b240-50c35cbf5e93@lunn.ch>


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

On Mon, Apr 29, 2024 at 04:57:35PM +0200, Andrew Lunn wrote:

> I was not expecting over-provisioning to happen. So prioritisation
> does not make much sense. You either have the power budget, or you
> don't. The SFP gets to use a higher power class if there is budget, or
> it is kept at a lower power class if there is no budget. I _guess_ you
> could give it a high power class, let it establish link, monitor its
> actual power consumption, and then decide to drop it to a lower class
> if the actual consumption indicates it could work at a lower
> class. But the danger is, you are going to loose link.

I suspect these devices will be like most other modern systems and
typically not consume anything like their peak current most of the time,
for networking hardware I'd imagine this will only be when the link is
saturated and could depend on factors like how long the physical links
are.  If it's anything like other similar hardware you may also be
making power requests with a very low resolution specification of the
consumption so have conservative allocation end up rejecting systems
that should work.

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

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmYvw50ACgkQJNaLcl1U
h9DjNAf+NMX+1h+nLe7YsdoVEifR8tW/hw3s5gl7CudpxtOjlkqGSUJhP3iVHc9r
7IhxAGGw6ENDf/uChIOGv+sE+Ev8TO96q9Jz6eiUV9SYisWkfU/8csDGrlOjRqVf
6g7f0JY2IsvtMqBgef1ok2ov899wACM3EQS/lCyVjsBNSYzFIB/JwolzH8ynPDz+
7busVF7vf/+6QU7caq7zMHEeVHB+KZcCgpxlOk+wh7Hlqqfaxeg6qhYDE8mpDG0/
9PBZz2F+gHSx9+tDCltfB6dzUpbzE8l6K/Rqexgto2mAKy0nF17iSPWCd+++8dOD
lfwBp9OMRqV6UMIgxHqArbktai0c9A==
=oodJ
-----END PGP SIGNATURE-----

--bo8r1wdIHpgK6ehz--