devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Vinod Koul <vkoul@kernel.org>,
	Kishon Vijay Abraham I <kishon@kernel.org>,
	linux-rockchip@lists.infradead.org,
	linux-phy@lists.infradead.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Frank Wang <frank.wang@rock-chips.com>,
	Kever Yang <kever.yang@rock-chips.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	kernel@collabora.com
Subject: Re: [PATCH v2 03/12] dt-bindings: phy: add rockchip usbdp combo phy document
Date: Wed, 14 Feb 2024 18:25:11 +0000	[thread overview]
Message-ID: <20240214-duckbill-nimbly-4ca5ac491ec7@spud> (raw)
In-Reply-To: <20240213163609.44930-4-sebastian.reichel@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 1160 bytes --]

On Tue, Feb 13, 2024 at 05:32:37PM +0100, Sebastian Reichel wrote:
> +  rockchip,dp-lane-mux:
> +    $ref: /schemas/types.yaml#/definitions/uint32-array
> +    minItems: 2
> +    maxItems: 4
> +    description:
> +      An array of physical Type-C lanes indexes. Position of an entry
> +      determines the DisplayPort (DP) lane index, while the value of an entry
> +      indicates physical Type-C lane. The supported DP lanes number are 2 or 4.
> +      e.g. for 2 lanes DP lanes map, we could have "rockchip,dp-lane-mux = <2,
> +      3>;", assuming DP lane0 on Type-C phy lane2, DP lane1 on Type-C phy
> +      lane3. For 4 lanes DP lanes map, we could have "rockchip,dp-lane-mux =
> +      <0, 1, 2, 3>;", assuming DP lane0 on Type-C phy lane0, DP lane1 on Type-C
> +      phy lane1, DP lane2 on Type-C phy lane2, DP lane3 on Type-C phy lane3.

>        If
> +      DP lane map by DisplayPort Alt mode, this property is not need.

You missed one of the nits I pointed out on the previous version:
"If DP lanes are mapped by" "not needed."

Otherwise, I think this looks okay to me..
Reviewed-by: Conor Dooley <conor.dooley@microchip.com>

Cheers,
Conor.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-02-14 18:25 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 16:32 [PATCH v2 00/12] RK3588 USBDP support Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 01/12] dt-bindings: soc: rockchip: add clock to RK3588 VO grf Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 02/12] dt-bindings: soc: rockchip: add rk3588 USB3 syscon Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 03/12] dt-bindings: phy: add rockchip usbdp combo phy document Sebastian Reichel
2024-02-14 18:25   ` Conor Dooley [this message]
2024-02-15 12:31   ` Rob Herring
2024-02-13 16:32 ` [PATCH v2 04/12] phy: rockchip: add usbdp combo phy driver Sebastian Reichel
2024-02-16  6:47   ` Vinod Koul
2024-02-13 16:32 ` [PATCH v2 05/12] arm64: defconfig: enable Rockchip Samsung USBDP PHY Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 06/12] arm64: dts: rockchip: Fix usb2phy nodename for rk3588 Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 07/12] arm64: dts: rockchip: reorder usb2phy properties " Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 08/12] arm64: dts: rockchip: add USBDP phys on rk3588 Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 09/12] arm64: dts: rockchip: add USB3 DRD controllers " Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 10/12] arm64: dts: rockchip: add USB3 to rk3588-evb1 Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 11/12] arm64: dts: rockchip: add upper USB3 port to rock-5a Sebastian Reichel
2024-02-13 16:32 ` [PATCH v2 12/12] arm64: dts: rockchip: add lower USB3 port to rock-5b Sebastian Reichel
2024-02-13 19:16 ` (subset) [PATCH v2 00/12] RK3588 USBDP support Heiko Stuebner

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=20240214-duckbill-nimbly-4ca5ac491ec7@spud \
    --to=conor@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frank.wang@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=kever.yang@rock-chips.com \
    --cc=kishon@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --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).