From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com>
Cc: Boris Brezillon <bbrezillon@kernel.org>,
Richard Weinberger <richard@nod.at>,
Marek Vasut <marek.vasut@gmail.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH 0/4] Introduce generic ONFI support
Date: Mon, 8 Apr 2019 14:10:23 +0200 [thread overview]
Message-ID: <20190408141023.6c57199f@xps13> (raw)
In-Reply-To: <MN2PR08MB5951DD5B4DC318D44E01206DB82C0@MN2PR08MB5951.namprd08.prod.outlook.com>
Hi Shivamurthy,
"Shivamurthy Shastri (sshivamurthy)" <sshivamurthy@micron.com> wrote on
Mon, 8 Apr 2019 11:48:08 +0000:
> Hi,
>
> Just a gentle reminder that I'd like some feedback on these patches.
Yes, this is definitely in my queue.
>
> Thanks,
> Shiva
>
> > Subject: [PATCH 0/4] Introduce generic ONFI support
> >
> > Current support to ONFI parameter page is only for raw NAND, this patch
> > series turn ONFI support into generic. So that, other NAND devices like SPI
> > NAND can use this.
> >
> > Support to detect parameter page is enabled in SPI NAND core.
> >
> > Turned Micron SPI NAND driver to use parameter page.
> >
> > From SPI NAND side, this patch series is tested with Micron flashes
> > MT29F2G01ABXGD, MT29F4G01ABXFD, MT29F8G01ADXFD,
> > MT29F1G01ABXFD.
> >
> > I created this patch series based on mtd/next + Miquel Raynal's new series of
> > patches, as I needed some of the changes done by him.
> >
> > Shivamurthy Shastri (4):
> > mtd: rawnand: Turn the ONFI support to generic
> > mtd: nand: Move ONFI code into nand/ directory
> > mtd: spinand: Enabled support to detect parameter page
> > mtd: spinand: micron: Support for new Micron SPI NAND flashes
> >
> > drivers/mtd/nand/Makefile | 2 +-
> > drivers/mtd/nand/onfi.c | 169 +++++++++++++++++
> > drivers/mtd/nand/raw/Makefile | 1 -
> > drivers/mtd/nand/raw/internals.h | 6 +-
> > drivers/mtd/nand/raw/nand_base.c | 236 +++++++++++++++++++++--
> > drivers/mtd/nand/raw/nand_onfi.c | 312 -------------------------------
> > drivers/mtd/nand/spi/core.c | 113 ++++++++++-
> > drivers/mtd/nand/spi/micron.c | 109 ++++++++---
> > include/linux/mtd/nand.h | 30 +++
> > include/linux/mtd/rawnand.h | 5 +
> > include/linux/mtd/spinand.h | 5 +
> > 11 files changed, 620 insertions(+), 368 deletions(-)
> > create mode 100644 drivers/mtd/nand/onfi.c
> > delete mode 100644 drivers/mtd/nand/raw/nand_onfi.c
> >
> > --
> > 2.17.1
>
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2019-04-08 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-26 10:51 [PATCH 0/4] Introduce generic ONFI support Shivamurthy Shastri (sshivamurthy)
2019-04-08 11:48 ` Shivamurthy Shastri (sshivamurthy)
2019-04-08 12:10 ` Miquel Raynal [this message]
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=20190408141023.6c57199f@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=boris.brezillon@collabora.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
--cc=sshivamurthy@micron.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).