From: Xianwei Zhao <xianwei.zhao@amlogic.com>
To: Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Liang Yang <liang.yang@amlogic.com>,
Feng Chen <feng.chen@amlogic.com>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v2 1/3] spi: dt-bindings: add doc for Amlogic A113L2 SFC
Date: Thu, 21 Aug 2025 17:36:50 +0800 [thread overview]
Message-ID: <6ab6359a-a20a-49c3-9179-6c9571ca05d0@amlogic.com> (raw)
In-Reply-To: <20250821-spifc-v2-1-b119f64b5c09@amlogic.com>
On 2025/8/21 13:17, Xianwei Zhao via B4 Relay wrote:
> [ EXTERNAL EMAIL ]
>
> From: Feng Chen <feng.chen@amlogic.com>
>
> Add bindings for Amlogic A113L2 SPI Flash Controller.
>
Here I misunderstood and missed the modification of Subject.I mistakenly
deleted the description.
I'll send the next version right away to solve these problems.
> Signed-off-by: Feng Chen <feng.chen@amlogic.com>
> Signed-off-by: Xianwei Zhao <xianwei.zhao@amlogic.com>
> ---
> .../devicetree/bindings/spi/amlogic,a4-spifc.yaml | 82 ++++++++++++++++++++++
> 1 file changed, 82 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/spi/amlogic,a4-spifc.yaml b/Documentation/devicetree/bindings/spi/amlogic,a4-spifc.yaml
> new file mode 100644
> index 000000000000..80a89408a832
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/spi/amlogic,a4-spifc.yaml
> @@ -0,0 +1,82 @@
> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
> +# Copyright (C) 2025 Amlogic, Inc. All rights reserved
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/spi/amlogic,a4-spifc.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: SPI flash controller for Amlogic ARM SoCs
> +
> +maintainers:
> + - Liang Yang <liang.yang@amlogic.com>
> + - Feng Chen <feng.chen@amlogic.com>
> + - Xianwei Zhao <xianwei.zhao@amlogic.com>
> +
> +description:
> + The Amlogic SPI flash controller is an extended version of the Amlogic NAND
> + flash controller. It supports SPI Nor Flash and SPI NAND Flash(where the Host
> + ECC HW engine could be enabled).
> +
> +allOf:
> + - $ref: /schemas/spi/spi-controller.yaml#
> +
> +properties:
> + compatible:
> + const: amlogic,a4-spifc
> +
> + reg:
> + maxItems: 1
> +
> + clocks:
> + items:
> + - description: clock apb gate
> + - description: clock used for the controller
> +
> + clock-names:
> + items:
> + - const: gate
> + - const: core
> +
> + interrupts:
> + maxItems: 1
> +
> + amlogic,rx-adj:
> + description:
> + Adjust sample timing for RX, Sampling time move later by 1 bus clock.
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [0, 1, 2, 3]
> + default: 0
> +
> +required:
> + - compatible
> + - reg
> + - clocks
> + - clock-names
> +
> +unevaluatedProperties: false
> +
> +examples:
> + - |
> + sfc0: spi@fe08d000 {
> + compatible = "amlogic,a4-spifc";
> + reg = <0xfe08d000 0x800>;
> + clocks = <&clkc_periphs 31>,
> + <&clkc_periphs 102>;
> + clock-names = "gate", "core";
> +
> + pinctrl-0 = <&spiflash_default>;
> + pinctrl-names = "default";
> +
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + flash@0 {
> + compatible = "spi-nand";
> + reg = <0>;
> + #address-cells = <1>;
> + #size-cells = <1>;
> + nand-ecc-engine = <&sfc0>;
> + nand-ecc-strength = <8>;
> + nand-ecc-step-size = <512>;
> + };
> + };
>
> --
> 2.37.1
>
>
next prev parent reply other threads:[~2025-08-21 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 5:17 [PATCH v2 0/3] support for Amlogic SPI Flash Controller IP Xianwei Zhao via B4 Relay
2025-08-21 5:17 ` [PATCH v2 1/3] spi: dt-bindings: add doc for Amlogic A113L2 SFC Xianwei Zhao via B4 Relay
2025-08-21 9:36 ` Xianwei Zhao [this message]
2025-08-21 5:17 ` [PATCH v2 2/3] spi: amlogic: add driver for Amlogic SPI Flash Controller Xianwei Zhao via B4 Relay
2025-08-21 5:17 ` [PATCH v2 3/3] MAINTAINERS: Add an entry for Amlogic spifc driver Xianwei Zhao via B4 Relay
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=6ab6359a-a20a-49c3-9179-6c9571ca05d0@amlogic.com \
--to=xianwei.zhao@amlogic.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=feng.chen@amlogic.com \
--cc=krzk+dt@kernel.org \
--cc=liang.yang@amlogic.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).