public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	"linux-renesas-soc@vger.kernel.org"
	<linux-renesas-soc@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
	"biju.das.au" <biju.das.au@gmail.com>
Subject: Re: [PATCH 03/12] dt-bindings: soc: renesas: Document RZ/G3E SMARC SoM and Carrier-II EVK
Date: Wed, 27 Nov 2024 20:02:11 +0000	[thread overview]
Message-ID: <20241127-cargo-impish-9117a49fa425@spud> (raw)
In-Reply-To: <TY3PR01MB11346A0C7A4DAD6A250A6B55386282@TY3PR01MB11346.jpnprd01.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3288 bytes --]

On Wed, Nov 27, 2024 at 05:18:56PM +0000, Biju Das wrote:
> Hi Conor Dooley,
> 
> Thanks for the feedback.
> 
> > -----Original Message-----
> > From: Conor Dooley <conor@kernel.org>
> > Sent: 27 November 2024 16:33
> > Subject: Re: [PATCH 03/12] dt-bindings: soc: renesas: Document RZ/G3E SMARC SoM and Carrier-II EVK
> > 
> > On Wed, Nov 27, 2024 at 12:34:42PM +0000, Biju Das wrote:
> > > Hi Conor Dooley,
> > >
> > > Thanks for the feedback.
> > >
> > > > -----Original Message-----
> > > > From: Conor Dooley <conor@kernel.org>
> > > > Sent: 25 November 2024 18:52
> > > > Subject: Re: [PATCH 03/12] dt-bindings: soc: renesas: Document
> > > > RZ/G3E SMARC SoM and Carrier-II EVK
> > > >
> > > > On Fri, Nov 22, 2024 at 12:45:39PM +0000, Biju Das wrote:
> > > > > Document the Renesas RZ/G3E SMARC Carrier-II EVK board which is
> > > > > based on the Renesas RZ/G3E SMARC SoM. The RZ/G3E SMARC Carrier-II
> > > > > EVK consists of an RZ/G3E SoM module and a SMARC Carrier-II carrier board.
> > > > > The SoM module sits on top of the carrier board.
> > > > >
> > > > > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > > > > ---
> > > > >  Documentation/devicetree/bindings/soc/renesas/renesas.yaml | 4
> > > > > ++++
> > > > >  1 file changed, 4 insertions(+)
> > > > >
> > > > > diff --git
> > > > > a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > > > > b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > > > > index 7cc2bb97db13..1785142fc8da 100644
> > > > > --- a/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > > > > +++ b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> > > > > @@ -527,6 +527,10 @@ properties:
> > > > >
> > > > >        - description: RZ/G3E (R9A09G047)
> > > > >          items:
> > > > > +          - enum:
> > > > > +              - renesas,smarc2-evk # RZ SMARC Carrier-II EVK
> > > > > +          - enum:
> > > > > +              - renesas,rzg3e-smarcm # RZ/G3E SMARC Module (SoM)
> > > >
> > > > Why are these enums, when you have a single item in each?
> > >
> > > I just followed the style used in [1]
> > >
> > > [1]
> > > https://elixir.bootlin.com/linux/v6.12.1/source/Documentation/devicetr
> > > ee/bindings/soc/renesas/renesas.yaml#L531
> > 
> > It ain't the same though, since you additionally have the SoM.
> > 
> > > Other than that,
> > >
> > > In future some vendors can add their RZ/G3E SoM's here
> > 
> > Only makes sense if their SoM is compatible with the smarc2-evk.
> 
> All our SMARC Modules and SMARC Carrier boards are SMARC compliant.

All of yours might be, but what you said was "some vendors".

> 
> So, if anyone have a RZ/G3E SMARC SoM, that should work with SMARC2-EVK.
> 
> > 
> > > Or
> > >
> > > They can use Renesas RZ/G3E SMARC module and use their custom carrier boards.
> > 
> > But allowing this part does make sense.
> 
> We already have a use case for this example.
> 
> Renesas RZ/G3E SoM can work on both Renesas smarc-evk and smarc2-evk.
> 
> But we only officially support RZ/G3E SoM with SMARC2-EVK as it has multiple display support.
> 
> So, can I use const for both SoM and Carrier EVK as at the moment there is only
> one?

That is what I would do.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2024-11-27 20:02 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-22 12:45 [PATCH 00/12] Add support for Renesas RZ/G3E SoC and SMARC-EVK platform Biju Das
2024-11-22 12:45 ` [PATCH 01/12] dt-bindings: serial: renesas: Document RZ/G3E (r9a09g047) scif Biju Das
2024-11-25 18:50   ` Conor Dooley
2024-11-22 12:45 ` [PATCH 02/12] dt-bindings: soc: renesas: Document Renesas RZ/G3E SoC variants Biju Das
2024-11-25 18:51   ` Conor Dooley
2024-11-22 12:45 ` [PATCH 03/12] dt-bindings: soc: renesas: Document RZ/G3E SMARC SoM and Carrier-II EVK Biju Das
2024-11-25 18:52   ` Conor Dooley
2024-11-27 12:34     ` Biju Das
2024-11-27 16:33       ` Conor Dooley
2024-11-27 17:18         ` Biju Das
2024-11-27 20:02           ` Conor Dooley [this message]
2024-11-28  6:51             ` Biju Das
2024-11-28  8:49               ` Geert Uytterhoeven
2024-11-22 12:45 ` [PATCH 04/12] dt-bindings: clock: renesas: Document RZ/G3E SoC CPG Biju Das
2024-11-25 18:52   ` Conor Dooley
2024-11-29 14:44   ` Biju Das
2024-11-22 12:45 ` [PATCH 08/12] arm64: dts: renesas: Add initial DTSI for RZ/G3E SoC Biju Das
2024-11-22 12:45 ` [PATCH 09/12] arm64: dts: renesas: Add initial support for RZ/G3E SMARC SoM Biju Das
2024-11-22 12:45 ` [PATCH 10/12] arm64: dts: renesas: Add initial device tree for RZ/G3E SMARC EVK board Biju Das

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=20241127-cargo-impish-9117a49fa425@spud \
    --to=conor@kernel.org \
    --cc=biju.das.au@gmail.com \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    --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