From: Han Xu <han.xu@freescale.com>
To: Michal Suchanek <hramrach@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Mark Brown <broonie@kernel.org>,
Boris Brezillon <boris.brezillon@free-electrons.com>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Rafal Milecki <zajec5@gmail.com>, Jagan Teki <jteki@openedev.com>,
"Andrew F. Davis" <afd@ti.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Gabor Juhos <juhosg@openwrt.org>, Bean Huo <beanhuo@micron.com>,
Furquan Shaikh <furquan@google.com>,
<linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>,
<linux-spi@vger.kernel.org>
Subject: Re: [PATCH v6 06/10] mtd: spi-nor: simplify write loop
Date: Tue, 15 Dec 2015 14:22:17 -0600 [thread overview]
Message-ID: <20151215202216.GA11742@chopperman.am.freescale.net> (raw)
In-Reply-To: <2236d87ad516f118f58eb5df232d441f970c4499.1449052427.git.hramrach@gmail.com>
On Wed, Dec 02, 2015 at 10:38:20AM +0000, Michal Suchanek wrote:
> The spi-nor write loop assumes that what is passed to the hardware
> driver write() is what gets written.
>
> When write() writes less than page size at once data is dropped on the
> floor. Check the amount of data writen and exit if it does not match
> requested amount.
>
> Signed-off-by: Michal Suchanek <hramrach@gmail.com>
>
> ---
>
> - add warning when writing incomplete pages
> - refuse to continue writing when full page was not written
> ---
> drivers/mtd/spi-nor/spi-nor.c | 58 +++++++++++++++++++------------------------
> 1 file changed, 25 insertions(+), 33 deletions(-)
>
> diff --git a/drivers/mtd/spi-nor/spi-nor.c b/drivers/mtd/spi-nor/spi-nor.c
> index 3d02803..115c123 100644
> --- a/drivers/mtd/spi-nor/spi-nor.c
> +++ b/drivers/mtd/spi-nor/spi-nor.c
> @@ -1005,8 +1005,8 @@ static int spi_nor_write(struct mtd_info *mtd, loff_t to, size_t len,
> size_t *retlen, const u_char *buf)
> {
> struct spi_nor *nor = mtd_to_spi_nor(mtd);
> - u32 page_offset, page_size, i;
> - int ret;
> + size_t page_offset, page_remain, i;
> + ssize_t ret;
>
> dev_dbg(nor->dev, "to 0x%08x, len %zd\n", (u32)to, len);
>
> @@ -1014,45 +1014,37 @@ static int spi_nor_write(struct mtd_info *mtd, loff_t to, size_t len,
> if (ret)
> return ret;
>
> - write_enable(nor);
> -
> - page_offset = to & (nor->page_size - 1);
> + for (i = 0; i < len; ) {
> + ssize_t written;
>
> - /* do all the bytes fit onto one page? */
> - if (page_offset + len <= nor->page_size) {
> - ret = nor->write(nor, to, len, buf);
> - if (ret < 0)
> - goto write_err;
> - *retlen += ret;
> - } else {
> + page_offset = to & (nor->page_size - 1);
> + WARN_ONCE(page_offset,
> + "Writing at offset %zu into a NOR page. Writing partial pages may decrease reliability and increase wear of NOR flash.",
> + page_offset);
> /* the size of data remaining on the first page */
> - page_size = nor->page_size - page_offset;
> - ret = nor->write(nor, to, page_size, buf);
> + page_remain = min_t(size_t,
> + nor->page_size - page_offset, len - i);
> +
> + write_enable(nor);
> + ret = nor->write(nor, to + i, page_remain, buf + i);
Previous implementation was trying to write nor->page_size byte data in
each loop, except the first and last loop, if possible. But this change
may write only (nor->page_size - page_offset) in each loop, for the
worst case, if page_offset equals nor->page_size -1, it writes byte by
byte.
> if (ret < 0)
> goto write_err;
> - *retlen += ret;
> -
> - /* write everything in nor->page_size chunks */
> - for (i = ret; i < len; ) {
> - page_size = len - i;
> - if (page_size > nor->page_size)
> - page_size = nor->page_size;
> -
> - ret = spi_nor_wait_till_ready(nor);
> - if (ret)
> - goto write_err;
> + written = ret;
>
> - write_enable(nor);
> -
> - ret = nor->write(nor, to + i, page_size, buf + i);
> - if (ret < 0)
> - goto write_err;
> - *retlen += ret;
> - i += ret;
> + ret = spi_nor_wait_till_ready(nor);
> + if (ret)
> + goto write_err;
> + *retlen += written;
> + i += written;
> + if (written != page_remain) {
> + dev_err(nor->dev,
> + "While writing %zu bytes written %zd bytes\n",
> + page_remain, written);
> + ret = -EIO;
> + goto write_err;
> }
> }
>
> - ret = spi_nor_wait_till_ready(nor);
> write_err:
> spi_nor_unlock_and_unprep(nor, SPI_NOR_OPS_WRITE);
> return ret;
> --
> 2.6.2
>
--
Best Regards,
Han "Allen" Xu
next prev parent reply other threads:[~2015-12-15 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1449052427.git.hramrach@gmail.com>
[not found] ` <ad10a42f8c502b9b91fcba05b3e46c42663e1141.1449052427.git.hramrach@gmail.com>
2015-12-02 21:06 ` [PATCH v6 03/10] mtd: fsl-quadspi: return amount of data read/written or error Han Xu
2015-12-02 23:07 ` Brian Norris
[not found] ` <2236d87ad516f118f58eb5df232d441f970c4499.1449052427.git.hramrach@gmail.com>
2015-12-15 20:22 ` Han Xu [this message]
2015-12-15 23:45 ` [PATCH v6 06/10] mtd: spi-nor: simplify write loop Michal Suchanek
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=20151215202216.GA11742@chopperman.am.freescale.net \
--to=han.xu@freescale.com \
--cc=afd@ti.com \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@free-electrons.com \
--cc=broonie@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=furquan@google.com \
--cc=hkallweit1@gmail.com \
--cc=hramrach@gmail.com \
--cc=javier@osg.samsung.com \
--cc=jteki@openedev.com \
--cc=juhosg@openwrt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=zajec5@gmail.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
all inboxes | Powered by JetHome®