From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 59767C10DC1 for ; Fri, 1 Dec 2023 16:03:58 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:Content-Type: List-Subscribe:List-Help:List-Post:List-Archive:List-Unsubscribe:List-Id: In-Reply-To:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date: Reply-To:Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date :Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=zbUCCwRktD+ogwcZ7L9YZCQWXEzcaNtgjVjoDxwlyUc=; b=RAAaC/dRZAdbiZ5Jt/VfOXhjaM 0EPO7a+rsPJy7YQfaekke7IXnudSU+Xsn8j56XDzCZalQCLcXSl8wqXUqohjZn9u/JfiWkpO6PFmW ztFvsCGq79IBov8E8lqfsdxyUkkBDHzGlY3QoUKToUDYrpihtMopby0McDelNEaHLqLmT+qK8OmcA qhrVkxe4pTK01tfbkc9cZO+GJCW54sPSTig0AxlKxXQUIwNPQKPjhbhDIEbTi7EiOGHc2f4klls/k 0KtPkytqLO7xS5WaAg6EjxYNetcWPm13JRSywki9EdY10K+IkKyf2aJQmO6xtGdrkOObj+lN10TLO Q/gcphGA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.96 #2 (Red Hat Linux)) id 1r95zi-00E6pP-0I; Fri, 01 Dec 2023 16:03:58 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.96 #2 (Red Hat Linux)) id 1r95zf-00E6ox-2v for linux-phy@lists.infradead.org; Fri, 01 Dec 2023 16:03:57 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by dfw.source.kernel.org (Postfix) with ESMTP id 63B5C621C4; Fri, 1 Dec 2023 16:03:55 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 02BDEC433C9; Fri, 1 Dec 2023 16:03:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1701446635; bh=9lz4V6T3s7FtzNYEF3vq/lL88rTOR/qPlr59bt0P74A=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=XNhq00bMc4W3OYvg+KnG1p0EHAme+QA1msyZ4YsLOg8LV/yL2bfZ/dJeyFKIvrPFP nBp6pDpqs4AGHBt47903+iJKJUPnZbOVewn0LJF0AwDKoiZZnvLm6a412q8ZdujTaw SVD0F6mV+MHbKNJwVA+JFl5CsiHNZ1f6fKAmzP8gf7JYwBHtgrCFWgyCh7Ch2JDP0l X5tTTS6e7C19CYeERPpT+76ltSJZPVdeanfpwBeWC1iwAeA4LeR+kwGWbjlhs95Czy 8+5zY+O2ZRTrzpwBvzIEdybZ8vERgq2LijNBfNs2vyGEs8F6Jknv5IY9BZdNKP5pWZ rao/idOUiPS/g== Date: Fri, 1 Dec 2023 16:03:50 +0000 From: Conor Dooley To: Tzuyi Chang Cc: Vinod Koul , Kishon Vijay Abraham I , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Stanley Chang Subject: Re: [PATCH 1/2] dt-bindings: phy: realtek: Add Realtek DHC RTD SoC PCIe PHY Message-ID: <20231201-umbilical-unending-c8fa05cb42d2@spud> References: <20231201105207.11786-1-tychang@realtek.com> <20231201105207.11786-2-tychang@realtek.com> MIME-Version: 1.0 In-Reply-To: <20231201105207.11786-2-tychang@realtek.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20231201_080356_032566_E856DB88 X-CRM114-Status: GOOD ( 20.71 ) X-BeenThere: linux-phy@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Linux Phy Mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6241428819176458634==" Sender: "linux-phy" Errors-To: linux-phy-bounces+linux-phy=archiver.kernel.org@lists.infradead.org --===============6241428819176458634== Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="plkfvTK++KeNoCJp" Content-Disposition: inline --plkfvTK++KeNoCJp Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Dec 01, 2023 at 06:52:06PM +0800, Tzuyi Chang wrote: > Add the device tree bindings for the Realtek DHC(Digital Home Center) > RTD SoCs PCIe PHY. >=20 > Signed-off-by: Tzuyi Chang > --- > .../bindings/phy/realtek,rtd-pcie-phy.yaml | 61 +++++++++++++++++++ > 1 file changed, 61 insertions(+) > create mode 100644 Documentation/devicetree/bindings/phy/realtek,rtd-pci= e-phy.yaml >=20 > diff --git a/Documentation/devicetree/bindings/phy/realtek,rtd-pcie-phy.y= aml b/Documentation/devicetree/bindings/phy/realtek,rtd-pcie-phy.yaml > new file mode 100644 > index 000000000000..44ff23f698e6 > --- /dev/null > +++ b/Documentation/devicetree/bindings/phy/realtek,rtd-pcie-phy.yaml > @@ -0,0 +1,61 @@ > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) > +# Copyright 2023 Realtek Semiconductor Corporation > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/phy/realtek,rtd-pcie-phy.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Realtek DHC PCIe PHY > + > +maintainers: > + - Tzuyi Chang > + > +description: > + Realtek PCIe PHY supports the DHC(Digital Home Center) RTD series SoCs. > + The PCIe PHY driver is designed to support physical layer functionality > + of the PCIe controller. > + > +properties: > + compatible: > + enum: > + - realtek,rtd1319-pcie0-phy > + - realtek,rtd1319-pcie1-phy > + - realtek,rtd1319-pcie2-phy > + - realtek,rtd1619b-pcie1-phy > + - realtek,rtd1619b-pcie2-phy Please explain why different PHYs on the same SoC need different compatibles. > + - realtek,rtd1319d-pcie1-phy > + - realtek,rtd1315e-pcie1-phy And why bother with the 1 here given there is no 0 or 2? This looks suspiciously like abuse of the compatible - especially since most of the ops are the same despite the differing compatibles. The case where that does not apply, it looks like the issue is down to the portion of the nvmem cell corresponding to the PHY, which has nothing to do with the programming model of the PHY itself IMO. Cheers, Conor. > + > + "#phy-cells": > + const: 0 > + > + nvmem-cells: > + maxItems: 1 > + description: > + Phandle to nvmem cell that contains 'Tx swing trim' > + tuning parameter value for PCIe phy. > + > + nvmem-cell-names: > + items: > + - const: tx_swing_trim > + > + realtek,pcie-syscon: > + $ref: /schemas/types.yaml#/definitions/phandle > + description: phandle of syscon used to control PCIe MDIO register. > + > +required: > + - compatible > + - realtek,pcie-syscon > + - "#phy-cells" > + > +additionalProperties: false > + > +examples: > + - | > + pcie1_phy { > + compatible =3D "realtek,rtd1319d-pcie1-phy"; > + realtek,pcie-syscon =3D <&pcie1>; > + #phy-cells =3D <0>; > + nvmem-cells =3D <&otp_pcie_tx_swing_trim>; > + nvmem-cell-names =3D "tx_swing_trim"; > + }; > --=20 > 2.43.0 > --plkfvTK++KeNoCJp Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZWoD5gAKCRB4tDGHoIJi 0kopAP969dS+RHyZaMFpNcKy3CvurjimEZqsYofY/GYH97aSxAEAjCob1GhCewzI nJVKasHS5PXypGlEsGDWIUIAFn+TKwk= =ndUt -----END PGP SIGNATURE----- --plkfvTK++KeNoCJp-- --===============6241428819176458634== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline -- linux-phy mailing list linux-phy@lists.infradead.org https://lists.infradead.org/mailman/listinfo/linux-phy --===============6241428819176458634==--