From: Rob Herring <robh@kernel.org>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: devicetree@vger.kernel.org, krzysztof.kozlowski+dt@linaro.org,
airlied@linux.ie, Chris Morgan <macromorgan@hotmail.com>,
dri-devel@lists.freedesktop.org, thierry.reding@gmail.com,
sam@ravnborg.org
Subject: Re: [PATCH V2 2/3] dt-bindings: display: panel: Add NewVision NV3051D bindings
Date: Sat, 24 Sep 2022 12:07:44 -0500 [thread overview]
Message-ID: <20220924170744.GA961091-robh@kernel.org> (raw)
In-Reply-To: <20220920145905.20595-3-macroalpha82@gmail.com>
On Tue, Sep 20, 2022 at 09:59:04AM -0500, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Add documentation for the NewVision NV3051D panel bindings.
> Note that for the two expected consumers of this panel binding
> the underlying LCD model is unknown. Name "anbernic,rg353p-panel"
> is used because the hardware itself is known as "anbernic,rg353p".
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> ---
> .../display/panel/newvision,nv3051d.yaml | 55 +++++++++++++++++++
> 1 file changed, 55 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
>
> diff --git a/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml b/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
> new file mode 100644
> index 000000000000..d90bca4171c2
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
> @@ -0,0 +1,55 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/display/panel/newvision,nv3051d.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NewVision NV3051D based LCD panel
> +
> +description: |
> + The NewVision NV3051D is a driver chip used to drive DSI panels. For now,
> + this driver only supports the 640x480 panels found in the Anbernic RG353
> + based devices.
> +
> +maintainers:
> + - Chris Morgan <macromorgan@hotmail.com>
> +
> +allOf:
> + - $ref: panel-common.yaml#
> +
> +properties:
> + compatible:
> + items:
> + - enum:
> + - anbernic,rg353p-panel
> + - anbernic,rg353v-panel
Is 'panel' redundant? IOW, could 'rg353v' identify something else other
than the panel?
Rob
next prev parent reply other threads:[~2022-09-24 17:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 14:59 [PATCH V2 0/3] drm/panel: Add NewVision NV3051D Panels Chris Morgan
2022-09-20 14:59 ` [PATCH V2 1/3] dt-bindings: vendor-prefixes: add NewVision vendor prefix Chris Morgan
2022-09-21 6:50 ` Krzysztof Kozlowski
2022-09-20 14:59 ` [PATCH V2 2/3] dt-bindings: display: panel: Add NewVision NV3051D bindings Chris Morgan
2022-09-21 6:51 ` Krzysztof Kozlowski
2022-09-21 14:38 ` Chris Morgan
2022-09-21 15:21 ` Krzysztof Kozlowski
2022-09-21 15:50 ` Chris Morgan
2022-09-21 15:57 ` Krzysztof Kozlowski
2022-09-21 16:17 ` Chris Morgan
2022-09-21 7:01 ` Krzysztof Kozlowski
2022-09-24 17:07 ` Rob Herring [this message]
2022-09-24 17:51 ` Chris Morgan
2022-09-20 14:59 ` [PATCH V2 3/3] drm/panel: Add NewVision NV3051D MIPI-DSI LCD panel Chris Morgan
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=20220924170744.GA961091-robh@kernel.org \
--to=robh@kernel.org \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=macroalpha82@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=sam@ravnborg.org \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).