From: Sam Ravnborg <sam@ravnborg.org>
To: Tomohito Esaki <etom@igel.co.jp>
Cc: devicetree@vger.kernel.org,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-doc@vger.kernel.org, David Airlie <airlied@linux.ie>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATH 3/4] dt-bindings: display: Add virtual DRM
Date: Mon, 21 Jun 2021 18:03:08 +0200 [thread overview]
Message-ID: <20210621160308.GD823900@ravnborg.org> (raw)
In-Reply-To: <20210621064403.26663-4-etom@igel.co.jp>
Hi Tomohito
> +
> +description:
> + This document defines device tree properties virtual DRM. The initial
> + position, size and z-position of the plane used in the virtual DRM is
> + specified.
> + The current limitation is that these settings are applied to all crtc.
This comment (I think) refers to the actual implmentation which is
irrelevant for the binding. The implementation may refer to the binding,
but the binding must be implementation agnostic.
> +
> +properties:
> + compatible:
> + const: virt-drm
> +
> +patternProperties:
> + "^plane(@.*)?$":
> + description: Information of the planes used in virtual DRM
> + type: object
> +
> + properties:
> + x:
> + type: int
This syntax looks wrong, I had expected something like:
$ref: "/schemas/types.yaml#/definitions/uint32"
> + description: x-coordinate of the left-top of the plane in pixels
> +
> + y:
> + type: int
> + description: y-coordinate of the left-top of the plane in pixels
> +
> + width:
> + type: int
> + description: width of the plane in pixels
> +
> + height:
> + type: int
> + description: height of the plane in pixels
> +
> + zpos:
> + type: int
> + description: z-position of the plane
> +
> + required:
> + - x
> + - y
> + - width
> + - height
> + - zpos
> +
> +required:
> + - compatible
> + - "^plane(@.*)?$"
If there is no node to match this binding does not take effect.
So I think ^plane... do not need to be specified.
> +
> +examples:
> + - |
> + vdrm@0 {
> + compatible = "virt-drm";
> + plane@0 {
> + x = <200>;
> + y = <100>;
> + width = <800>;
> + height = <600>;
> + zpos = <1>;
> + };
> + };
Do not mix spaces and tabd, be consistent and use 4 spaces as indent in
all the example.
Sam
next prev parent reply other threads:[~2021-06-21 16:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 6:43 [PATH 0/4] [RFC] Support virtual DRM Tomohito Esaki
2021-06-21 6:43 ` Tomohito Esaki
2021-06-21 6:44 ` [PATH 1/4] drm: Add Virtual DRM device driver Tomohito Esaki
2021-06-21 6:44 ` Tomohito Esaki
2021-06-21 13:55 ` kernel test robot
2021-06-21 13:55 ` kernel test robot
2021-06-21 13:55 ` kernel test robot
2021-06-21 15:55 ` Sam Ravnborg
2021-06-22 4:10 ` Esaki Tomohito
2021-06-22 4:10 ` Esaki Tomohito
2021-06-21 6:44 ` [PATH 2/4] rcar-du: Add support virtual DRM device Tomohito Esaki
2021-06-21 6:44 ` Tomohito Esaki
2021-06-21 11:25 ` kernel test robot
2021-06-21 11:25 ` kernel test robot
2021-06-21 11:25 ` kernel test robot
2021-06-21 15:57 ` Sam Ravnborg
2021-06-21 6:44 ` [PATH 3/4] dt-bindings: display: Add virtual DRM Tomohito Esaki
2021-06-21 6:44 ` Tomohito Esaki
2021-06-21 16:03 ` Sam Ravnborg [this message]
2021-06-21 17:40 ` Rob Herring
2021-06-21 17:40 ` Rob Herring
2021-06-22 4:17 ` Esaki Tomohito
2021-06-22 4:17 ` Esaki Tomohito
2021-06-22 16:54 ` Rob Herring
2021-06-22 16:54 ` Rob Herring
2021-06-21 6:44 ` [PATH 4/4] doc-rst: Add virtual DRM documentation Tomohito Esaki
2021-06-21 6:44 ` Tomohito Esaki
2021-06-22 8:04 ` [PATH 0/4] [RFC] Support virtual DRM Simon Ser
2021-06-22 8:04 ` Simon Ser
-- strict thread matches above, loose matches on Subject: below --
2021-06-21 6:27 Tomohito Esaki
2021-06-21 6:27 ` [PATH 3/4] dt-bindings: display: Add " Tomohito Esaki
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=20210621160308.GD823900@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=etom@igel.co.jp \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--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.