linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sheng Yong <shengyong1@huawei.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: <dwmw2@infradead.org>, <richard@nod.at>,
	<linux-mtd@lists.infradead.org>,
	Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: [RFC PATCH 0/5] MTD: nandsim: simulate multiple chips
Date: Mon, 23 Nov 2015 09:53:29 +0800	[thread overview]
Message-ID: <56527199.9080306@huawei.com> (raw)
In-Reply-To: <20151120190630.GV64635@google.com>



On 11/21/2015 3:06 AM, Brian Norris wrote:
> On Wed, Aug 05, 2015 at 08:55:49AM +0000, Sheng Yong wrote:
>> Hi, folks,
>>
>> These patchset add a new module parameter, numchips, to supports to
>> simulate NAND flash with multiple chips.
>>
>> This simulation helps to test and improve generic NAND driver on
>> multiple chips NAND flash.
> 
Hi, Brian

Thanks for your reply.
> I'm not quite sure I understand the real purpose of this feature. Seems
> like you're just testing different corners of the internals of the NAND
> framework, but not actually exposing anything new that an MTD user would
> care about. Care to clarify?
> 
Sorry for I didn't put much explaination in the last mail. Test for multi-
chips NAND flash detection is not the main purpose. The main purpose of doing
this is that if nand_scan_ident() fails to read the first chip, it will not
continue to try to setup the other chips, while if we make an appropriate
partition strategy, the other chips may contains data we expect.

So we think it may worth trying to skip the faulty chips and continue scanning
the other chips and setup the partitions that are not on the faulty chips. We
are not quiet sure if it's correct to do so, but we think simulating a multi-
chip NAND is the first step.

thanks,
Sheng

> Brian
> 
>> MTD test (except for mtd_nandbiterr) are passed. 
>>
>> Thanks,
>> Sheng
>>
>> Sheng Yong (5):
>>   MTD: nandsim: add numchips module parameter
>>   MTD: nandsim: fix column address size of large page
>>   MTD: nandsim: fix page address size
>>   MTD: nandsim: add ADJUST_ROW() to find the real page number
>>   MTD: nandsim: extent outprint messages
>>
>>  drivers/mtd/nand/nandsim.c | 632 +++++++++++++++++++++++++++------------------
>>  1 file changed, 377 insertions(+), 255 deletions(-)
>>
>> -- 
>> 1.8.3.4
>>
> 
> 

      reply	other threads:[~2015-11-23  1:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-05  8:55 [RFC PATCH 0/5] MTD: nandsim: simulate multiple chips Sheng Yong
2015-08-05  8:55 ` [RFC PATCH 1/5] MTD: nandsim: add numchips module parameter Sheng Yong
2015-08-05  8:55 ` [RFC PATCH 2/5] MTD: nandsim: fix column address size of large page Sheng Yong
2015-08-05  8:55 ` [RFC PATCH 3/5] MTD: nandsim: fix page address size Sheng Yong
2015-08-05  8:55 ` [RFC PATCH 4/5] MTD: nandsim: add ADJUST_ROW() to find the real page number Sheng Yong
2015-08-05  8:55 ` [RFC PATCH 5/5] MTD: nandsim: extent outprint messages Sheng Yong
2015-11-20 19:06 ` [RFC PATCH 0/5] MTD: nandsim: simulate multiple chips Brian Norris
2015-11-23  1:53   ` Sheng Yong [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=56527199.9080306@huawei.com \
    --to=shengyong1@huawei.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).