From: Brian Norris <computersforpeace@gmail.com>
To: Yanjiantao <yanjiantao@hisilicon.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Caizhiyong <caizhiyong@hisilicon.com>,
"Wanli (welly)" <welly.wan@hisilicon.com>,
Quyaxin <quyaxin@hisilicon.com>
Subject: Re: questions about [PATCH]mtd: nand: fix SCAN2NDPAGE check for BBM
Date: Tue, 13 Oct 2015 10:53:18 -0700 [thread overview]
Message-ID: <20151013175318.GY107187@google.com> (raw)
In-Reply-To: <A5C805F07496A54EAFF48B92DEC9C1057AECB1A7@SZXEMA501-MBX.china.huawei.com>
On Tue, Oct 13, 2015 at 11:33:54AM +0000, Yanjiantao wrote:
> Dear Brian,
>
> i read the patch: " mtd: nand: fix SCAN2NDPAGE check for BBM "
> And i am confused about the markbad flows.
>
> xxxxx;
> if (chip->bbt_options & NAND_BBT_SCANLASTPAGE)
> ofs += mtd->erasesize - mtd->writesize;
>
> xxxxx;
>
> do {
> if (chip->options & NAND_BUSWIDTH_16) {
> chip->cmdfunc(mtd, NAND_CMD_READOOB,
> chip->badblockpos & 0xFE, page);
> bad = cpu_to_le16(chip->read_word(mtd));
> if (chip->badblockpos & 0x1)
> bad >>= 8;
> else
> bad &= 0xFF;
> } else {
> chip->cmdfunc(mtd, NAND_CMD_READOOB, chip->badblockpos,
> page);
> bad = chip->read_byte(mtd);
> }
>
> if (likely(chip->badblockbits == 8))
> res = bad != 0xFF;
> else
> res = hweight8(bad) < chip->badblockbits;
> ofs += mtd->writesize;
> page = (int)(ofs >> chip->page_shift) & chip->pagemask;
> i++;
> } while (!res && i < 2 && (chip->bbt_options & NAND_BBT_SCAN2NDPAGE));
> mark bad flows is the same.
>
> If I understand the patch right, then I think that:
> 1. when NAND_BBT_SCANLASTPAGE is set, markbad and checkbad on the last page only.
> 2. when NAND_BBT_SCAN2NDPAGE is set, markbad and checkbad on the 1st and 2nd page.
>
> I checked some datasheets of different manufacturers(such as SAMSUNG/HYNIX/MICRON/TOSHIBA), they claim that bad block marker is on 1st/2nd, or 1st/last, or 1st/2nd/last(for spansion).
> the checkbad method may check fail in some cases:
> for example,:
> 1. for spansion nand(bad block marker is on 1st or 2nd or last page), set NAND_BBT_SCAN2NDPAGE while badblock marker is on last page or set NAND_BBT_SCANLASTPAGE while badblock marker is on 1st/2nd page may cause badblock chech failed.
> 2. for HYNIX (H27UBG8T2CTR) nand (bad block marker is on 1st or last page), check may failed whether NAND_BBT_SCANLASTPAGE is set or not.
Are you repeating the question from here [1]? The refer to my response
here [2].
Brian
[1] http://lists.infradead.org/pipermail/linux-mtd/2015-October/062486.html
[2] http://lists.infradead.org/pipermail/linux-mtd/2015-October/062509.html
prev parent reply other threads:[~2015-10-13 17:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C3050A4DBA34F345975765E43127F10F62D61353@SZXEMA512-MBX.china.huawei.com>
2015-10-13 8:53 ` 答复: [PATCH] mtd: cmdlinepart: allow fill-up partition at any point Yanjiantao
2015-10-13 17:51 ` Brian Norris
2015-10-14 2:48 ` 答复: " Yanjiantao
2015-10-17 9:02 ` Sheng Yong
2015-10-13 11:33 ` questions about [PATCH]mtd: nand: fix SCAN2NDPAGE check for BBM Yanjiantao
2015-10-13 17:53 ` Brian Norris [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=20151013175318.GY107187@google.com \
--to=computersforpeace@gmail.com \
--cc=caizhiyong@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=quyaxin@hisilicon.com \
--cc=welly.wan@hisilicon.com \
--cc=yanjiantao@hisilicon.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;
as well as URLs for NNTP newsgroup(s).