From: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
To: linux-aspeed@lists.ozlabs.org
Subject: [v2 1/4] dt-bindings: spi: Add binding file for ASPEED FMC/SPI memory controller
Date: Tue, 3 Nov 2020 15:21:59 +0800 [thread overview]
Message-ID: <20201103072202.24705-2-chin-ting_kuo@aspeedtech.com> (raw)
In-Reply-To: <20201103072202.24705-1-chin-ting_kuo@aspeedtech.com>
Create binding file with YAML syntax for ASPEED FMC/SPI memory controller.
Signed-off-by: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
---
.../bindings/spi/aspeed,spi-aspeed.yaml | 66 +++++++++++++++++++
1 file changed, 66 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/aspeed,spi-aspeed.yaml
diff --git a/Documentation/devicetree/bindings/spi/aspeed,spi-aspeed.yaml b/Documentation/devicetree/bindings/spi/aspeed,spi-aspeed.yaml
new file mode 100644
index 000000000000..41b9692c7226
--- /dev/null
+++ b/Documentation/devicetree/bindings/spi/aspeed,spi-aspeed.yaml
@@ -0,0 +1,66 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/spi/aspeed,spi-aspeed.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: SPI memory controller for ASPEED SoCs
+
+maintainers:
+ - Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
+
+description: |
+ There are three SPI memory controllers embedded in a ASPEED SoC.
+ They are usually connected to SPI NOR flashes. Each of them has
+ more than a chip select. They also support SPI single, dual and
+ quad IO modes for SPI NOR flash.
+
+allOf:
+ - $ref: /spi/spi-controller.yaml#
+
+properties:
+ compatible:
+ oneOf:
+ - items:
+ - enum:
+ - aspeed,ast2600-fmc
+ - aspeed,ast2600-spi
+
+ reg:
+ items:
+ - description: the control register location and length
+ - description: the flash memory mapping address and length
+
+ clocks:
+ description: AHB bus clock which will be converted to SPI bus clock
+
+required:
+ - compatible
+ - reg
+ - clocks
+ - num-cs
+
+unevaluatedProperties: false
+
+examples:
+ - |
+ #include <dt-bindings/clock/ast2600-clock.h>
+ spi1: spi at 1e630000 {
+ compatible = "aspeed,ast2600-spi";
+ reg = <0x1e630000 0xc4>, <0x30000000 0x10000000>;
+ reg-names = "spi_ctrl_reg", "spi_mmap";
+ clocks = <&syscon ASPEED_CLK_AHB>;
+ num-cs = <2>;
+ #address-cells = <1>;
+ #size-cells = <0>;
+ flash at 0 {
+ compatible = "jedec,spi-nor";
+ reg = <0>;
+ spi-max-frequency = <50000000>;
+ };
+ flash at 1 {
+ compatible = "jedec,spi-nor";
+ reg = <1>;
+ spi-max-frequency = <50000000>;
+ };
+ };
--
2.17.1
next prev parent reply other threads:[~2020-11-03 7:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 7:21 [v2 0/4] Porting ASPEED FMC/SPI memory controller driver Chin-Ting Kuo
2020-11-03 7:21 ` Chin-Ting Kuo [this message]
2020-11-05 18:40 ` [v2 1/4] dt-bindings: spi: Add binding file for ASPEED FMC/SPI memory controller Rob Herring
2020-11-06 9:03 ` Chin-Ting Kuo
2020-11-03 7:22 ` [v2 2/4] ARM: dts: aspeed: ast2600: Update FMC/SPI controller setting for spi-aspeed.c Chin-Ting Kuo
2020-11-03 7:22 ` [v2 3/4] ARM: dts: aspeed: ast2600-evb: Adjust SPI flash configuration Chin-Ting Kuo
2020-11-03 7:22 ` [v2 4/4] spi: aspeed: Add ASPEED FMC/SPI memory controller driver Chin-Ting Kuo
2020-11-04 20:39 ` Mark Brown
2020-11-05 11:27 ` Chin-Ting Kuo
2020-12-01 13:57 ` [v2 0/4] Porting " Mark Brown
2020-12-02 21:19 ` Joel Stanley
2020-12-03 10:32 ` Mark Brown
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=20201103072202.24705-2-chin-ting_kuo@aspeedtech.com \
--to=chin-ting_kuo@aspeedtech.com \
--cc=linux-aspeed@lists.ozlabs.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