From: <Tudor.Ambarus@microchip.com>
To: <alexander.sverdlin@nokia.com>, <marek.vasut@gmail.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>
Subject: Re: [PATCH] mtd: spi-nor: fix erase_type array to indicate current map conf
Date: Fri, 23 Nov 2018 12:39:44 +0000 [thread overview]
Message-ID: <70ac7381-bea8-8f1a-a03b-bc03478dbd7c@microchip.com> (raw)
In-Reply-To: <679e7fb8-f424-b72c-ac8a-315926080ede@nokia.com>
Hi, Alexander,
On 11/23/2018 01:33 PM, Sverdlin, Alexander (Nokia - DE/Ulm) wrote:
> So erasesize is back to the value before non-uniform support patches,
> partitions are not made read only any more, but actual write or
> erase still fails.
How does the erase fail?
What map configuration is selected? Where are the hybrid blocks, at the bottom
or at the top of the address space?
Does the erase fail even when address is aligned with 64k and the size multiple
of 64k? Does the following fail?
$ mtd_debug erase /dev/your_mtd 0 65536
The non-uniform erase will fail if it can't select a sequence of commands that
can erase the entire requested chunk.
Cheers,
ta
prev parent reply other threads:[~2018-11-23 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 12:36 [PATCH] mtd: spi-nor: fix erase_type array to indicate current map conf Tudor.Ambarus
2018-11-22 12:38 ` Tudor.Ambarus
2018-11-22 14:56 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-22 15:01 ` Tudor.Ambarus
2018-11-22 16:14 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-22 16:22 ` Tudor.Ambarus
2018-11-23 9:42 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-23 10:17 ` Boris Brezillon
2018-11-23 10:29 ` Boris Brezillon
2018-11-23 10:32 ` Tudor.Ambarus
2018-11-23 11:33 ` Sverdlin, Alexander (Nokia - DE/Ulm)
2018-11-23 12:39 ` Tudor.Ambarus [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=70ac7381-bea8-8f1a-a03b-bc03478dbd7c@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=alexander.sverdlin@nokia.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.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