From: Graham Moore <grmoore@altera.com> To: <ggrahammoore@gmail.com> Cc: David Woodhouse <dwmw2@infradead.org>, Brian Norris <computersforpeace@gmail.com>, ZY - marex <marex@denx.de>, Artem Bityutskiy <artem.bityutskiy@linux.intel.com>, Sourav Poddar <sourav.poddar@ti.com>, Sascha Hauer <s.hauer@pengutronix.de>, Geert Uytterhoeven <geert+renesas@linux-m68k.org>, Jingoo Han <jg1.han@samsung.com>, Insop Song <insop.song@gainspeed.com>, Graham Moore <grmoore@altera.com>, <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>, Alan Tull <atull@altera.com>, Dinh Nguyen <dinguyen@altera.com>, Yves Vandervennet <rocket.yvanderv@gmail.com> Subject: [PATCH V3] Add support for flag status register on Micron chips. Date: Tue, 22 Apr 2014 09:03:15 -0500 [thread overview] Message-ID: <1398175396-7560-1-git-send-email-grmoore@altera.com> (raw) 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
WARNING: multiple messages have this Message-ID (diff)
From: Graham Moore <grmoore@altera.com> To: <ggrahammoore@gmail.com> Cc: ZY - marex <marex@denx.de>, Geert Uytterhoeven <geert+renesas@linux-m68k.org>, Graham Moore <grmoore@altera.com>, Artem Bityutskiy <artem.bityutskiy@linux.intel.com>, Sascha Hauer <s.hauer@pengutronix.de>, Jingoo Han <jg1.han@samsung.com>, linux-kernel@vger.kernel.org, Yves Vandervennet <rocket.yvanderv@gmail.com>, linux-mtd@lists.infradead.org, Insop Song <insop.song@gainspeed.com>, Alan Tull <atull@altera.com>, Sourav Poddar <sourav.poddar@ti.com>, Brian Norris <computersforpeace@gmail.com>, David Woodhouse <dwmw2@infradead.org>, Dinh Nguyen <dinguyen@altera.com> Subject: [PATCH V3] Add support for flag status register on Micron chips. Date: Tue, 22 Apr 2014 09:03:15 -0500 [thread overview] Message-ID: <1398175396-7560-1-git-send-email-grmoore@altera.com> (raw) 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
next reply other threads:[~2014-04-22 14:04 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-22 14:03 Graham Moore [this message] 2014-04-22 14:03 ` [PATCH V3] Add support for flag status register on Micron chips Graham Moore 2014-04-22 14:03 ` Graham Moore 2014-04-22 14:03 ` Graham Moore 2014-04-22 16:55 ` Marek Vasut 2014-04-22 16:55 ` Marek Vasut 2014-04-22 18:48 ` Graham Moore 2014-04-22 18:48 ` Graham Moore 2014-04-22 18:58 ` Marek Vasut 2014-04-22 18:58 ` Marek Vasut 2014-04-25 4:47 ` Huang Shijie 2014-04-25 4:47 ` Huang Shijie 2014-04-25 15:50 ` Marek Vasut 2014-04-25 15:50 ` Marek Vasut 2014-04-22 18:45 ` Gerhard Sittig 2014-04-22 18:45 ` Gerhard Sittig 2014-04-22 19:17 ` Graham Moore 2014-04-22 19:17 ` Graham Moore 2014-04-25 1:34 ` Huang Shijie 2014-04-25 1:34 ` Huang Shijie 2014-04-25 2:42 ` Marek Vasut 2014-04-25 2:42 ` Marek Vasut 2014-04-25 1:52 ` Huang Shijie 2014-04-25 1:52 ` Huang Shijie 2014-04-25 22:12 ` Marek Vasut 2014-04-25 22:12 ` Marek Vasut 2014-04-26 3:10 ` Huang Shijie 2014-04-26 3:10 ` Huang Shijie 2014-04-28 5:06 ` Marek Vasut 2014-04-28 5:06 ` Marek Vasut 2014-04-28 7:06 ` Huang Shijie 2014-04-28 7:06 ` Huang Shijie 2014-04-28 14:22 ` Graham Moore 2014-04-28 14:22 ` Graham Moore 2014-04-28 15:37 ` Huang Shijie 2014-04-28 15:37 ` Huang Shijie 2014-07-12 2:07 ` Brian Norris 2014-07-12 2:07 ` Brian Norris 2014-04-25 1:54 ` Huang Shijie 2014-04-25 1:54 ` Huang Shijie
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=1398175396-7560-1-git-send-email-grmoore@altera.com \ --to=grmoore@altera.com \ --cc=artem.bityutskiy@linux.intel.com \ --cc=atull@altera.com \ --cc=computersforpeace@gmail.com \ --cc=dinguyen@altera.com \ --cc=dwmw2@infradead.org \ --cc=geert+renesas@linux-m68k.org \ --cc=ggrahammoore@gmail.com \ --cc=insop.song@gainspeed.com \ --cc=jg1.han@samsung.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=marex@denx.de \ --cc=rocket.yvanderv@gmail.com \ --cc=s.hauer@pengutronix.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.