linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Conor Dooley <conor@kernel.org>, John Clark <inindev@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-rockchip@lists.infradead.org, robh@kernel.org,
	krzysztof.kozlowski@linaro.org, conor+dt@kernel.org,
	jonas@kwiboo.se, frattaroli.nicolas@gmail.com, andrew@lunn.ch
Subject: Re: [PATCH v3 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 and Core3576 bindings
Date: Tue, 06 May 2025 18:38:27 +0200	[thread overview]
Message-ID: <5007332.31r3eYUQgx@diego> (raw)
In-Reply-To: <c8114ff8-f207-4ea8-aaf1-298dcea9f030@gmail.com>

Hi John,

Am Dienstag, 6. Mai 2025, 17:54:10 Mitteleuropäische Sommerzeit schrieb John Clark:
> On 5/6/25 11:44 AM, Conor Dooley wrote:
> > On Tue, May 06, 2025 at 07:41:14AM -0400, John Clark wrote:
> >> Add device tree binding for the Luckfox Omni3576 Carrier Board with
> >> Core3576 Module, based on the Rockchip RK3576 SoC.
> >>
> >> Signed-off-by: John Clark <inindev@gmail.com>
> >> ---
> >>   Documentation/devicetree/bindings/arm/rockchip.yaml | 10 ++++++++++
> >>   1 file changed, 10 insertions(+)
> >>
> >> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> >> index 455fbb290b77..826dede32145 100644
> >> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> >> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> >> @@ -715,6 +715,16 @@ properties:
> >>             - const: lckfb,tspi-rk3566
> >>             - const: rockchip,rk3566
> >>   
> >> +      - description: Luckfox Core3576 Module
> >> +        items:
> >> +          - const: luckfox,core3576
> >> +          - const: rockchip,rk3576
> >> +
> >> +      - description: Luckfox Omni3576 Carrier Board
> >> +        items:
> >> +          - const: luckfox,omni3576
> >> +          - const: rockchip,rk3576
> > 
> > Not sure this is correct, does the module not have to be attached to
> > this particular carrier to be used?
> 
> The compute module and the carrier board together like the E25. 
> Presumably the compute module would be used in other applications
> but the carrier board is not useful without it.
> 
> Is the E25 done correctly here?  I can copy this format:

For the baseboard + module you should always have one of those

> >> +      - description: Luckfox Core3576 Module
> >> +        items:
> >> +          - const: luckfox,core3576
> >> +          - const: rockchip,rk3576
> >> +

      - description: Luckfox Core3576 based boards
        items:
          - enum:
              - luckfox,omni3576
          - const: luckfox,core3576
          - const: rockchip,rk3576

I've looked at the product page [0] now and the Core3576 module itself
can't work independently without a baseboard present, so the above should
be enough, and also allows for possible future other baseboards to be
integrated.


Heiko


[0] https://www.luckfox.com/EN-Core3576




  parent reply	other threads:[~2025-05-06 23:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 11:41 [PATCH v3 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 John Clark
2025-05-06 11:41 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add luckfox prefix John Clark
2025-05-06 15:45   ` Conor Dooley
2025-05-06 11:41 ` [PATCH v3 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 and Core3576 bindings John Clark
2025-05-06 15:44   ` Conor Dooley
2025-05-06 15:54     ` John Clark
2025-05-06 16:34       ` Conor Dooley
2025-05-06 16:38       ` Heiko Stübner [this message]
2025-05-06 11:41 ` [PATCH v3 3/3] arm64: dts: rockchip: Add Luckfox Omni3576 Board support John Clark
2025-05-06 17:05 ` [PATCH v3 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 Krzysztof Kozlowski
2025-05-06 17:14   ` John Clark
2025-05-06 17:16     ` Krzysztof Kozlowski
2025-05-06 18:23 ` Rob Herring (Arm)
2025-05-06 21:18   ` Heiko Stübner

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=5007332.31r3eYUQgx@diego \
    --to=heiko@sntech.de \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=inindev@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh@kernel.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).