From: Conor Dooley <conor@kernel.org>
To: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au, clg@kaod.org,
clg@redhat.com, broonie@kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
openbmc@lists.ozlabs.org, linux-spi@vger.kernel.org,
BMC-SW@aspeedtech.com
Subject: Re: [PATCH 1/4] dt-bindings: spi: aspeed,ast2600-fmc: Add AST2700 SoC support
Date: Thu, 13 Nov 2025 19:36:19 +0000 [thread overview]
Message-ID: <20251113-reroute-backlit-b2e1d1b6dc04@spud> (raw)
In-Reply-To: <20251113085332.89688-2-chin-ting_kuo@aspeedtech.com>
[-- Attachment #1: Type: text/plain, Size: 1419 bytes --]
On Thu, Nov 13, 2025 at 04:53:29PM +0800, Chin-Ting Kuo wrote:
> Add AST2700 to the list of supported SoCs in the ASPEED FMC/SPI bindings.
Please add information here as to why these devices are not compatible
with the ast2600 ones. With that info,
Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: changes-requested
>
> Signed-off-by: Chin-Ting Kuo <chin-ting_kuo@aspeedtech.com>
> ---
> Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml b/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml
> index 57d932af4506..80e542624cc6 100644
> --- a/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml
> +++ b/Documentation/devicetree/bindings/spi/aspeed,ast2600-fmc.yaml
> @@ -12,7 +12,7 @@ maintainers:
>
> description: |
> This binding describes the Aspeed Static Memory Controllers (FMC and
> - SPI) of the AST2400, AST2500 and AST2600 SOCs.
> + SPI) of the AST2400, AST2500, AST2600 and AST2700 SOCs.
>
> allOf:
> - $ref: spi-controller.yaml#
> @@ -20,6 +20,8 @@ allOf:
> properties:
> compatible:
> enum:
> + - aspeed,ast2700-fmc
> + - aspeed,ast2700-spi
> - aspeed,ast2600-fmc
> - aspeed,ast2600-spi
> - aspeed,ast2500-fmc
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-13 19:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 8:53 [PATCH 0/4] spi: aspeed: Add AST2700 SoC support and Quad SPI handling update Chin-Ting Kuo
2025-11-13 8:53 ` [PATCH 1/4] dt-bindings: spi: aspeed,ast2600-fmc: Add AST2700 SoC support Chin-Ting Kuo
2025-11-13 19:36 ` Conor Dooley [this message]
2025-11-14 0:57 ` Chin-Ting Kuo
2025-11-13 8:53 ` [PATCH 2/4] spi: aspeed: Enable Quad SPI mode for page program Chin-Ting Kuo
2025-11-13 8:53 ` [PATCH 3/4] spi: aspeed: Use phys_addr_t for bus addresses to support 64-bit platforms Chin-Ting Kuo
2025-11-13 8:53 ` [PATCH 4/4] spi: aspeed: Add support for the AST2700 SPI controller Chin-Ting Kuo
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=20251113-reroute-backlit-b2e1d1b6dc04@spud \
--to=conor@kernel.org \
--cc=BMC-SW@aspeedtech.com \
--cc=andrew@codeconstruct.com.au \
--cc=broonie@kernel.org \
--cc=chin-ting_kuo@aspeedtech.com \
--cc=clg@kaod.org \
--cc=clg@redhat.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=openbmc@lists.ozlabs.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