[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <1398175396-7560-1-git-send-email-grmoore@altera.com>
Date: Tue, 22 Apr 2014 09:03:15 -0500
From: Graham Moore <grmoore@...era.com>
To: <ggrahammoore@...il.com>
CC: David Woodhouse <dwmw2@...radead.org>,
Brian Norris <computersforpeace@...il.com>,
ZY - marex <marex@...x.de>,
Artem Bityutskiy <artem.bityutskiy@...ux.intel.com>,
Sourav Poddar <sourav.poddar@...com>,
Sascha Hauer <s.hauer@...gutronix.de>,
Geert Uytterhoeven <geert+renesas@...ux-m68k.org>,
Jingoo Han <jg1.han@...sung.com>,
Insop Song <insop.song@...nspeed.com>,
Graham Moore <grmoore@...era.com>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
Alan Tull <atull@...era.com>,
Dinh Nguyen <dinguyen@...era.com>,
Yves Vandervennet <rocket.yvanderv@...il.com>
Subject: [PATCH V3] Add support for flag status register on Micron chips.
I rebased this patch onto the l2-mtd spinor branch. Sorry it took so long, had to patch for our SoC, corporate network issues, etc.
The change to read the flag status register is, afaik, specific to Micron chips. So, imo, the fsr ready check should be in the m25p80.c file. But I put it into the spin-nor.c file, because I need to call the read_sr() function, which is declared static in spi-nor.c.
I *could* duplicate the read_sr code and put the wait_till_fsr_ready in m25p80, but I'm pretty sure that would attract some critique :) Suggestions most welcome.
I also used n25q512ax3 for the id because there are two part numbers for the 512MB part with FSR, n25q512a13 and n25qa512a83. The '83' version has a reset line.
Graham Moore (1):
Add support for flag status register on Micron chips.
drivers/mtd/spi-nor/spi-nor.c | 51 +++++++++++++++++++++++++++++++++++++++++
include/linux/mtd/spi-nor.h | 4 ++++
2 files changed, 55 insertions(+)
--
1.7.9.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists