[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY4PR07MB27573039EAB6C6E6734F1D54C1D49@CY4PR07MB2757.namprd07.prod.outlook.com>
Date: Wed, 8 Sep 2021 11:58:35 +0000
From: Parshuram Raju Thombare <pthombar@...ence.com>
To: Pratyush Yadav <p.yadav@...com>
CC: "broonie@...nel.org" <broonie@...nel.org>,
"lukas@...ner.de" <lukas@...ner.de>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"linux-spi@...r.kernel.org" <linux-spi@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jayshri Dajiram Pawar <jpawar@...ence.com>,
Milind Parab <mparab@...ence.com>,
Konrad Kociolek <konrad@...ence.com>
Subject: RE: [PATCH v3 1/2] spi: cadence: add dt-bindings documentation for
Cadence XSPI controller
>> Isn't stating that validation need against spi-controller.yaml as well as
>> this schema sufficient ? Can you please point an example how to make
>> controller binding a "subclass" of spi-controller.yaml binding ?
>
>I just showed you. You need to add the below lines:
Oh, my bad. I already added that dependency in my local patches for next version,
I thought you are suggesting something else.
>> I think spi-controller.yaml uses wildcard for the name of a device node,
>> so anything in string@...value: should work.
>
>Sure, but mtd.yaml (which the SPI NOR binding depends on) requires it.
Ok, using "jedec,spi-nor" creates dependency on spi-nor schema, otherwise
I was not seeing any issue in " make dt_binding_check" with just "spi-nor".
This will be taken care in next version of patch set.
Regards,
Parshuram Thombare
Powered by blists - more mailing lists