[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e1aaf325-2bdc-4b3b-a955-35a313b44255@kernel.org>
Date: Mon, 7 Oct 2024 09:03:27 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Marcus Folkesson <marcus.folkesson@...il.com>
Cc: Miquel Raynal <miquel.raynal@...tlin.com>,
Richard Weinberger <richard@....at>, Vignesh Raghavendra <vigneshr@...com>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, linux-mtd@...ts.infradead.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v4 2/2] dt-bindings: mtd: davinci: convert to yaml
On 07/10/2024 08:29, Marcus Folkesson wrote:
> On Mon, Oct 07, 2024 at 08:07:27AM +0200, Krzysztof Kozlowski wrote:
>> On Sun, Oct 06, 2024 at 03:05:47PM +0200, Marcus Folkesson wrote:
>>> + ti,davinci-nand-use-bbt:
>>> + type: boolean
>>> + description:
>>> + Use flash based bad block table support. OOB identifier is saved in OOB
>>> + area.
>>> + deprecated: true
>>> +
>>> +required:
>>> + - compatible
>>> + - reg
>>> + - ti,davinci-chipselect
>>> +
>>> +additionalProperties: true
>>
>> That's a final device schema, this cannot be true. Why you are doing
>> this entirely different than all other bindings?
>
> From my understanding, additionalProperties is to indicate that the
> schema could contain properties that were not explicit listed here but
> inherited from e.g. nand-controller.yaml.
>
> Obviously that is not the case.
> Could you please give me some guidance?
I suggested - open any other binding. What is there? What was the exact
error automation reported to you *twice*?
Best regards,
Krzysztof
Powered by blists - more mailing lists