From: masonccyang@mxic.com.tw
To: "Miquel Raynal" <miquel.raynal@bootlin.com>
Cc: kstewart@linuxfoundation.org, vigneshr@ti.com,
bbrezillon@kernel.org, juliensu@mxic.com.tw, richard@nod.at,
linux-kernel@vger.kernel.org, frieder.schrempf@kontron.de,
marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
tglx@linutronix.de, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: Re: [PATCH] Add support for Macronix NAND randomizer
Date: Mon, 26 Aug 2019 17:24:41 +0800 [thread overview]
Message-ID: <OFBC7B2DED.A4E37205-ON48258462.00332180-48258462.0033B2E6@mxic.com.tw> (raw)
In-Reply-To: <20190826092344.7b23ede1@xps13>
Hi Miquel,
>
> Re: [PATCH] Add support for Macronix NAND randomizer
>
> Hi Mason,
>
> masonccyang@mxic.com.tw wrote on Mon, 26 Aug 2019 10:52:31 +0800:
>
> > Hi Miquel,
> > >
> > > Mason Yang <masonccyang@mxic.com.tw> wrote on Tue, 20 Aug 2019
13:53:48
> > > +0800:
> > >
> > > > Macronix NANDs support randomizer operation for user data
scrambled,
> > > > which can be enabled with a SET_FEATURE.
> > > >
> > > > User data written to the NAND device without randomizer is still
> > readable
> > > > after randomizer function enabled.
> > > > The penalty of randomizer are NOP = 1 instead of NOP = 4 and more
time
> > period
> > >
> > > please don't use 'NOP' here, use 'subpage accesses' instead,
otherwise
> > > people might not understand what it means while it has a real
impact.
> > >
> >
> > okay, understood.
> > will fix it by next submitting.
> >
> > > > is needed in program operation and entering deep power-down mode.
> > > > i.e., tPROG 300us to 340us(randomizer enabled)
> > > >
> > > > If subpage write not available with hardware ECC, for example,
> > > > NAND chip options NAND_NO_SUBPAGE_WRITE be set in driver and
> > > > randomizer function is recommended for high-reliability.
> > > > Driver checks byte 167 of Vendor Blocks in ONFI parameter page
table
> > > > to see if this high-reliability function is supported.
> > > >
> > >
> > > You did not flagged this patch as a v2 and forgot about the
changelog.
> >
> > will fix, thank you.
> >
> > > You did not listen to our comments in the last version neither. I
was
> > > open to a solution with a specific DT property for warned users but
I
> > > don't see it coming.
> >
> > Sorry I missed the previous version of "read-retry and randomizer
support"
> > patch.
> > Specific DT property is a good method to control it.
> >
> > For more high-reliability concern, randomizer is recommended to enable
by
> > default,
> > but sub-page write is not allowed when randomizer is enabled.
> >
> > Since most of HW ECC did not support sub-page write and we think
driver to
> > check
> > chip options flags is another simple and good way to enable
randomizer.
>
> Sorry but this is wrong. Several controllers and NAND chips support
> subpages. And changing now the behavior with such chips would entirely
> break the concerned setups (see Boris answer about UBI complaining if
> the subpage size changes).
okay, I see.
thanks for your information.
I will patch it based on your comments in the last version.
>
> Thanks,
> Miquèl
best regards,
Mason
CONFIDENTIALITY NOTE:
This e-mail and any attachments may contain confidential information
and/or personal data, which is protected by applicable laws. Please be
reminded that duplication, disclosure, distribution, or use of this e-mail
(and/or its attachments) or any part thereof is prohibited. If you receive
this e-mail in error, please notify us immediately and delete this mail as
well as its attachment(s) from your system. In addition, please be
informed that collection, processing, and/or use of personal data is
prohibited unless expressly permitted by personal data protection laws.
Thank you for your attention and cooperation.
Macronix International Co., Ltd.
=====================================================================
============================================================================
CONFIDENTIALITY NOTE:
This e-mail and any attachments may contain confidential information and/or personal data, which is protected by applicable laws. Please be reminded that duplication, disclosure, distribution, or use of this e-mail (and/or its attachments) or any part thereof is prohibited. If you receive this e-mail in error, please notify us immediately and delete this mail as well as its attachment(s) from your system. In addition, please be informed that collection, processing, and/or use of personal data is prohibited unless expressly permitted by personal data protection laws. Thank you for your attention and cooperation.
Macronix International Co., Ltd.
=====================================================================
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-26 9:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-20 5:53 [PATCH] Add support for Macronix NAND randomizer Mason Yang
2019-08-24 11:03 ` Miquel Raynal
2019-08-26 2:52 ` masonccyang
2019-08-26 7:23 ` Miquel Raynal
2019-08-26 9:24 ` masonccyang [this message]
2019-08-29 9:07 ` masonccyang
2019-08-30 9:51 ` Miquel Raynal
2019-09-02 6:53 ` masonccyang
2019-09-02 7:05 ` Richard Weinberger
2019-09-02 7:39 ` masonccyang
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=OFBC7B2DED.A4E37205-ON48258462.00332180-48258462.0033B2E6@mxic.com.tw \
--to=masonccyang@mxic.com.tw \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@kontron.de \
--cc=juliensu@mxic.com.tw \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=vigneshr@ti.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).