From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/7] ARM: dts: Fix the DNS-313 flash compatible
Date: Sun, 6 May 2018 15:43:49 +0200 [thread overview]
Message-ID: <20180506134352.2637-5-linus.walleij@linaro.org> (raw)
In-Reply-To: <20180506134352.2637-1-linus.walleij@linaro.org>
The flash on the DNS-313 needs to be probed as JEDEC, it does
not conform to the common CFI standard.
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
---
arch/arm/boot/dts/gemini-dlink-dns-313.dts | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/gemini-dlink-dns-313.dts b/arch/arm/boot/dts/gemini-dlink-dns-313.dts
index 2d9aa5ba8320..d865cde8ed12 100644
--- a/arch/arm/boot/dts/gemini-dlink-dns-313.dts
+++ b/arch/arm/boot/dts/gemini-dlink-dns-313.dts
@@ -157,8 +157,12 @@
soc {
flash at 30000000 {
+ /*
+ * This is a Eon EN29LV400AB 512 KiB flash with
+ * three partitions.
+ */
+ compatible = "cortina,gemini-flash", "jedec-flash";
status = "okay";
- /* 512KB of flash */
reg = <0x30000000 0x00080000>;
/*
--
2.17.0
next prev parent reply other threads:[~2018-05-06 13:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-06 13:43 [PATCH 0/7] Gemini DTS updates Linus Walleij
2018-05-06 13:43 ` [PATCH 1/7] ARM: dts: gemini: Fix "debounce-interval" property misspelling Linus Walleij
2018-05-06 13:43 ` [PATCH 2/7] ARM: dtd: Set DNS-313 LEDs to use better triggers Linus Walleij
2018-05-06 13:43 ` [PATCH 3/7] ARM: dts: Set DNS-685 " Linus Walleij
2018-05-06 13:43 ` Linus Walleij [this message]
2018-05-06 13:43 ` [PATCH 5/7] ARM: dts: Fix bootargs for Gemini D-Link devices Linus Walleij
2018-05-06 13:43 ` [PATCH 6/7] ARM: dts: Add second ATA to NAS4220B Linus Walleij
2018-05-06 13:43 ` [PATCH 7/7] ARM: dts: Fix DTC warnings Linus Walleij
2018-05-08 10:37 ` Robin Murphy
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=20180506134352.2637-5-linus.walleij@linaro.org \
--to=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).