From: Pratyush Yadav <p.yadav@ti.com>
To: Parshuram Thombare <pthombar@cadence.com>
Cc: <broonie@kernel.org>, <lukas@wunner.de>, <robh+dt@kernel.org>,
<linux-spi@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <jpawar@cadence.com>,
<mparab@cadence.com>, Konrad Kociolek <konrad@cadence.com>
Subject: Re: [PATCH v3 1/2] spi: cadence: add dt-bindings documentation for Cadence XSPI controller
Date: Fri, 3 Sep 2021 23:47:24 +0530 [thread overview]
Message-ID: <20210903181722.ukarfanyew2b7yoz@ti.com> (raw)
In-Reply-To: <1630499829-20059-1-git-send-email-pthombar@cadence.com>
On 01/09/21 02:37PM, Parshuram Thombare wrote:
> Add DT binding for Cadence's XSPI controller driver.
>
> Signed-off-by: Konrad Kociolek <konrad@cadence.com>
> Signed-off-by: Jayshri Pawar <jpawar@cadence.com>
> Signed-off-by: Parshuram Thombare <pthombar@cadence.com>
> ---
> .../devicetree/bindings/spi/cdns,xspi.yaml | 66 ++++++++++++++++++++++
> 1 file changed, 66 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/spi/cdns,xspi.yaml
>
> diff --git a/Documentation/devicetree/bindings/spi/cdns,xspi.yaml b/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> new file mode 100644
> index 0000000..e52d6fa
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/cdns,xspi.yaml
> @@ -0,0 +1,66 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +# Copyright 2020-21 Cadence
> +%YAML 1.2
> +---
> +$id: "http://devicetree.org/schemas/spi/cdns,xspi.yaml#"
> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
> +
> +title: Cadence XSPI Controller
> +
> +maintainers:
> + - Parshuram Thombare <pthombar@cadence.com>
> +
> +description: |
> + The XSPI controller allows SPI protocol communication in
> + single, dual, quad or octal wire transmission modes for
> + read/write access to slaves such as SPI-NOR flash.
This needs to be a "subclass" of the spi-controller.yaml binding.
allOf:
- $ref: spi-controller.yaml#
> +
> +properties:
> + compatible:
> + const: cdns,xspi-nor
> +
> + reg:
> + items:
> + - description: address and length of the controller register set
> + - description: address and length of the Slave DMA data port
> + - description: address and length of the auxiliary registers
> +
> + reg-names:
> + items:
> + - const: xspi-iobase
> + - const: xspi-sdmabase
> + - const: xspi-auxbase
> +
> + interrupts:
> + maxItems: 1
> +
> +required:
> + - compatible
> + - reg
> + - interrupts
> +
> +examples:
> + - |
> + #include <dt-bindings/interrupt-controller/irq.h>
> +
> + xspi: spi@a0010000 {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + compatible = "cdns,xspi-nor";
> + reg = <0x0 0xa0010000 0x0 0x10000>,
> + <0x0 0xb0000000 0x0 0x10000>,
> + <0x0 0xa0020000 0x0 0x10000>;
> + reg-names = "xspi-iobase", "xspi-sdmabase", "xspi-auxbase";
> + interrupts = <0 90 IRQ_TYPE_LEVEL_HIGH>;
> + interrupt-parent = <&gic>;
> + mt35xu512@0 {
Node name should be flash@0.
> + 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.
Please run dt_binding_check, it should point this out. See [0].
> + spi-max-frequency = <75000000>;
> + reg = <0>;
> + };
> + mt35xu512@1 {
> + compatible = "spi-nor", "micron,mt35xu512";
Same as above.
> + spi-max-frequency = <75000000>;
> + reg = <1>;
> + };
> + };
> --
> 2.7.4
>
[0] https://www.kernel.org/doc/html/latest/devicetree/bindings/writing-schema.html#testing
--
Regards,
Pratyush Yadav
Texas Instruments Inc.
next prev parent reply other threads:[~2021-09-03 18:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 12:35 [PATCH v3 0/2] add support for Cadence's " Parshuram Thombare
2021-09-01 12:37 ` [PATCH v3 1/2] spi: cadence: add dt-bindings documentation for Cadence " Parshuram Thombare
2021-09-02 12:03 ` Rob Herring
2021-09-03 8:03 ` Parshuram Raju Thombare
2021-09-03 18:17 ` Pratyush Yadav [this message]
2021-09-08 6:52 ` Parshuram Raju Thombare
2021-09-08 11:32 ` Pratyush Yadav
2021-09-08 11:58 ` Parshuram Raju Thombare
2021-09-01 12:37 ` [PATCH v3 2/2] spi: cadence: add support " Parshuram Thombare
2021-09-02 14:39 ` Mark Brown
2021-09-03 8:10 ` Parshuram Raju Thombare
2021-09-03 10:18 ` Mark Brown
2021-09-03 10:47 ` Parshuram Raju Thombare
2021-09-03 11:24 ` Mark Brown
2021-09-03 18:56 ` Pratyush Yadav
2021-09-08 7:27 ` Parshuram Raju Thombare
2021-09-08 11:21 ` Pratyush Yadav
2021-09-08 11:40 ` Parshuram Raju Thombare
2021-09-08 12:24 ` Mark Brown
2021-09-08 16:22 ` Pratyush Yadav
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210903181722.ukarfanyew2b7yoz@ti.com \
--to=p.yadav@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jpawar@cadence.com \
--cc=konrad@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mparab@cadence.com \
--cc=pthombar@cadence.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome