From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Zoltan Szubbocsev (zszubbocsev)" <zszubbocsev@micron.com>
Cc: Boris Brezillon <bbrezillon@kernel.org>,
"Bean Huo (beanhuo)" <beanhuo@micron.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Richard Weinberger <richard@nod.at>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [EXT] Re: [PATCH V1] mtd: core: Micron SLC NAND filling block
Date: Wed, 19 Dec 2018 15:17:51 +0100 [thread overview]
Message-ID: <20181219151751.74931b39@xps13> (raw)
In-Reply-To: <SN6PR08MB502421AE43E6824C3CC5C1E4CBBE0@SN6PR08MB5024.namprd08.prod.outlook.com>
Hi Zoltan,
"Zoltan Szubbocsev (zszubbocsev)" <zszubbocsev@micron.com> wrote on
Wed, 19 Dec 2018 13:59:49 +0000:
> Boris,
>
> Are there non UBI/UBIFS cases?
> Can you please be specific?
UBI is one user of MTD.
What about direct accesses to MTD devices? Squashfs?
In any case, I don't think it is exaggerated to say that Linux has been
built on "layering". This issue is NAND chip specific, hence must be
handled at the NAND core level. In the NAND erase path I would like to
see a call to a vendor specific hook that:
1/ checks if the part is affected by comparing its ID to a list,
2/ if yes, checks if the block must be filled before erasing.
The logic of 1/ and 2/ should probably reside in
drivers/mtd/nand/raw/nand_micron.c
Thanks,
Miquèl
next prev parent reply other threads:[~2018-12-19 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 11:03 [PATCH V1] mtd: core: Micron SLC NAND filling block Bean Huo (beanhuo)
2018-12-19 13:17 ` Boris Brezillon
2018-12-19 13:59 ` [EXT] " Zoltan Szubbocsev (zszubbocsev)
2018-12-19 14:17 ` Miquel Raynal [this message]
2018-12-19 17:19 ` Bean Huo (beanhuo)
2018-12-19 18:31 ` Richard Weinberger
2018-12-19 18:46 ` Boris Brezillon
2018-12-19 14:27 ` Richard Weinberger
2018-12-19 18:11 ` [EXT] " Bean Huo (beanhuo)
2018-12-19 18:28 ` Richard Weinberger
2018-12-19 18:44 ` Boris Brezillon
2018-12-19 22:29 ` Thomas Gleixner
2019-01-02 13:34 ` Bean Huo (beanhuo)
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=20181219151751.74931b39@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=beanhuo@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=zszubbocsev@micron.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