[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220316174306.GC21737@9a2d8922b8f1>
Date: Wed, 16 Mar 2022 23:13:06 +0530
From: Kuldeep Singh <singh.kuldeep87k@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>
Cc: Marc Zyngier <marc.zyngier@....com>,
Mark Rutland <mark.rutland@....com>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: timer: Document arm,cortex-a7-timer for
arch timer
On Wed, Mar 16, 2022 at 05:28:49PM +0100, Krzysztof Kozlowski wrote:
> On 16/03/2022 10:54, Kuldeep Singh wrote:
> > Renesas RZ/N1D platform uses compatible "arm,cortex-a7-timer" in
> > conjugation with "arm,armv7-timer". Since, initial entry is not
> > documented, it start raising dtbs_check warnings.
> >
> > ['arm,cortex-a7-timer', 'arm,armv7-timer'] is too long
> > 'arm,cortex-a7-timer' is not one of ['arm,armv7-timer', 'arm,armv8-timer']
> > 'arm,cortex-a7-timer' is not one of ['arm,cortex-a15-timer']
> >
> > In general, removing an existing entry is mostly devastating considering
> > backward compatibility. Therefore, document it.
>
> How removing undocumented and unused compatible is devastating for
> backwards compatibility? I don't see it.
>
> DTS is rather wrong, not bindings. Otherwise please explain it more, why
> DTS is correct.
Please see my comment on 3/3 patch.
- Kuldeep
Powered by blists - more mailing lists