From: Rob Herring <robh@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol.vincent@wanadoo.fr>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Simon Horman <horms@kernel.org>,
Duy Nguyen <duy.nguyen.rh@renesas.com>,
linux-can@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>
Subject: Re: [PATCH v2 2/7] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3E support
Date: Fri, 21 Feb 2025 17:18:56 -0600 [thread overview]
Message-ID: <20250221231856.GA329615-robh@kernel.org> (raw)
In-Reply-To: <20250221-childlike-deepen-8daa4513d5b5@spud>
On Fri, Feb 21, 2025 at 05:53:43PM +0000, Conor Dooley wrote:
> On Thu, Feb 20, 2025 at 01:04:18PM +0000, Biju Das wrote:
> > Document support for the CAN-FD Interface on the RZ/G3E (R9A09G047) SoC,
> > which supports up to six channels.
> >
> > The CAN-FD module on RZ/G3E is very similar to the one on both R-Car V4H
> > and RZ/G2L, but differs in some hardware parameters:
> > * No external clock, but instead has ram clock.
> > * Support up to 6 channels.
> > * 20 interrupts.
> >
> > Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> > ---
> > v1->v2:
> > * No change.
> > ---
> > .../bindings/net/can/renesas,rcar-canfd.yaml | 67 +++++++++++++++++--
> > 1 file changed, 62 insertions(+), 5 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
> > index f87f90f431e5..189d5303ad75 100644
> > --- a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
> > +++ b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
> > @@ -42,6 +42,8 @@ properties:
> > - renesas,r9a07g054-canfd # RZ/V2L
> > - const: renesas,rzg2l-canfd # RZ/G2L family
> >
> > + - const: renesas,r9a09g047-canfd # RZ/G3E
> > +
> > reg:
> > maxItems: 1
> >
> > @@ -59,6 +61,19 @@ properties:
> > - description: CAN1 error interrupt
> > - description: CAN1 transmit interrupt
> > - description: CAN1 transmit/receive FIFO receive completion interrupt
> > + - description: CAN2 error interrupt
> > + - description: CAN2 transmit interrupt
> > + - description: CAN2 transmit/receive FIFO receive completion interrupt
> > + - description: CAN3 error interrupt
> > + - description: CAN3 transmit interrupt
> > + - description: CAN3 transmit/receive FIFO receive completion interrupt
> > + - description: CAN4 error interrupt
> > + - description: CAN4 transmit interrupt
> > + - description: CAN4 transmit/receive FIFO receive completion interrupt
> > + - description: CAN5 error interrupt
> > + - description: CAN5 transmit interrupt
> > + - description: CAN5 transmit/receive FIFO receive completion interrupt
> > + minItems: 8
> >
> > interrupt-names:
> > oneOf:
> > @@ -74,15 +89,33 @@ properties:
> > - const: ch1_err
> > - const: ch1_rec
> > - const: ch1_trx
> > + - const: ch2_err
> > + - const: ch2_rec
> > + - const: ch2_trx
> > + - const: ch3_err
> > + - const: ch3_rec
> > + - const: ch3_trx
> > + - const: ch4_err
> > + - const: ch4_rec
> > + - const: ch4_trx
> > + - const: ch5_err
> > + - const: ch5_rec
> > + - const: ch5_trx
> > + minItems: 8
> >
> > clocks:
> > maxItems: 3
> >
> > clock-names:
> > - items:
> > - - const: fck
> > - - const: canfd
> > - - const: can_clk
> > + oneOf:
> > + - items:
> > + - const: fck
> > + - const: canfd
> > + - const: can_clk
> > + - items:
> > + - const: fck
> > + - const: ram_clk
> > + - const: can_clk
> >
> > power-domains:
> > maxItems: 1
> > @@ -173,7 +206,9 @@ allOf:
> > properties:
> > compatible:
> > contains:
> > - const: renesas,rzg2l-canfd
> > + enum:
> > + - renesas,r9a09g047-canfd
> > + - renesas,rzg2l-canfd
> > then:
> > properties:
> > resets:
> > @@ -187,6 +222,19 @@ allOf:
> > required:
> > - reset-names
> >
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + const: renesas,r9a09g047-canfd
> > + then:
> > + properties:
> > + interrupts:
> > + maxItems: 20
> > +
> > + interrupt-names:
> > + maxItems: 20
>
> Should these be minItems instead of maxItems? The list has 20 elements
> at the moment (right?) so you're not adding any restriction here.
And the existing platforms need to have 'maxItems: 8'.
next prev parent reply other threads:[~2025-02-21 23:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 13:04 [PATCH v2 0/7] Add support for RZ/G3E CANFD Biju Das
2025-02-20 13:04 ` [PATCH v2 1/7] dt-bindings: can: renesas,rcar-canfd: Simplify the conditional schema Biju Das
2025-02-21 17:51 ` Conor Dooley
2025-02-20 13:04 ` [PATCH v2 2/7] dt-bindings: can: renesas,rcar-canfd: Document RZ/G3E support Biju Das
2025-02-21 17:53 ` Conor Dooley
2025-02-21 18:03 ` Biju Das
2025-02-21 23:18 ` Rob Herring [this message]
2025-02-22 8:20 ` Biju Das
2025-02-20 13:04 ` [PATCH v2 3/7] can: rcar_canfd: Use of_get_available_child_by_name() Biju Das
2025-02-20 13:17 ` Geert Uytterhoeven
2025-02-20 13:04 ` [PATCH v2 4/7] can: rcar_canfd: Add gen4_type variable to struct rcar_canfd_hw_info Biju Das
2025-02-24 10:11 ` Geert Uytterhoeven
2025-02-24 10:36 ` Biju Das
2025-02-20 13:04 ` [PATCH v2 5/7] can: rcar_canfd: Add only_internal_clks " Biju Das
2025-02-20 13:04 ` [PATCH v2 6/7] can: rcar_canfd: Enhance multi_channel_irqs handling Biju Das
2025-02-20 13:04 ` [PATCH v2 7/7] can: rcar_canfd: Add RZ/G3E support 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=20250221231856.GA329615-robh@kernel.org \
--to=robh@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=duy.nguyen.rh@renesas.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=horms@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.