[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87a4y5pw33.fsf@bootlin.com>
Date: Thu, 22 Jan 2026 15:21:04 +0100
From: Miquel Raynal <miquel.raynal@...tlin.com>
To: Rob Herring <robh@...nel.org>
Cc: Mark Brown <broonie@...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>, Vaishnav Achath <vaishnav.a@...com>, Thomas
Petazzoni <thomas.petazzoni@...tlin.com>, Hervé Codina
<herve.codina@...tlin.com>, Wolfram Sang
<wsa+renesas@...g-engineering.com>, Vignesh Raghavendra
<vigneshr@...com>, Santhosh Kumar K <s-k6@...com>, Pratyush Yadav
<pratyush@...nel.org>, Pascal Eberhard <pascal.eberhard@...com>,
linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org
Subject: Re: [PATCH v3 01/17] spi: dt-bindings: cdns,qspi-nor: Remove
duplicated constraints
On 21/01/2026 at 16:14:00 -06, Rob Herring <robh@...nel.org> wrote:
> On Wed, Jan 21, 2026 at 06:04:57PM +0100, Miquel Raynal (Schneider Electric) wrote:
>> The if/then/else block sets the restrictions in all cases for
>> resets/reset-names, very much like it does for other properties as well
>> such as cdns,fifo-depth. Drop the constraints from the place where these
>> constraints are simply ignored.
>
> But they aren't.
I looked deeper. Indeed the two constraints are applied, and it works
because the constraints in "if" blocks must be subsets of what is
already a constraint in the main body.
...
>> - resets:
>> - minItems: 2
>> - maxItems: 3
>> -
>> - reset-names:
>> - minItems: 2
>> - maxItems: 3
>> - items:
>> - enum: [ qspi, qspi-ocp, rstc_ref ]
>
> The primary reason to keep this is to prevent making up other names. If
> the names are only in if/then schemas then anything is allowed and it's
> not visible in reviews.
Makes sense. I will drop this patch.
Thanks,
Miquèl
Powered by blists - more mailing lists