From: Krzysztof Kozlowski <krzk@kernel.org>
To: Biju <biju.das.au@gmail.com>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Vincent Mailhol <mailhol@kernel.org>,
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>
Cc: Biju Das <biju.das.jz@bp.renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
linux-can@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: can: renesas,rcar-canfd: Document renesas,fd-only property
Date: Sun, 23 Nov 2025 14:25:35 +0100 [thread overview]
Message-ID: <3928e893-66e1-4873-a78b-75e38e746661@kernel.org> (raw)
In-Reply-To: <20251123112326.128448-2-biju.das.jz@bp.renesas.com>
On 23/11/2025 12:23, Biju wrote:
> From: Biju Das <biju.das.jz@bp.renesas.com>
>
> The CANFD on RZ/{G2L,G3E} and R-Car Gen4 support 3 modes FD-Only mode,
> Classical CAN mode and CAN-FD mode. In FD-Only mode, communication in
> Classical CAN frame format is disabled. Document renesas,fd-only to handle
> this mode. As these SoCs support 3 modes, update the description of
> renesas,no-can-fd property and disallow it for R-Car Gen3.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
> ---
> v1->v2:
> * Added conditional check to disallow fd-only mode for R-Car Gen3.
> ---
> .../bindings/net/can/renesas,rcar-canfd.yaml | 24 ++++++++++++++++---
> 1 file changed, 21 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
> index f4ac21c68427..a52244f0b5d1 100644
> --- a/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
> +++ b/Documentation/devicetree/bindings/net/can/renesas,rcar-canfd.yaml
> @@ -125,9 +125,17 @@ properties:
> renesas,no-can-fd:
> $ref: /schemas/types.yaml#/definitions/flag
> description:
> - The controller can operate in either CAN FD only mode (default) or
> - Classical CAN only mode. The mode is global to all channels.
> - Specify this property to put the controller in Classical CAN only mode.
> + The controller can operate in either CAN-FD mode (default) or FD-Only
> + mode (RZ/{G2L,G3E} and R-Car Gen4) or Classical CAN mode. Specify this
> + property to put the controller in Classical CAN mode.
> +
> + renesas,fd-only:
> + $ref: /schemas/types.yaml#/definitions/flag
> + description:
> + The CANFD on RZ/{G2L,G3E} and R-Car Gen4 SoCs support 3 modes FD-Only
> + mode, Classical CAN mode and CAN-FD mode (default). In FD-Only mode,
> + communication in Classical CAN frame format is disabled. Specify this
> + property to put the controller in FD-Only mode.
>
> assigned-clocks:
> description:
> @@ -267,6 +275,16 @@ allOf:
> patternProperties:
> "^channel[6-7]$": false
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - renesas,rcar-gen3-canfd
> + then:
> + properties:
> + renesas,fd-only: false
> +
You did not respond to my first paragraph from previous version. As I
said, you now need oneOf to restrict these, since you are not using
simple enum.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-11-23 13:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-23 11:23 [PATCH v2 0/2] Add FD-Only mode support for R-Car CANFD Biju
2025-11-23 11:23 ` [PATCH v2 1/2] dt-bindings: can: renesas,rcar-canfd: Document renesas,fd-only property Biju
2025-11-23 13:25 ` Krzysztof Kozlowski [this message]
2025-11-23 14:06 ` Biju Das
2025-11-23 14:17 ` Biju Das
2025-11-23 14:21 ` Krzysztof Kozlowski
2025-11-23 15:15 ` Biju Das
2025-11-23 15:23 ` Krzysztof Kozlowski
2025-11-23 15:53 ` 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=3928e893-66e1-4873-a78b-75e38e746661@kernel.org \
--to=krzk@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=fabrizio.castro.jz@renesas.com \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mailhol@kernel.org \
--cc=mkl@pengutronix.de \
--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