From: sashiko-bot@kernel.org
To: "Damon Ding" <damon.ding@rock-chips.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org, robh@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, neil.armstrong@linaro.org,
olteanv@gmail.com
Subject: Re: [PATCH v4 1/6] dt-bindings: display: rockchip: analogix-dp: Add support for RK3568
Date: Fri, 30 Oct 2026 06:55:36 +0000 [thread overview]
Message-ID: <sashiko-outbox-190620@kernel.org> (raw)
In-Reply-To: <20261030064905.2248999-2-damon.ding@rock-chips.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: display: rockchip: unwieldy per-compatible conditionals
--
commit 53ce09e99c75e142a328f4bf2e7535fad7dadeb9
Author: Damon Ding <damon.ding@rock-chips.com>
dt-bindings: display: rockchip: analogix-dp: Add support for RK3568
This commit documents the rockchip,rk3568-edp compatible in
rockchip,analogix-dp.yaml, making rockchip,grf conditional and adding the
avdd-0v9-supply and avdd-1v8-supply properties for RK3568.
> diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
> index 6548f157fd966..f3e70cc3a1236 100644
> --- a/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
> +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
[ ... ]
> @@ -61,11 +72,25 @@ required:
> - clock-names
> - resets
> - reset-names
> - - rockchip,grf
>
> allOf:
> - $ref: /schemas/display/bridge/analogix,dp.yaml#
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3568-edp
> + then:
> + properties:
> + rockchip,grf: false
> + else:
> + properties:
> + avdd-0v9-supply: false
> + avdd-1v8-supply: false
> + required:
> + - rockchip,grf
> +
> - if:
> properties:
> compatible:
> @@ -100,6 +125,7 @@ allOf:
> compatible:
> contains:
> enum:
> + - rockchip,rk3568-edp
> - rockchip,rk3576-edp
> - rockchip,rk3588-edp
> then:
[Severity: Low]
This isn't a bug, but with the addition of rockchip,rk3568-edp, allOf in
Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
now has four separate per-compatible if-then blocks governing almost all
Rockchip-specific properties (clocks, clock-names, resets, reset-names,
rockchip,grf, avdd-0v9-supply, and avdd-1v8-supply), with
rockchip,rk3568-edp matched in two different blocks.
Given these growing variant differences across SoCs, would it be cleaner
to split this binding into separate schema documents rather than adding
more per-compatible conditionals here?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261030064905.2248999-1-damon.ding@rock-chips.com?part=1
WARNING: multiple messages have this Message-ID (diff)
From: sashiko-bot@kernel.org
To: "Damon Ding" <damon.ding@rock-chips.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-phy@lists.infradead.org, robh@kernel.org,
conor+dt@kernel.org, vkoul@kernel.org, neil.armstrong@linaro.org,
olteanv@gmail.com
Subject: Re: [PATCH v4 1/6] dt-bindings: display: rockchip: analogix-dp: Add support for RK3568
Date: Fri, 30 Oct 2026 06:55:36 +0000 [thread overview]
Message-ID: <sashiko-outbox-190620@kernel.org> (raw)
In-Reply-To: <20261030064905.2248999-2-damon.ding@rock-chips.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: display: rockchip: unwieldy per-compatible conditionals
--
commit 53ce09e99c75e142a328f4bf2e7535fad7dadeb9
Author: Damon Ding <damon.ding@rock-chips.com>
dt-bindings: display: rockchip: analogix-dp: Add support for RK3568
This commit documents the rockchip,rk3568-edp compatible in
rockchip,analogix-dp.yaml, making rockchip,grf conditional and adding the
avdd-0v9-supply and avdd-1v8-supply properties for RK3568.
> diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
> index 6548f157fd966..f3e70cc3a1236 100644
> --- a/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
> +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
[ ... ]
> @@ -61,11 +72,25 @@ required:
> - clock-names
> - resets
> - reset-names
> - - rockchip,grf
>
> allOf:
> - $ref: /schemas/display/bridge/analogix,dp.yaml#
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: rockchip,rk3568-edp
> + then:
> + properties:
> + rockchip,grf: false
> + else:
> + properties:
> + avdd-0v9-supply: false
> + avdd-1v8-supply: false
> + required:
> + - rockchip,grf
> +
> - if:
> properties:
> compatible:
> @@ -100,6 +125,7 @@ allOf:
> compatible:
> contains:
> enum:
> + - rockchip,rk3568-edp
> - rockchip,rk3576-edp
> - rockchip,rk3588-edp
> then:
[Severity: Low]
This isn't a bug, but with the addition of rockchip,rk3568-edp, allOf in
Documentation/devicetree/bindings/display/rockchip/rockchip,analogix-dp.yaml
now has four separate per-compatible if-then blocks governing almost all
Rockchip-specific properties (clocks, clock-names, resets, reset-names,
rockchip,grf, avdd-0v9-supply, and avdd-1v8-supply), with
rockchip,rk3568-edp matched in two different blocks.
Given these growing variant differences across SoCs, would it be cleaner
to split this binding into separate schema documents rather than adding
more per-compatible conditionals here?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261030064905.2248999-1-damon.ding@rock-chips.com?part=1
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2026-10-30 6:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 6:48 [PATCH v4 0/6] Add eDP support for RK3568 Damon Ding
2026-10-30 6:48 ` Damon Ding
2026-10-30 6:48 ` Damon Ding
2026-10-30 6:49 ` [PATCH v4 1/6] dt-bindings: display: rockchip: analogix-dp: Add " Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:55 ` sashiko-bot [this message]
2026-10-30 6:55 ` sashiko-bot
2026-10-30 6:49 ` [PATCH v4 2/6] dt-bindings: phy: Add rockchip,rk3568-edp-phy Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` [PATCH v4 3/6] drm/bridge: analogix_dp: Add support for RK3568 Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` [PATCH v4 4/6] phy: rockchip: Add support for Naneng eDP phy Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 7:07 ` sashiko-bot
2026-10-30 7:07 ` sashiko-bot
2026-10-30 6:49 ` [PATCH v4 5/6] drm/rockchip: analogix_dp: Add support for RK3568 Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` [PATCH v4 6/6] arm64: dts: rockchip: rk356x: Add eDP controller and phy nodes Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 6:49 ` Damon Ding
2026-10-30 7:04 ` sashiko-bot
2026-10-30 7:04 ` 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=sashiko-outbox-190620@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=damon.ding@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--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.