From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Brian Norris <computersforpeace@gmail.com>,
Sourav Poddar <sourav.poddar@ti.com>, Marek Vasut <marex@denx.de>,
David Woodhouse <dwmw2@infradead.org>
Cc: Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
linux-mtd@lists.infradead.org
Subject: [PATCH] mtd: m25p80: Use OPCODE_QUAD_READ_4B for 4-byte addressing
Date: Wed, 15 Jan 2014 16:48:55 +0100 [thread overview]
Message-ID: <1389800935-6468-1-git-send-email-geert@linux-m68k.org> (raw)
From: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
commit 3487a63955c34ea508bcf4ca5131ddd953876e2d ("drivers: mtd: m25p80: add
quad read support") in -next added both the 3-byte OPCODE_QUAD_READ and the
4-byte OPCODE_QUAD_READ_4B, but incorrectly uses OPCODE_QUAD_READ for both
3-byte and 4-byte addressing.
Use OPCODE_QUAD_READ_4B in the 4-byte case to fix this.
Signed-off-by: Geert Uytterhoeven <geert+renesas@linux-m68k.org>
---
drivers/mtd/devices/m25p80.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
index bf358326c335..0e9e78acc677 100644
--- a/drivers/mtd/devices/m25p80.c
+++ b/drivers/mtd/devices/m25p80.c
@@ -1258,7 +1258,7 @@ pr_info("jid = 0x%p\n", jid);
/* Dedicated 4-byte command set */
switch (flash->flash_read) {
case M25P80_QUAD:
- flash->read_opcode = OPCODE_QUAD_READ;
+ flash->read_opcode = OPCODE_QUAD_READ_4B;
break;
case M25P80_FAST:
flash->read_opcode = OPCODE_FAST_READ_4B;
--
1.7.9.5
next reply other threads:[~2014-01-15 15:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 15:48 Geert Uytterhoeven [this message]
2014-01-16 0:09 ` [PATCH] mtd: m25p80: Use OPCODE_QUAD_READ_4B for 4-byte addressing Marek Vasut
2014-01-16 21:05 ` Brian Norris
2014-01-17 2:04 ` Huang Shijie
2014-01-17 7:01 ` Brian Norris
2014-01-18 21:20 ` Jagan Teki
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=1389800935-6468-1-git-send-email-geert@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=geert+renesas@linux-m68k.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marex@denx.de \
--cc=sourav.poddar@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;
as well as URLs for NNTP newsgroup(s).