From: "Cédric Le Goater" <clg@kaod.org>
To: Rob Herring <robh@kernel.org>
Cc: <linux-spi@vger.kernel.org>, <linux-mtd@lists.infradead.org>,
Mark Brown <broonie@kernel.org>,
Tudor Ambarus <tudor.ambarus@microchip.com>,
Pratyush Yadav <p.yadav@ti.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
<linux-aspeed@lists.ozlabs.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 02/10] dt-bindings: spi: Add Aspeed SMC controllers device tree binding
Date: Thu, 17 Feb 2022 09:37:02 +0100 [thread overview]
Message-ID: <a77fe4bb-c4d6-4329-b25e-26e990e8092b@kaod.org> (raw)
In-Reply-To: <YgwV5ZGCbrNhlk0s@robh.at.kernel.org>
On 2/15/22 22:06, Rob Herring wrote:
> On Mon, Feb 14, 2022 at 10:42:23AM +0100, Cédric Le Goater wrote:
>> The "interrupt" property is optional because it is only necessary for
>> controllers supporting DMAs (Not implemented yet in the new driver).
>>
>> Cc: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
>> Signed-off-by: Cédric Le Goater <clg@kaod.org>
>> ---
>> .../bindings/spi/aspeed,ast2600-fmc.yaml | 92 +++++++++++++++++++
>> 1 file changed, 92 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml b/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml
>> new file mode 100644
>> index 000000000000..ed71c4d86930
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml
>> @@ -0,0 +1,92 @@
>> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: http://devicetree.org/schemas/spi/aspeed,ast2600-fmc.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Aspeed SMC controllers bindings
>> +
>> +maintainers:
>> + - Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
>> + - Cédric Le Goater <clg@kaod.org>
>> +
>> +description: |
>> + This binding describes the Aspeed Static Memory Controllers (FMC and
>> + SPI) of the AST2400, AST2500 and AST2600 SOCs.
>> +
>> +allOf:
>> + - $ref: "spi-controller.yaml#"
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - aspeed,ast2600-fmc
>> + - aspeed,ast2600-spi
>> + - aspeed,ast2500-fmc
>> + - aspeed,ast2500-spi
>> + - aspeed,ast2400-fmc
>> + - aspeed,ast2400-spi
>> +
>> + reg:
>> + items:
>> + - description: registers
>> + - description: memory mapping
>> +
>> + clocks:
>> + maxItems: 1
>> +
>> + interrupts:
>> + maxItems: 1
>> +
>> +patternProperties:
>> + "@[0-9a-f]+":
>> + type: object
>> +
>> + properties:
>> + spi-rx-bus-width:
>> + enum: [1, 2, 4]
>> +
>> + required:
>> + - reg
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - clocks
>> +
>> +unevaluatedProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/aspeed-scu-ic.h>
>> + #include <dt-bindings/clock/ast2600-clock.h>
>> +
>> + spi@1e620000 {
>> + reg = < 0x1e620000 0xc4
>> + 0x20000000 0x10000000 >;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + compatible = "aspeed,ast2600-fmc";
>> + clocks = <&syscon ASPEED_CLK_AHB>;
>> + status = "disabled";
>
> Why is your example disabled? Drop 'status'.
my bad. I took the basic definition of the SoC and the devices
are activated in the boards. I will fix in v2.
Thanks,
C.
>
>> + interrupts = <GIC_SPI 39 IRQ_TYPE_LEVEL_HIGH>;
>> + flash@0 {
>> + reg = < 0 >;
>> + compatible = "jedec,spi-nor";
>> + spi-max-frequency = <50000000>;
>> + status = "disabled";
>
> Ditto.
>
>> + };
>> + flash@1 {
>> + reg = < 1 >;
>> + compatible = "jedec,spi-nor";
>> + spi-max-frequency = <50000000>;
>> + status = "disabled";
>> + };
>> + flash@2 {
>> + reg = < 2 >;
>> + compatible = "jedec,spi-nor";
>> + spi-max-frequency = <50000000>;
>> + status = "disabled";
>> + };
>> + };
>> --
>> 2.34.1
>>
>>
next prev parent reply other threads:[~2022-02-17 8:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-14 9:42 [PATCH 00/10] spi: spi-mem: Add driver for Aspeed SMC controllers Cédric Le Goater
2022-02-14 9:42 ` [PATCH 01/10] mtd: spi-nor: aspeed: Rename Kconfig option Cédric Le Goater
2022-02-25 7:31 ` Pratyush Yadav
2022-02-27 18:50 ` Cédric Le Goater
2022-02-28 6:07 ` Joel Stanley
2022-02-28 14:37 ` Cédric Le Goater
2022-02-14 9:42 ` [PATCH 02/10] dt-bindings: spi: Add Aspeed SMC controllers device tree binding Cédric Le Goater
2022-02-15 19:49 ` Rob Herring
2022-02-15 21:06 ` Rob Herring
2022-02-17 8:37 ` Cédric Le Goater [this message]
2022-02-14 9:42 ` [PATCH 03/10] spi: spi-mem: Add driver for Aspeed SMC controllers Cédric Le Goater
2022-02-15 6:27 ` Lukas Wunner
2022-02-15 9:07 ` Cédric Le Goater
2022-02-25 7:50 ` Pratyush Yadav
2022-02-27 18:46 ` Cédric Le Goater
2022-02-14 9:42 ` [PATCH 04/10] spi: aspeed: Add support for direct mapping Cédric Le Goater
2022-02-25 9:12 ` Pratyush Yadav
2022-02-27 21:06 ` Cédric Le Goater
2022-02-14 9:42 ` [PATCH 05/10] spi: aspeed: Adjust direct mapping to device size Cédric Le Goater
2022-02-14 9:42 ` [PATCH 06/10] spi: aspeed: Workaround AST2500 limitations Cédric Le Goater
2022-02-14 9:42 ` [PATCH 07/10] spi: aspeed: Add support for the AST2400 SPI controller Cédric Le Goater
2022-02-14 9:42 ` [PATCH 08/10] spi: aspeed: Calibrate read timings Cédric Le Goater
2022-02-25 9:18 ` Pratyush Yadav
2022-02-27 21:27 ` Cédric Le Goater
2022-02-14 9:42 ` [PATCH 09/10] ARM: dts: aspeed: Enable Dual SPI RX transfers Cédric Le Goater
2022-02-16 7:21 ` Joel Stanley
2022-02-14 9:42 ` [PATCH 10/10] spi: aspeed: Activate new spi-mem driver Cédric Le Goater
2022-02-16 7:02 ` Joel Stanley
2022-02-16 8:12 ` Cédric Le Goater
2022-02-16 7:21 ` [PATCH 00/10] spi: spi-mem: Add driver for Aspeed SMC controllers Joel Stanley
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=a77fe4bb-c4d6-4329-b25e-26e990e8092b@kaod.org \
--to=clg@kaod.org \
--cc=andrew@aj.id.au \
--cc=broonie@kernel.org \
--cc=chin-ting_kuo@aspeedtech.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=p.yadav@ti.com \
--cc=richard@nod.at \
--cc=robh@kernel.org \
--cc=tudor.ambarus@microchip.com \
--cc=vigneshr@ti.com \
/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
all inboxes | Powered by JetHome®