From: sashiko-bot@kernel.org
To: "Jason Yang" <jason98166@gmail.com>
Cc: neil.armstrong@linaro.org, devicetree@vger.kernel.org,
olteanv@gmail.com, robh@kernel.org,
linux-phy@lists.infradead.org, conor+dt@kernel.org,
vkoul@kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
Date: Sun, 26 Jul 2026 15:02:50 +0000 [thread overview]
Message-ID: <20260726150250.8157C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260726-dcphy-rx-v1-v2-1-cf9cc34a412a@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The dt-binding allows `#phy-cells = 2` to represent PHY direction, but the corresponding driver `phy-rockchip-samsung-dcphy.c` was not updated to support this.
--
--- Patch [1]: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys ---
commit 421d266fa3318c44780c09224a034b0edeca9db3
Author: Jason Yang <jason98166@gmail.com>
Subject: dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
This commit updates the Rockchip RK3588 MIPI D-/C-PHY device tree binding
to support per-direction configuration. It changes the #phy-cells property
to allow either 1 or 2 cells, where the optional second cell specifies the
PHY direction (TX or RX).
> diff --git a/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml b/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> index c8ff5ba22a86b..68a43db9c6690 100644
> --- a/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> +++ b/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> @@ -20,12 +20,22 @@ properties:
> maxItems: 1
>
> "#phy-cells":
> - const: 1
> + enum: [1, 2]
[Severity: Medium]
Will this new 2-cell configuration work with the current PHY driver?
Looking at samsung_mipi_dcphy_xlate() in
drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c, the driver explicitly
rejects anything other than 1 cell:
if (args->args_count != 1) {
dev_err(dev, "invalid number of arguments\n");
return ERR_PTR(-EINVAL);
}
If a device tree is updated to use the newly allowed 2-cell configuration
to specify TX/RX direction, won't phy_get() fail and return -EINVAL? Should
the driver be updated alongside the binding so consumers can successfully
acquire the PHY?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260726-dcphy-rx-v1-v2-0-cf9cc34a412a@gmail.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Jason Yang" <jason98166@gmail.com>
Cc: neil.armstrong@linaro.org, devicetree@vger.kernel.org,
olteanv@gmail.com, robh@kernel.org,
linux-phy@lists.infradead.org, conor+dt@kernel.org,
vkoul@kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
Date: Sun, 26 Jul 2026 15:02:50 +0000 [thread overview]
Message-ID: <20260726150250.8157C1F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260726-dcphy-rx-v1-v2-1-cf9cc34a412a@gmail.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The dt-binding allows `#phy-cells = 2` to represent PHY direction, but the corresponding driver `phy-rockchip-samsung-dcphy.c` was not updated to support this.
--
--- Patch [1]: [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys ---
commit 421d266fa3318c44780c09224a034b0edeca9db3
Author: Jason Yang <jason98166@gmail.com>
Subject: dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys
This commit updates the Rockchip RK3588 MIPI D-/C-PHY device tree binding
to support per-direction configuration. It changes the #phy-cells property
to allow either 1 or 2 cells, where the optional second cell specifies the
PHY direction (TX or RX).
> diff --git a/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml b/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> index c8ff5ba22a86b..68a43db9c6690 100644
> --- a/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> +++ b/Documentation/devicetree/bindings/phy/rockchip,rk3588-mipi-dcphy.yaml
> @@ -20,12 +20,22 @@ properties:
> maxItems: 1
>
> "#phy-cells":
> - const: 1
> + enum: [1, 2]
[Severity: Medium]
Will this new 2-cell configuration work with the current PHY driver?
Looking at samsung_mipi_dcphy_xlate() in
drivers/phy/rockchip/phy-rockchip-samsung-dcphy.c, the driver explicitly
rejects anything other than 1 cell:
if (args->args_count != 1) {
dev_err(dev, "invalid number of arguments\n");
return ERR_PTR(-EINVAL);
}
If a device tree is updated to use the newly allowed 2-cell configuration
to specify TX/RX direction, won't phy_get() fail and return -EINVAL? Should
the driver be updated alongside the binding so consumers can successfully
acquire the PHY?
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260726-dcphy-rx-v1-v2-0-cf9cc34a412a@gmail.com?part=1
next prev parent reply other threads:[~2026-07-26 15:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 14:55 [PATCH v2 0/4] phy: rockchip-samsung-dcphy: support the D-PHY receiver direction Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` [PATCH v2 1/4] dt-bindings: phy: rockchip,rk3588-mipi-dcphy: support per-direction phys Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 15:02 ` sashiko-bot [this message]
2026-07-26 15:02 ` sashiko-bot
2026-07-26 14:55 ` [PATCH v2 2/4] phy: rockchip-samsung-dcphy: factor MIPI D-PHY power on/off into helpers Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` [PATCH v2 3/4] phy: rockchip-samsung-dcphy: model TX and RX as separate PHYs Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` [PATCH v2 4/4] phy: rockchip-samsung-dcphy: add MIPI D-PHY receiver support Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 14:55 ` Jason Yang via B4 Relay
2026-07-26 15:07 ` sashiko-bot
2026-07-26 15:07 ` sashiko-bot
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=20260726150250.8157C1F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jason98166@gmail.com \
--cc=linux-phy@lists.infradead.org \
--cc=neil.armstrong@linaro.org \
--cc=olteanv@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.