[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY4PR07MB2757DF7EFD862D67FBF648CBC1D49@CY4PR07MB2757.namprd07.prod.outlook.com>
Date: Wed, 8 Sep 2021 06:52:37 +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
>This needs to be a "subclass" of the spi-controller.yaml binding.
>
>allOf:
> - $ref: spi-controller.yaml#
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 ?
>Node name should be flash@0.
I think spi-controller.yaml uses wildcard for the name of a device node,
so anything in string@...value: should work.
>> + compatible = "spi-nor", "micron,mt35xu512";
>
>These compatibles are arbitrary and undocumented. You probably just need
>"jedec,spi-nor". If you need anything else, you need to justify why.
Although just "spi-nor" also works, I agree to use "jedec, spi-nor" and drop
device name.
Regards,
Parshuram Thombare
Powered by blists - more mailing lists