From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Chris Morgan <macroalpha82@gmail.com>, dri-devel@lists.freedesktop.org
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
daniel@ffwll.ch, airlied@gmail.com, sam@ravnborg.org,
neil.armstrong@linaro.org, Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: display: newvision,nv3051d: Add Anbernic 351V Support
Date: Sat, 5 Aug 2023 23:14:26 +0200 [thread overview]
Message-ID: <11171a47-cb9f-8369-e590-587aa8ca457e@linaro.org> (raw)
In-Reply-To: <20230804164503.135169-2-macroalpha82@gmail.com>
On 04/08/2023 18:45, Chris Morgan wrote:
> From: Chris Morgan <macromorgan@hotmail.com>
>
> Document the Anbernic RG351V panel, which appears to be identical to
> the panel used in their 353 series except for in inclusion of an
> additional DSI format flag.
>
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> ---
> .../display/panel/newvision,nv3051d.yaml | 18 +++++++++++-------
> 1 file changed, 11 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml b/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
> index 116c1b6030a2..1226db3613e6 100644
> --- a/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/newvision,nv3051d.yaml
> @@ -8,8 +8,8 @@ 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.
> + this driver only supports the 640x480 panels found in the Anbernic RG351
> + and 353 based devices.
I would prefer to drop the reference to driver entirely. It's not
related to the bindings. If driver changes (e.g. supports 1024x768),
then binding changes as well?
>
> maintainers:
> - Chris Morgan <macromorgan@hotmail.com>
> @@ -19,11 +19,15 @@ allOf:
>
> properties:
> compatible:
> - items:
> - - enum:
> - - anbernic,rg353p-panel
> - - anbernic,rg353v-panel
> - - const: newvision,nv3051d
> + oneOf:
> + - items:
> + - enum:
> + - anbernic,rg353p-panel
> + - anbernic,rg353v-panel
> + - const: newvision,nv3051d
> +
> + - items:
> + - const: anbernic,rg351v-panel
This part is good, so with adjusting description:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-05 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 16:45 [PATCH 0/2] Support Anbernic RG351V Panel Chris Morgan
2023-08-04 16:45 ` [PATCH 1/2] dt-bindings: display: newvision,nv3051d: Add Anbernic 351V Support Chris Morgan
2023-08-05 21:14 ` Krzysztof Kozlowski [this message]
2023-08-04 16:45 ` [PATCH 2/2] drm/panel: nv3051d: Add Support for Anbernic 351V 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=11171a47-cb9f-8369-e590-587aa8ca457e@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=daniel@ffwll.ch \
--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=neil.armstrong@linaro.org \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.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 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).