The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Rok Markovic <rok@kanardia.eu>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Sandy Huang <hjc@rock-chips.com>,
	Andy Yan <andy.yan@rock-chips.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
	Alibek Omarov <a1ba.omarov@gmail.com>
Subject: Re: [PATCH v2 2/4] dt-bindings: display: rockchip,lvds: add RK3568
Date: Fri, 7 Aug 2026 17:31:29 -0500	[thread overview]
Message-ID: <20260807223129.GA2151152-robh@kernel.org> (raw)
In-Reply-To: <20260724080824.115260-3-rok@kanardia.eu>

On Fri, Jul 24, 2026 at 10:08:22AM +0200, Rok Markovic wrote:
> The RK3568 LVDS transmitter has no register block of its own: it is
> programmed entirely through the GRF and re-uses the MIPI DSI0 D-PHY
> (rockchip,rk3568-dsi-dphy) in LVDS mode. It therefore takes the same
> shape as px30: phys/phy-names, no reg, and no clock of its own.
> 
> Since the block exposes no MMIO, nothing in the LVDS path is clocked
> from the DSI controller's APB clock; that gate is held off while LVDS
> scans out. It has no analog supplies of its own and no pinctrl either:
> the lanes are dedicated D-PHY pins, not muxable GPIOs.
> 
> Signed-off-by: Rok Markovic <rok@kanardia.eu>
> Assisted-by: Claude:claude-opus-4-8
> ---
> Changes in v2:
>   - RK3568 now takes no clock (clocks/clock-names disabled, as for
>     px30): the block has no register space, so nothing consumes the
>     DSI controller's APB clock.
> 
>  .../display/rockchip/rockchip,lvds.yaml       | 22 +++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/display/rockchip/rockchip,lvds.yaml b/Documentation/devicetree/bindings/display/rockchip/rockchip,lvds.yaml
> index 03b002a..b77d4fa 100644
> --- a/Documentation/devicetree/bindings/display/rockchip/rockchip,lvds.yaml
> +++ b/Documentation/devicetree/bindings/display/rockchip/rockchip,lvds.yaml
> @@ -15,6 +15,7 @@ properties:
>      enum:
>        - rockchip,px30-lvds
>        - rockchip,rk3288-lvds
> +      - rockchip,rk3568-lvds
>  
>    reg:
>      maxItems: 1
> @@ -121,6 +122,27 @@ allOf:
>          - avdd1v8-supply
>          - avdd3v3-supply
>  
> +  - if:
> +      properties:
> +        compatible:
> +          contains:
> +            const: rockchip,rk3568-lvds
> +
> +    then:
> +      properties:
> +        reg: false
> +        clocks: false
> +        clock-names: false
> +        avdd1v0-supply: false
> +        avdd1v8-supply: false
> +        avdd3v3-supply: false
> +        pinctrl-names: false
> +        pinctrl-0: false

Other than pinctrl props, this is the same as the existing px30 if/then 
schema, so just add the compatible there. pinctrl properties are 
implicitly always allowed.

Really, I think this and px30 and this should be its own schema. There's 
not a lot of common parts.

Finally, if the only interface is the GRF, then this should be a child 
of the GRF node.

Rob

  reply	other threads:[~2026-08-07 22:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  8:08 [PATCH v2 0/4] drm/rockchip: add RK3568 LVDS support Rok Markovic
2026-07-24  8:08 ` [PATCH v2 1/4] drm/rockchip: lvds: propagate bus_flags to the CRTC state Rok Markovic
2026-07-24  8:08 ` [PATCH v2 2/4] dt-bindings: display: rockchip,lvds: add RK3568 Rok Markovic
2026-08-07 22:31   ` Rob Herring [this message]
2026-07-24  8:08 ` [PATCH v2 3/4] drm/rockchip: lvds: add RK3568 support Rok Markovic
2026-07-27  7:10   ` Chaoyi Chen
2026-07-24  8:08 ` [PATCH v2 4/4] arm64: dts: rockchip: rk356x: add LVDS node Rok Markovic

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=20260807223129.GA2151152-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=a1ba.omarov@gmail.com \
    --cc=airlied@gmail.com \
    --cc=andy.yan@rock-chips.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=heiko@sntech.de \
    --cc=hjc@rock-chips.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=rok@kanardia.eu \
    --cc=simona@ffwll.ch \
    --cc=tzimmermann@suse.de \
    /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