[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200217155213.5594-1-frieder.schrempf@kontron.de>
Date: Mon, 17 Feb 2020 15:53:43 +0000
From: Schrempf Frieder <frieder.schrempf@...tron.de>
To: Boris Brezillon <bbrezillon@...nel.org>,
Schrempf Frieder <frieder.schrempf@...tron.de>,
Jeff Kletsky <git-commits@...ycomm.com>,
liaoweixiong <liaoweixiong@...winnertech.com>,
Miquel Raynal <miquel.raynal@...tlin.com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
"Richard Weinberger" <richard@....at>
Subject: [PATCH v2 0/3] mtd: spinand: Fix reading and writing of bad block
markers
From: Frieder Schrempf <frieder.schrempf@...tron.de>
We were pointed to the issue of bad block markers not being saved to flash on
one of our boards with SPI NAND flash. After a bit of investigation it seems
like there are two overlapping bugs in the original framework that cause silent
failure when writing a bad block marker.
This set contains fixes for both of these issues and one more fix (patch 2) that
should not affect the actual behavior of the driver.
Changes in v2:
* Patch 1: Incorporate small improvements proposed by Boris
* Patch 1: Add Boris' R-b tag
* Patch 2: Add Boris' R-b tag
* Patch 3: Instead of waiting for the erase operation to finish,
just don't do an erase at all, as it is not needed.
Frieder Schrempf (3):
mtd: spinand: Stop using spinand->oobbuf for buffering bad block
markers
mtd: spinand: Explicitly use MTD_OPS_RAW to write the bad block marker
to OOB
mtd: spinand: Don not erase the block before writing a bad block
marker
drivers/mtd/nand/spi/core.c | 18 ++++++++----------
1 file changed, 8 insertions(+), 10 deletions(-)
--
2.17.1
Powered by blists - more mailing lists