From: Cédric Le Goater <clg@kaod.org>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH] ARM: dts: aspeed-g4: Add all flash chips
Date: Thu, 5 Sep 2019 08:45:06 +0200 [thread overview]
Message-ID: <6348d0f1-6e2e-cae6-7f76-996825de0527@kaod.org> (raw)
In-Reply-To: <d9805fa2-db79-457b-a166-7c84e1608128@www.fastmail.com>
On 05/09/2019 02:33, Andrew Jeffery wrote:
>
>
> On Thu, 5 Sep 2019, at 09:32, Joel Stanley wrote:
>> The FMC supports five chip selects, so describe the five possible flash
>> chips.
>>
>> Signed-off-by: Joel Stanley <joel@jms.id.au>
>> ---
>> arch/arm/boot/dts/aspeed-g4.dtsi | 20 ++++++++++++++++++++
>> 1 file changed, 20 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/aspeed-g4.dtsi b/arch/arm/boot/dts/aspeed-g4.dtsi
>> index e465cda40fe7..dffb595d30e4 100644
>> --- a/arch/arm/boot/dts/aspeed-g4.dtsi
>> +++ b/arch/arm/boot/dts/aspeed-g4.dtsi
>> @@ -67,6 +67,26 @@
>> compatible = "jedec,spi-nor";
>> status = "disabled";
>> };
>> + flash at 1 {
>> + reg = < 1 >;
>> + compatible = "jedec,spi-nor";
>> + status = "disabled";
>> + };
>> + flash at 2 {
>> + reg = < 2 >;
>> + compatible = "jedec,spi-nor";
>> + status = "disabled";
>> + };
>> + flash at 3 {
>> + reg = < 3 >;
>> + compatible = "jedec,spi-nor";
>> + status = "disabled";
>> + };
>> + flash at 4 {
>> + reg = < 4 >;
>> + compatible = "jedec,spi-nor";
>> + status = "disabled";
>> + };
>
> The FMC supports parallel NOR and NAND interfaces too, but so far no-one has
> cared for these options, so if they ever do we'll fix it then.
New Aspeed SoCs only have SPI support. So I don't think the other interfaces
were ever used.
C.
>
> Reviewed-by: Andrew Jeffery <andrew@aj.id.au>
>
next prev parent reply other threads:[~2019-09-05 6:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 0:02 [PATCH] ARM: dts: aspeed-g4: Add all flash chips Joel Stanley
2019-09-05 0:33 ` Andrew Jeffery
2019-09-05 6:45 ` Cédric Le Goater [this message]
2019-09-05 6:43 ` Cédric Le Goater
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=6348d0f1-6e2e-cae6-7f76-996825de0527@kaod.org \
--to=clg@kaod.org \
--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