public inbox for linux-sunxi@lists.linux.dev
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@arm.com>
To: Chris Morgan <macroalpha82@gmail.com>
Cc: linux-sunxi@lists.linux.dev, devicetree@vger.kernel.org,
	mripard@kernel.org, ryan@testtoast.com, samuel@sholland.org,
	jernej.skrabec@gmail.com, wens@csie.org, conor+dt@kernel.org,
	krzk+dt@kernel.org, robh@kernel.org,
	Chris Morgan <macromorgan@hotmail.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: sunxi: Add Anbernic RG35XXSP
Date: Thu, 6 Jun 2024 11:26:14 +0100	[thread overview]
Message-ID: <20240606112614.5380b2d1@donnerap.manchester.arm.com> (raw)
In-Reply-To: <20240605185339.266833-2-macroalpha82@gmail.com>

On Wed,  5 Jun 2024 13:53:38 -0500
Chris Morgan <macroalpha82@gmail.com> wrote:

Hi,

> From: Chris Morgan <macromorgan@hotmail.com>
> 
> Add the Anbernic RG35XXSP variant device and consolidate the Anbernic
> H700 devices.
> 
> The Anbernic RG35XXSP is almost identical to the RG35XX-Plus, but in a
> clamshell form-factor.
> 
> Signed-off-by: Chris Morgan <macromorgan@hotmail.com>
> ---
>  .../devicetree/bindings/arm/sunxi.yaml        | 24 +++++++------------
>  1 file changed, 9 insertions(+), 15 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/arm/sunxi.yaml b/Documentation/devicetree/bindings/arm/sunxi.yaml
> index c2a158b75e49..1ae77e5edf9a 100644
> --- a/Documentation/devicetree/bindings/arm/sunxi.yaml
> +++ b/Documentation/devicetree/bindings/arm/sunxi.yaml
> @@ -51,25 +51,19 @@ properties:
>            - const: allwinner,parrot
>            - const: allwinner,sun8i-a33
>  
> -      - description: Anbernic RG-Nano
> -        items:
> -          - const: anbernic,rg-nano
> -          - const: allwinner,sun8i-v3s
> -
> -      - description: Anbernic RG35XX (2024)
> -        items:
> -          - const: anbernic,rg35xx-2024
> -          - const: allwinner,sun50i-h700
> -
> -      - description: Anbernic RG35XX Plus
> +      - description: Anbernic H700 Handheld Gaming Console

So that's certainly an interesting optimisation, but so far we were using
one entry per device, it seems.
I am not entirely sure what the purpose of this file is, exactly: just to
document the compatible names, to reserve them and avoid clashes in the
future? Or also to put some official names to each device? That seems to
somewhat overlap with the root node's model property in the respective
device .dts, though.

It would be good to clarify this, and establish how to group those devices.
I mean technically we could for instance put *all* H6 devices into one
entry, using the same scheme as below.
Not sure that's desired, though.

Cheers,
Andre

>          items:
> -          - const: anbernic,rg35xx-plus
> +          - enum:
> +              - anbernic,rg35xx-2024
> +              - anbernic,rg35xx-h
> +              - anbernic,rg35xx-plus
> +              - anbernic,rg35xx-sp
>            - const: allwinner,sun50i-h700
>  
> -      - description: Anbernic RG35XX H
> +      - description: Anbernic RG-Nano
>          items:
> -          - const: anbernic,rg35xx-h
> -          - const: allwinner,sun50i-h700
> +          - const: anbernic,rg-nano
> +          - const: allwinner,sun8i-v3s
>  
>        - description: Amarula A64 Relic
>          items:


  parent reply	other threads:[~2024-06-06 10:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-05 18:53 [PATCH 0/2] Add Anbernic RG35XX-SP Chris Morgan
2024-06-05 18:53 ` [PATCH 1/2] dt-bindings: arm: sunxi: Add Anbernic RG35XXSP Chris Morgan
2024-06-06  6:43   ` Krzysztof Kozlowski
2024-06-06 10:26   ` Andre Przywara [this message]
2024-06-06 11:30     ` Maxime Ripard
2024-06-06 16:55       ` Chris Morgan
2024-06-06 17:04         ` Chen-Yu Tsai
2024-06-05 18:53 ` [PATCH 2/2] arm64: dts: allwinner: h700: Add Anbernic RG35XX-SP Chris Morgan
2024-06-06  9:51   ` Andre Przywara
2024-06-06 11:58     ` Chen-Yu Tsai
2024-06-06 12:35       ` Andre Przywara
2024-06-06 17:06         ` Chris Morgan
2024-06-06 17:28           ` Andre Przywara
2024-06-06 15:56 ` [PATCH 0/2] " Rob Herring (Arm)
2024-06-06 16:52   ` 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=20240606112614.5380b2d1@donnerap.manchester.arm.com \
    --to=andre.przywara@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jernej.skrabec@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-sunxi@lists.linux.dev \
    --cc=macroalpha82@gmail.com \
    --cc=macromorgan@hotmail.com \
    --cc=mripard@kernel.org \
    --cc=robh@kernel.org \
    --cc=ryan@testtoast.com \
    --cc=samuel@sholland.org \
    --cc=wens@csie.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