From: Tudor Ambarus <tudor.ambarus@microchip.com>
To: <marek.vasut@gmail.com>, <cyrille.pitchen@microchip.com>,
<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
<boris.brezillon@bootlin.com>, <richard@nod.at>
Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<nicolas.ferre@microchip.com>, <Cristian.Birsan@microchip.com>,
Tudor Ambarus <tudor.ambarus@microchip.com>
Subject: [PATCH] add support to non-uniform SFDP SPI NOR flash memories
Date: Fri, 8 Jun 2018 16:48:17 +0300 [thread overview]
Message-ID: <20180608134818.21387-1-tudor.ambarus@microchip.com> (raw)
The commit message became wall-of-text, my feeling is that I heavily
reworked the code so I changed the author. If someone thinks differently,
please say and I'll change back to the initial authorship. What I've done:
- minimize the amount of erase() calls by using the best sequence of erase
type commands depending on alignment.
- build the list of best fitted erase commands to be executed once we
validate that the erase can be performed.
- add improvements on how the erase map is handled. The regions are
consecutive in the address space, walk through the regions incrementally.
- speed up finding the best erase type command. Order erase types by
size, iterate them from the biggest to the smallest and stop when best
fitted command is found.
- determine at init if there are erase types that can erase the entire
memory
- fix the erase size in overlaid regions. S25FS512S states that 'if a sector
erase command is applied to a 256KB range that is overlaid by 4KB secors,
the overlaid 4kB sectors are not affected by the erase'
Backward compatibility test done on MX25L25673G.
Changes since RFC PATCH:
- build a list of erase commands to be executed once we validate
that the erase can be performed
- fix walking through the address space in overlaid regions
- drop wall-of-text description commit message, change author
Tudor Ambarus (1):
mtd: spi-nor: add support to non-uniform SFDP SPI NOR flash memories
drivers/mtd/spi-nor/spi-nor.c | 357 ++++++++++++++++++++++++++++++++++++++++--
include/linux/mtd/spi-nor.h | 108 +++++++++++++
2 files changed, 451 insertions(+), 14 deletions(-)
--
2.9.4
next reply other threads:[~2018-06-08 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-08 13:48 Tudor Ambarus [this message]
2018-06-08 13:48 ` [PATCH] mtd: spi-nor: add support to non-uniform SFDP SPI NOR flash memories Tudor Ambarus
2018-06-24 20:00 ` Boris Brezillon
2018-07-09 14:48 ` Tudor Ambarus
2018-06-08 13:54 ` [PATCH] " Cyrille Pitchen
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=20180608134818.21387-1-tudor.ambarus@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Cristian.Birsan@microchip.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@microchip.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=nicolas.ferre@microchip.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