[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52ede134-143d-4571-9aef-34bc54d4bc01@kernel.org>
Date: Tue, 13 Jan 2026 22:01:41 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
"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 13/01/2026 20:25, Geert Uytterhoeven wrote:
> On Mon, 12 Jan 2026 at 18:22, Lad, Prabhakar <prabhakar.csengg@...il.com> wrote:
>> On Mon, Jan 12, 2026 at 4:30 PM Krzysztof Kozlowski <krzk@...nel.org> wrote:
>>> 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.
>
> Except that I have no idea which of the two names I should use in
> case of renesas,rcar-gen3-canfd and renesas,rcar-gen4-canfd, as
> the hardware documentation doesn't explain that? AFAIU it is just
> a single, common reset for the whole block...
So there is a reason why reset-names should be disallowed :). It's fine
then.
Best regards,
Krzysztof
Powered by blists - more mailing lists