All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: tomm.merciai@gmail.com, prabhakar.mahadev-lad.rj@bp.renesas.com,
	linux-renesas-soc@vger.kernel.org, biju.das.jz@bp.renesas.com,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	Thomas Zimmermann <tzimmermann@suse.de>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 02/10] dt-bindings: display: Document Renesas RZ/G3E display subsystem
Date: Thu, 12 Nov 2026 11:32:16 +0100	[thread overview]
Message-ID: <avWVsEFmoDWgesqZ@tom-desktop> (raw)
In-Reply-To: <20261104-lurking-griffin-of-tornado-ca7ac8@quoll>

Hi Krzysztof,
Thanks for your review.

On Wed, Nov 04, 2026 at 11:19:47AM +0100, Krzysztof Kozlowski wrote:
> On Fri, Oct 23, 2026 at 06:47:35PM +0200, Tommaso Merciai wrote:
> > The Renesas RZ/G3E (R9A09G047) SoC has two LCD Controllers, LCDC0 and
> > LCDC1, each containing a Display Unit (DU). The two DUs are separate
> > instances of the same IP, with their own registers, interrupt, clocks,
> > reset and VSP, and are therefore described by two device tree nodes.
> > 
> > The DSI encoder and channel 1 of the LVDS encoder can be fed by either
> > DU, the source being selected at runtime. Driving those outputs from
> > either DU requires handling both DUs as a single display subsystem.
> > 
> > Document the renesas,r9a09g047-display-subsystem node that groups the
> > two Display Unit instances.
> > 
> > Signed-off-by: Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
> > ---
> > v8->v9:
> >  - New patch.
> > 
> >  .../renesas,r9a09g047-display-subsystem.yaml  | 44 +++++++++++++++++++
> >  MAINTAINERS                                   |  1 +
> >  2 files changed, 45 insertions(+)
> >  create mode 100644 Documentation/devicetree/bindings/display/renesas,r9a09g047-display-subsystem.yaml
> > 
> > diff --git a/Documentation/devicetree/bindings/display/renesas,r9a09g047-display-subsystem.yaml b/Documentation/devicetree/bindings/display/renesas,r9a09g047-display-subsystem.yaml
> > new file mode 100644
> > index 000000000000..e23cc53a1fea
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/display/renesas,r9a09g047-display-subsystem.yaml
> > @@ -0,0 +1,44 @@
> > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> > +%YAML 1.2
> > +---
> > +$id: http://devicetree.org/schemas/display/renesas,r9a09g047-display-subsystem.yaml#
> > +$schema: http://devicetree.org/meta-schemas/core.yaml#
> > +
> > +title: Renesas RZ/G3E Display Subsystem
> > +
> > +maintainers:
> > +  - Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>
> > +
> > +description:
> > +  The Renesas RZ/G3E display subsystem is a virtual device needed to list the
> 
> We do not take bindings for virtual devices, because you do not need
> them. Instantiate your driver from existing bindings, instead of
> creating fake device just for Linux drivers.

Thanks for sharing.

I will drop this patch into the next version, also I will
instantiate the driver from existing bindings like you suggested.

Kind regards,
Tommaso

> 
> > +  Display Unit instances that comprise the graphics subsystem.
> > +
> > +properties:
> > +  compatible:
> > +    const: renesas,r9a09g047-display-subsystem
> > +
> > +  ports:
> > +    $ref: /schemas/types.yaml#/definitions/phandle-array
> 
> Properties have only one type and ports is already defined as object for
> graph.
> 
> Why isn't this a graph?
> 
> Best regards,
> Krzysztof
> 

  reply	other threads:[~2026-11-12 10:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-23 16:47 [PATCH v9 00/10] drm: renesas: rz-du: Add RZ/G3E support Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 01/10] dt-bindings: display: renesas,rzg2l-du: Add support for RZ/G3E SoC Tommaso Merciai
2026-10-23 16:47   ` [PATCH v9 01/10] dt-bindings: display: renesas, rzg2l-du: " Tommaso Merciai
2026-11-04 10:16   ` [PATCH v9 01/10] dt-bindings: display: renesas,rzg2l-du: " Krzysztof Kozlowski
2026-10-23 16:47 ` [PATCH v9 02/10] dt-bindings: display: Document Renesas RZ/G3E display subsystem Tommaso Merciai
2026-11-04 10:19   ` Krzysztof Kozlowski
2026-11-12 10:32     ` Tommaso Merciai [this message]
2026-10-23 16:47 ` [PATCH v9 03/10] drm: renesas: rz-du: vsp: Keep the planes in the VSP Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 04/10] drm: renesas: rz-du: Reference the DRM device by pointer Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 05/10] drm: renesas: rz-du: Count all registered encoders for the possible clones Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 06/10] drm: renesas: rz-du: Split the mode setting initialization Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 07/10] drm: renesas: rz-du: Make the CRTC index relative to the DRM device Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 08/10] drm: renesas: rz-du: Share the encoder of an output driven by several DUs Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 09/10] drm: renesas: rz-du: Add RZ/G3E (R9A09G047) DU support Tommaso Merciai
2026-10-23 16:47 ` [PATCH v9 10/10] arm64: dts: renesas: r9a09g047: Add DU{0,1} and display subsystem nodes Tommaso Merciai
2026-10-23 16:47   ` [PATCH v9 10/10] arm64: dts: renesas: r9a09g047: Add DU{0, 1} " Tommaso Merciai

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=avWVsEFmoDWgesqZ@tom-desktop \
    --to=tommaso.merciai.xr@bp.renesas.com \
    --cc=airlied@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=magnus.damm@gmail.com \
    --cc=mripard@kernel.org \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --cc=robh@kernel.org \
    --cc=simona@ffwll.ch \
    --cc=tomm.merciai@gmail.com \
    --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 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.