From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 4E04F435EEC; Wed, 8 Jul 2026 16:39:39 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783528782; cv=none; b=MFhytex/9CyqEjU7RX7MyNm/tYa0xKMXWFFa1rUi+p39pzUpfn17k6JIBOUDYuVMe7WwhoDdJGv6E0+PMUxZVom5JpHztLgu0sNGImJ5vUL8kRPlPBJFD6yY4/H3Eu6kWXzeBLzL2eefvgHvuOTJl9BIGcnHB1eH5YC2Y9JFEbg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1783528782; c=relaxed/simple; bh=VXPzWa5LujKUUxkyvvHEPmwRqAn44lKYZ+904oWZfNg=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YqAvlhaRTAuRPVqq70y2yPVK3PDrxt4fET1pQkEXT3WFcpKPYwB2tSvjkmLEcHcEqCyDo+LS1b8N3EEP5iNXhvxwWKmFRN3HKkB30c//hCSrqGkn9IOogkIZOuuceb42pZqYe03B0bvis6+7f9ly+Bm6TyClNhIVGKV4oeqnHRY= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=mAKVPYvL; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="mAKVPYvL" Received: by smtp.kernel.org (Postfix) with ESMTPSA id DFF5F1F000E9; Wed, 8 Jul 2026 16:39:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1783528779; bh=0vXeI+uCXnMRTRUaf8HMNBKTFOd8TopxxzIUG1swgmA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=mAKVPYvLfywT4c/A7TNfSBbuW0PmTrerhJVp61IvBtaET8sHc8VIztbtUWBp0UqZx /tz6XVc2uJoqaZHv2oc1kjKDqoeVdSEdTShBIqdsu/34W4tgFke/gOmjTBF3GdsbRy J+oupoeLzOALtt+soh9dr19rB9cFk8RZQi49pW+CqpW9uh5I8YABFIhjk5yOXl9r/z VHFGAO5p3YlYiiwIBuK0zwmxsvrtn8uaeuM8nMWIMvdDsycG7QQcyCUrGVdji/Ola9 ZYfWXCrtrmiFHq46lv+JVjhr78iuQ1O4B0fqMWvX22K5dqJCWoxagqwjTdabI1MPux 1M9rxYeT7hlqQ== Date: Wed, 8 Jul 2026 17:39:34 +0100 From: Conor Dooley To: Gokul Praveen Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, krzk+dt@kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org, neil.armstrong@linaro.org, nm@ti.com, robh@kernel.org, sjakhade@cadence.com, kristo@kernel.org, vigneshr@ti.com, vkoul@kernel.org, yamonkar@cadence.com Subject: Re: [PATCH v5 net-next 1/2] dt-bindings: phy: cadence-torrent: Update property values to support multilink SERDES configuration Message-ID: <20260708-purifier-subside-667f32244c09@spud> References: <20260708083725.66777-1-g-praveen@ti.com> <20260708083725.66777-2-g-praveen@ti.com> Precedence: bulk X-Mailing-List: linux-kernel@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="SevP7+UOVskAfqSk" Content-Disposition: inline In-Reply-To: <20260708083725.66777-2-g-praveen@ti.com> --SevP7+UOVskAfqSk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 08, 2026 at 02:07:24PM +0530, Gokul Praveen wrote: > Update the maxItems value of clocks parameter as 3 clocks > (refclk,pll1_refclk,phy_en_refclk) are supported. >=20 > Update the clock-names parameter to support mutilink SERDES configuration > as the existing enum configuration of the clock-names parameter does not > allow both pll1_refclk and phy_en_refclk to be used at the same time, > hence preventing the support for the configuration (refclk,pll1_refclk, > phy_en_refclk), which is neeed for multilink SERDES usecases. >=20 > For multilink SERDES configurations where the links require different > clock speeds, all 3 clocks(refclk, pll1_refclk and phy_en_refclk) > are needed. >=20 > For example,considering the USXGMII+SGMII multilink SERDES configuration > usecase, having only 1 reference clock(refclk) fails because USXGMII > requires a clock speed of 156.25 Mhz and SGMII protocol requires an > clock speed of 100 Mhz. >=20 > Since one reference clock(refclk) alone cannot cater to the 2 > different clock speed requirements of these protocols, the second > input reference clock(pll1_refclk) along with phy_en_refclk > is also needed. This binding supports 2 devices and the generic compatible. Do all these devices have the new refclk? Thanks, Conor. >=20 > Signed-off-by: Gokul Praveen > --- > Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml | 3 ++- > 1 file changed, 2 insertions(+), 1 deletion(-) >=20 > diff --git a/Documentation/devicetree/bindings/phy/phy-cadence-torrent.ya= ml b/Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml > index 9af39b33646a..ac0f625cd76d 100644 > --- a/Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml > +++ b/Documentation/devicetree/bindings/phy/phy-cadence-torrent.yaml > @@ -34,7 +34,7 @@ properties: > =20 > clocks: > minItems: 1 > - maxItems: 2 > + maxItems: 3 > description: > PHY input reference clocks - refclk (for PLL0) & pll1_refclk (for = PLL1). > pll1_refclk is optional and used for multi-protocol configurations= requiring > @@ -48,6 +48,7 @@ properties: > items: > - const: refclk > - enum: [ pll1_refclk, phy_en_refclk ] > + - const: phy_en_refclk > =20 > reg: > minItems: 1 > --=20 > 2.34.1 >=20 --SevP7+UOVskAfqSk Content-Type: application/pgp-signature; name=signature.asc -----BEGIN PGP SIGNATURE----- iHUEABYKAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCak59RgAKCRB4tDGHoIJi 0jCnAQDwtt/OwP4pRnpx2Cyg3NCRTTNs5l3WIiTgazMbaX9XagD+KZWxE6E1LGe+ AxAPK0PIAm6SzsOvq7pGRtKDUpY01gg= =70nt -----END PGP SIGNATURE----- --SevP7+UOVskAfqSk--