Received-SPF: pass (google.com: domain of linux-kernel+bounces-88668-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Fri, 1 Mar 2024 17:10:05 +0100
From: =?UTF-8?B?S8O2cnk=?= Maincent <kory.maincent@bootlin.com>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>, Eric Dumazet
 <edumazet@google.com>, Jakub Kicinski <kuba@kernel.org>, Paolo Abeni
 <pabeni@redhat.com>, Jonathan Corbet <corbet@lwn.net>, Luis Chamberlain
 <mcgrof@kernel.org>, Russ Weight <russ.weight@linux.dev>, Greg
 Kroah-Hartman <gregkh@linuxfoundation.org>, "Rafael J. Wysocki"
 <rafael@kernel.org>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski
 <krzysztof.kozlowski+dt@linaro.org>, Conor Dooley <conor+dt@kernel.org>,
 Mark Brown <broonie@kernel.org>, Frank Rowand <frowand.list@gmail.com>,
 Andrew Lunn <andrew@lunn.ch>, Heiner Kallweit <hkallweit1@gmail.com>,
 Russell King <linux@armlinux.org.uk>, Thomas Petazzoni
 <thomas.petazzoni@bootlin.com>, netdev@vger.kernel.org,
 linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
 devicetree@vger.kernel.org, Dent Project <dentproject@linuxfoundation.org>
Subject: Re: [PATCH net-next v5 10/17] net: pse-pd: Add support for PSE PIs
Message-ID: <20240301171005.43188d02@kmaincent-XPS-13-7390>
In-Reply-To: <ZeHlB8DLEqWxBRYH@pengutronix.de>
References: <20240227-feature_poe-v5-0-28f0aa48246d@bootlin.com>
	<20240227-feature_poe-v5-10-28f0aa48246d@bootlin.com>
	<ZeHlB8DLEqWxBRYH@pengutronix.de>
Organization: bootlin
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hello Oleskij,

Thanks you for the review.

On Fri, 1 Mar 2024 15:24:07 +0100
Oleksij Rempel <o.rempel@pengutronix.de> wrote:

> > -static int of_pse_simple_xlate(struct pse_controller_dev *pcdev,
> > -			       const struct of_phandle_args *pse_spec)
> > +static int of_load_pse_pis(struct pse_controller_dev *pcdev)
> >  {
> > -	if (pse_spec->args[0] >=3D pcdev->nr_lines)
> > -		return -EINVAL;
> > +	struct device_node *np =3D pcdev->dev->of_node;
> > +	struct device_node *node, *pis;
> > +	int ret, i;
> > =20
> > -	return pse_spec->args[0];
> > +	if (!np)
> > +		return -ENODEV;
> > +
> > +	pcdev->pi =3D kcalloc(pcdev->nr_lines, sizeof(*pcdev->pi),
> > GFP_KERNEL);
> > +	if (!pcdev->pi)
> > +		return -ENOMEM;
> > +
> > +	pis =3D of_get_child_by_name(np, "pse-pis");
> > +	if (!pis) { =20
>=20
> Do we need to allocate pcdev->pi if there are no pse-pis?

In fact it is not needed in this patch but in the patch 13 which use regula=
tor
framework, as the regulator is described on each pi structure.

I will update them accordingly.

> > +		/* Legacy OF description of PSE PIs */
> > +		pcdev->of_legacy =3D true; =20
>=20
> It is not "legacy" :) PoDL do not providing definition of PSE PI since th=
ere
> is only one pair. May be: single_pair, no_pse_pi or any other idea.

You right it is not needed for PoDL. Maybe no_pse_pi is better according to=
 the
following thoughts.

Just wondering, how a pse controller that support PoE and PoDL simultaneous=
ly
would be exposed in the binding. In that case I suppose all the PIs (PoE and
PoDL) need to use the pse-pi subnode. Then the "alternative pinout" and
"polarity" parameter would not be requested for PoDL PIs.

> > +			dev_err(pcdev->dev, "wrong id of pse pi: %u\n",
> > +				id);
> > +			ret =3D -EINVAL;
> > +			goto out;
> > +		}
> > +
> > +		ret =3D of_property_count_strings(node, "pairset-names");
> > +		if (ret <=3D 0) =20
>=20
> if (ret < 0)
>    error: can't get "pairset-names" property: %pe
> if (ret < 1 || ret > 2)
>    error: wrong number of pairset-names. Should be 1 or 2, got %i

Need to modify this to be able to have PoDL PIs without pairset description.

Regards,
--=20
K=C3=B6ry Maincent, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com