All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Suchanek <hramrach@gmail.com>
To: David Woodhouse <dwmw2@infradead.org>,
	Brian Norris <computersforpeace@gmail.com>,
	Han Xu <han.xu@freescale.com>, "Rafał Miłecki" <zajec5@gmail.com>,
	Michal Suchanek <hramrach@gmail.com>,
	Alison Chaiken <alison_chaiken@mentor.com>,
	Huang Shijie <b32955@freescale.com>,
	Ben Hutchings <ben@decadent.org.uk>, Marek Vasut <marex@denx.de>,
	Gabor Juhos <juhosg@openwrt.org>,
	"Bean Huo 霍斌斌 \(beanhuo\)" <beanhuo@micron.com>,
	linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Subject: [PATCH 0/2] Add error checking to spi-nor read and write
Date: Tue, 28 Jul 2015 11:11:22 +0200	[thread overview]
Message-ID: <cover.1438074682.git.hramrach@gmail.com> (raw)


Hello,

I am working with half-broken SPI drivers which sometimes fail and spi-nor
completely ignores that leading to silent data corruption.

With these patches I get actual I/O errors when something fails.

Testing on different hardware would be appreciated, especially fsl-qspi.

I don't recall any comment on these patches so I am resending them separately.

Thanks

Michal

Michal Suchanek (2):
  mtd: spi-nor: rework spi nor read and write.
  mtd: spi-nor: rework write loop

 drivers/mtd/devices/m25p80.c      | 33 ++++++++++------
 drivers/mtd/spi-nor/fsl-quadspi.c | 29 +++++++-------
 drivers/mtd/spi-nor/spi-nor.c     | 79 +++++++++++++++++++++------------------
 include/linux/mtd/spi-nor.h       |  8 ++--
 4 files changed, 83 insertions(+), 66 deletions(-)

-- 
2.1.4

             reply	other threads:[~2015-07-28  9:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-28  9:11 Michal Suchanek [this message]
2015-07-28  9:23 ` [PATCH 2/2] mtd: spi-nor: rework write loop Michal Suchanek
2015-07-28  9:23 ` [PATCH 1/2] mtd: spi-nor: rework spi nor read and write Michal Suchanek
2015-07-28 18:15   ` Marek Vasut
2015-07-29  4:16     ` Michal Suchanek
2015-07-29 17:03       ` Marek Vasut

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=cover.1438074682.git.hramrach@gmail.com \
    --to=hramrach@gmail.com \
    --cc=alison_chaiken@mentor.com \
    --cc=b32955@freescale.com \
    --cc=beanhuo@micron.com \
    --cc=ben@decadent.org.uk \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=han.xu@freescale.com \
    --cc=juhosg@openwrt.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=marex@denx.de \
    --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 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.