From: "Heiko Stübner" <heiko@sntech.de>
To: vkoul@kernel.org, Andy Yan <andyshrk@163.com>
Cc: cristian.ciocaltea@collabora.com, kishon@kernel.org,
krzk+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-phy@lists.infradead.org,
linux-rockchip@lists.infradead.org,
Andy Yan <andy.yan@rock-chips.com>
Subject: Re: [PATCH v3] dt-bindings: phy: Add rk3576 hdptx phy
Date: Sun, 09 Feb 2025 21:13:15 +0100 [thread overview]
Message-ID: <8470934.EvYhyI6sBW@diego> (raw)
In-Reply-To: <20241231092721.252405-1-andyshrk@163.com>
Vinod,
Am Dienstag, 31. Dezember 2024, 10:27:11 MEZ schrieb Andy Yan:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> Add compatible for the HDPTX PHY on rk3576, which is compatible with
> rk3588, but without rst_phy/rst_ropll/rst_lcpll.
>
> In fact, these three reset lines are also optional on the rk3588,
> they just used for debug, then they were removed on the rk3576 IC
> design.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
With the binding more in the driver-realm, I guess this should go through
the phy tree?
Thanks a lot
Heiko
> ---
>
> Changes in v3:
> - Split from:
> https://lore.kernel.org/linux-rockchip/3330586.aeNJFYEL58@diego/T/#m02151cd8591d7fe92cf30ab69701ed57c1944c06
>
> Changes in v2:
> - Wrap commit message according to Linux coding style
> - Make "rockchip,rk3588-hdptx-phy" const for "rockchip,rk3576-hdptx-phy"
> - Make declare phy/ropll/lcpll reset line are not exit on rk3576
>
> .../phy/rockchip,rk3588-hdptx-phy.yaml | 62 +++++++++++++------
> 1 file changed, 44 insertions(+), 18 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/phy/rockchip,rk3588-hdptx-phy.yaml b/Documentation/devicetree/bindings/phy/rockchip,rk3588-hdptx-phy.yaml
> index 84fe59dbcf48..7a307f45cdec 100644
> --- a/Documentation/devicetree/bindings/phy/rockchip,rk3588-hdptx-phy.yaml
> +++ b/Documentation/devicetree/bindings/phy/rockchip,rk3588-hdptx-phy.yaml
> @@ -11,8 +11,13 @@ maintainers:
>
> properties:
> compatible:
> - enum:
> - - rockchip,rk3588-hdptx-phy
> + oneOf:
> + - enum:
> + - rockchip,rk3588-hdptx-phy
> + - items:
> + - enum:
> + - rockchip,rk3576-hdptx-phy
> + - const: rockchip,rk3588-hdptx-phy
>
> reg:
> maxItems: 1
> @@ -34,24 +39,12 @@ properties:
> const: 0
>
> resets:
> - items:
> - - description: PHY reset line
> - - description: APB reset line
> - - description: INIT reset line
> - - description: CMN reset line
> - - description: LANE reset line
> - - description: ROPLL reset line
> - - description: LCPLL reset line
> + minItems: 4
> + maxItems: 7
>
> reset-names:
> - items:
> - - const: phy
> - - const: apb
> - - const: init
> - - const: cmn
> - - const: lane
> - - const: ropll
> - - const: lcpll
> + minItems: 4
> + maxItems: 7
>
> rockchip,grf:
> $ref: /schemas/types.yaml#/definitions/phandle
> @@ -67,6 +60,39 @@ required:
> - reset-names
> - rockchip,grf
>
> +allOf:
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - rockchip,rk3576-hdptx-phy
> + then:
> + properties:
> + resets:
> + minItems: 4
> + maxItems: 4
> + reset-names:
> + items:
> + - const: apb
> + - const: init
> + - const: cmn
> + - const: lane
> + else:
> + properties:
> + resets:
> + minItems: 7
> + maxItems: 7
> + reset-names:
> + items:
> + - const: phy
> + - const: apb
> + - const: init
> + - const: cmn
> + - const: lane
> + - const: ropll
> + - const: lcpll
> +
> additionalProperties: false
>
> examples:
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-02-09 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-31 9:27 [PATCH v3] dt-bindings: phy: Add rk3576 hdptx phy Andy Yan
2025-01-03 19:05 ` Rob Herring (Arm)
2025-01-04 22:26 ` Heiko Stuebner
2025-02-09 20:13 ` Heiko Stübner [this message]
2025-02-10 17:21 ` (subset) " Vinod Koul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8470934.EvYhyI6sBW@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=vkoul@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).