[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <dd053cff-af8f-4378-9550-9f99f91cea20@kernel.org>
Date: Mon, 12 Jan 2026 17:30:38 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@...il.com>
Cc: Marc Kleine-Budde <mkl@...gutronix.de>,
Vincent Mailhol <mailhol@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
<conor+dt@...nel.org>, Geert Uytterhoeven <geert+renesas@...der.be>,
Magnus Damm <magnus.damm@...il.com>, linux-can@...r.kernel.org,
devicetree@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
linux-kernel@...r.kernel.org, Biju Das <biju.das.jz@...renesas.com>,
Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
Subject: Re: [PATCH v3 3/4] dt-bindings: can: renesas,rcar-canfd: Document
RZ/T2H and RZ/N2H SoCs
On 12/01/2026 15:04, Lad, Prabhakar wrote:
> - if:
> properties:
> compatible:
> contains:
> # SoCs WITH resets but WITHOUT reset-names
> enum:
> - renesas,rcar-gen3-canfd
> - renesas,rcar-gen4-canfd
> then:
> required:
> - resets
> properties:
> reset-names: false
>
Yes, although now I wonder why do you have such case... There are no
benefits in disallowing reset-names, even for single entries.
Best regards,
Krzysztof
Powered by blists - more mailing lists