From: "Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com>
To: Boris Brezillon <bbrezillon@kernel.org>,
Miquel Raynal <miquel.raynal@bootlin.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: Chuanhong Guo <gch981213@gmail.com>,
Richard Weinberger <richard@nod.at>,
Schrempf Frieder <frieder.schrempf@kontron.De>,
Marek Vasut <marek.vasut@gmail.com>,
Frieder Schrempf <frieder.schrempf@exceet.de>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
"Bean Huo \(beanhuo\)" <beanhuo@micron.com>
Subject: [PATCH 0/2] Support parameter page and Redesign Micron SPI NAND
Date: Mon, 4 Feb 2019 11:17:38 +0000 [thread overview]
Message-ID: <MN2PR08MB59511A3423EA99DFAFF4628DB86D0@MN2PR08MB5951.namprd08.prod.outlook.com> (raw)
Parameter page is supported by some of the manufacturers and instead of
maintaining spinand_info structure for each flash it is better to use
the parameter page to get the flash info. As I have seen the different
datasheets, command required to access parameter page is same across the
manufacturers.
Micron SPI NAND flashes support parameter page, instead of adding 8
devices I thought it is better to re-design the code using parameter
page.
Shivamurthy Shastri (2):
mtd: spinand: Add function to read parameter page
mtd: spinand: micron: Support for all Micron SPI NAND flashes
drivers/mtd/nand/spi/core.c | 62 ++++++++++++
drivers/mtd/nand/spi/micron.c | 172 +++++++++++++++++++++++++++-------
drivers/mtd/nand/spi/micron.h | 83 ++++++++++++++++
include/linux/mtd/spinand.h | 3 +
4 files changed, 286 insertions(+), 34 deletions(-)
create mode 100644 drivers/mtd/nand/spi/micron.h
--
2.17.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
reply other threads:[~2019-02-04 11:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=MN2PR08MB59511A3423EA99DFAFF4628DB86D0@MN2PR08MB5951.namprd08.prod.outlook.com \
--to=sshivamurthy@micron.com \
--cc=bbrezillon@kernel.org \
--cc=beanhuo@micron.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@exceet.de \
--cc=frieder.schrempf@kontron.De \
--cc=gch981213@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
/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).