From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 9B58162813; Thu, 21 Dec 2023 15:43:29 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="BvPuYSYB" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 00995C433C8; Thu, 21 Dec 2023 15:43:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1703173409; bh=p268v/Z0J/H5DA9xBR1KA840CSsR1hZCKg5Z9xk2s3c=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=BvPuYSYBl2X/2ntuQY8d5QQk0Ku6zFRvgcG2d7Z79O9T5f1wQKO9o7+gGxgJ6a/a2 mfCYdGFw7CHXl4NAVZpAz3J2YrB8h0NS4C7U2/mjQESTrS4dK37riC8323lwWg1nOb z5etc72DN2g2y8VehSmx21Yd9vc+VbBL20ljCYhb1sHuD6qnBr8qfx33YoVTH91thr wuaGC4M4c3Pgst7X9bupkaLDGvaVG4eZLc3/1+bCDoMe32XubgGgptffMXe3dmMAay N2CgV3x3cyOxo9pnEzoD5Wmv/QIBuUEGZBGlvFNy3EBi8ZWhInb0GC6hbWb0EGLH3p UT/ivN+mvANFw== Date: Thu, 21 Dec 2023 15:43:21 +0000 From: Mark Brown To: =?iso-8859-1?Q?K=F6ry?= Maincent Cc: Oleksij Rempel , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Jonathan Corbet , Luis Chamberlain , Russ Weight , Greg Kroah-Hartman , "Rafael J. Wysocki" , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Thomas Petazzoni , netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, devicetree@vger.kernel.org, Dent Project , Liam Girdwood Subject: Re: [PATCH net-next v2 8/8] net: pse-pd: Add PD692x0 PSE controller driver Message-ID: References: <20231201-feature_poe-v2-0-56d8cac607fa@bootlin.com> <20231201-feature_poe-v2-8-56d8cac607fa@bootlin.com> <20231204225956.GG981228@pengutronix.de> <20231205064527.GJ981228@pengutronix.de> <4b96b8c8-7def-46e5-9c85-d9e925fb9251@sirena.org.uk> <20231205140203.GK981228@pengutronix.de> <88ed0c94-d052-4564-be0c-79a0f502eda8@sirena.org.uk> <20231221163610.47038996@kmaincent-XPS-13-7390> Precedence: bulk X-Mailing-List: linux-doc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ayY3hi9uzG0eQYAg" Content-Disposition: inline In-Reply-To: <20231221163610.47038996@kmaincent-XPS-13-7390> X-Cookie: Results are not typical. --ayY3hi9uzG0eQYAg Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Dec 21, 2023 at 04:36:10PM +0100, K=F6ry Maincent wrote: > Mark Brown wrote: > > OK... I mean, if they're not using the regulator framework I'm not sure > > it has much impact - there are plenty of internal regulators in devices > > already so it wouldn't be *too* unusual other than the fact that AFAICT > > this is somewhat split between devices within the subsystem? Neither of > > the messages was super clear. > PSE Power Interface (which is kind of the RJ45 in PSE world) have similar > functionalities as regulators. We wondered if registering a regulator for > each PSE PI (RJ45 ports) is a good idea. The point is that the PSE contro= ller > driver will be its own regulator consumer. > I can't find any example in Linux with such a case of a driver being a pr= ovider > and a consumer of its own regulator. This idea of a regulator biting its = own > tail seems weird to me. Maybe it is better to implement the PSE functiona= lities > even if they are like the regulator functionalities. Is it at all plausible that a system (perhaps an embedded one) might use something other than PSE? --ayY3hi9uzG0eQYAg Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmWEXRkACgkQJNaLcl1U h9AWAwf+OP5Q11gZjq9GXb7vPW2rJm2BAFFBY2+mv5PDmeN23hAQZJ3hk7m0AYwr 5KBzgRuvGPeJ+pPbYmiwxNi8kXh9i8osTopdSP5p+OAzEIdT5DMqaaKJ0uWJlpYX zS0gp3FM1eH7Td+BrOAvJFlt0OgQLXr8SADS/SwEB16iIg6mHwEdSrDw8ZI66sA/ A7ANAodvCQ0WBYAU5OvDHoNwmzuKyNTHu+Z2Wqq/PLP5qsojZTi6QrbL1hNPqiLE lCvrWI58JCdfRjyM5f3BoQ05HDPdHTrVs1eTPScpZgHjFrwBk/89TJL87tRsBMi5 d/MFhEW24jlwrBiUU12PL9nk41zkqw== =r7wZ -----END PGP SIGNATURE----- --ayY3hi9uzG0eQYAg--