From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Mason Yang <masonccyang@mxic.com.tw>
Cc: 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 v3] mtd: rawnand: Add support for Macronix NAND randomizer
Date: Mon, 7 Oct 2019 10:18:47 +0200 [thread overview]
Message-ID: <20191007101847.7fcfcfc7@xps13> (raw)
In-Reply-To: <1567676229-23414-1-git-send-email-masonccyang@mxic.com.tw>
Hi Mason,
Mason Yang <masonccyang@mxic.com.tw> wrote on Thu, 5 Sep 2019 17:37:09
+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 subpage accesses prohibited and more time
> period is needed in program operation and entering deep power-down mode.
> i.e., tPROG 300us to 340us(randomizer enabled)
>
> For more high-reliability concern, if subpage write not available with
> hardware ECC and then to enable randomizer is recommended by default.
> Driver checks byte 167 of Vendor Blocks in ONFI parameter page table
> to see if this high-reliability function is supported. By adding a new
> specific DT property in children nodes to enable randomizer function.
> i.e.,
>
> nand: nand-controller@unit-address {
>
> nand@0 {
> reg = <0>;
> mxic,enable-randomizer-otp;
> };
> };
>
> --
> changelog
> v3:
> To enable randomizer by specific DT property in children nodes,
> mxic,enable-randomizer-otp;
>
> v2:
> To enable randomizer by checking chip options NAND_NO_SUBPAGE_WRITE
>
> v1:
> To enable randomizer by sys-fs
>
> Signed-off-by: Mason Yang <masonccyang@mxic.com.tw>
> ---
> drivers/mtd/nand/raw/nand_macronix.c | 64 ++++++++++++++++++++++++++++++++++++
As long as you modify bindings, you should write a separate patch to
update the documentation and get it acked by Rob Herring.
> 1 file changed, 64 insertions(+)
>
> diff --git a/drivers/mtd/nand/raw/nand_macronix.c b/drivers/mtd/nand/raw/nand_macronix.c
> index 58511ae..d5df09a 100644
> --- a/drivers/mtd/nand/raw/nand_macronix.c
> +++ b/drivers/mtd/nand/raw/nand_macronix.c
> @@ -11,6 +11,13 @@
> #define MACRONIX_READ_RETRY_BIT BIT(0)
> #define MACRONIX_NUM_READ_RETRY_MODES 6
>
> +#define MACRONIX_RANDOMIZER_BIT BIT(1)
> +#define ONFI_FEATURE_ADDR_MXIC_RANDOMIZER 0xB0
> +#define MACRONIX_RANDOMIZER_ENPGM BIT(0)
> +#define MACRONIX_RANDOMIZER_RANDEN BIT(1)
> +#define MACRONIX_RANDOMIZER_RANDOPT BIT(2)
> +#define MACRONIX_RANDOMIZER_MODE_EXIT ~MACRONIX_RANDOMIZER_ENPGM
I would rather prefer a
#define ...RANDOMISER_MODE_ENTER (ENGPM | RANDEN | RANDOPT)
#define ...RANDOMISER_MODE_EXIT (RANDEN | RANDOPT)
> +
> struct nand_onfi_vendor_macronix {
> u8 reserved;
> u8 reliability_func;
> @@ -29,15 +36,72 @@ static int macronix_nand_setup_read_retry(struct nand_chip *chip, int mode)
> return nand_set_features(chip, ONFI_FEATURE_ADDR_READ_RETRY, feature);
> }
>
> +static void macronix_nand_randomizer_check_enable(struct nand_chip *chip)
You should return something and check it from the calling function.
> +{
> + u8 feature[ONFI_SUBFEATURE_PARAM_LEN];
> + int ret;
> +
> + ret = nand_get_features(chip, ONFI_FEATURE_ADDR_MXIC_RANDOMIZER,
> + feature);
> + if (feature[0]) {
> + pr_info("Macronix NAND randomizer enabled:0x%x\n", feature[0]);
> + return;
> + }
> +
> + feature[0] = MACRONIX_RANDOMIZER_ENPGM | MACRONIX_RANDOMIZER_RANDEN |
> + MACRONIX_RANDOMIZER_RANDOPT;
> + ret = nand_set_features(chip, ONFI_FEATURE_ADDR_MXIC_RANDOMIZER,
> + feature);
> + if (ret)
> + goto err;
> +
> + feature[0] = 0x0;
> + ret = nand_prog_page_op(chip, 0, 0, feature, 1);
What is this? A comment is needed.
> + if (ret)
> + goto err;
> +
> + ret = nand_get_features(chip, ONFI_FEATURE_ADDR_MXIC_RANDOMIZER,
> + feature);
> + if (ret)
> + goto err;
> +
> + feature[0] &= MACRONIX_RANDOMIZER_MODE_EXIT;
> + ret = nand_set_features(chip, ONFI_FEATURE_ADDR_MXIC_RANDOMIZER,
> + feature);
> + if (ret)
> + goto err;
> +
> + pr_info("Macronix NAND randomizer enable ok\n");
The pr_info "ok" could be dropped, the "failed" one would go in
nand_onfi_init() after a check on the return code.
Then, no more goto's.
> + return;
> +err:
> + pr_err("Macronix NAND randomizer enable failed\n");
> +}
> +
> static void macronix_nand_onfi_init(struct nand_chip *chip)
> {
> struct nand_parameters *p = &chip->parameters;
> struct nand_onfi_vendor_macronix *mxic;
> + struct device_node *dn = nand_get_flash_node(chip);
> + int rand_otp = 0;
>
> if (!p->onfi)
> return;
>
> + if (of_find_property(dn, "mxic,enable-randomizer-otp", NULL))
> + rand_otp = 1;
> +
> mxic = (struct nand_onfi_vendor_macronix *)p->onfi->vendor;
> + if (rand_otp && chip->options & NAND_NO_SUBPAGE_WRITE &&
> + mxic->reliability_func & MACRONIX_RANDOMIZER_BIT) {
> + if (p->supports_set_get_features) {
> + bitmap_set(p->set_feature_list,
> + ONFI_FEATURE_ADDR_MXIC_RANDOMIZER, 1);
> + bitmap_set(p->get_feature_list,
> + ONFI_FEATURE_ADDR_MXIC_RANDOMIZER, 1);
> + macronix_nand_randomizer_check_enable(chip);
> + }
> + }
> +
> if ((mxic->reliability_func & MACRONIX_READ_RETRY_BIT) == 0)
> return;
>
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-10-07 8:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 9:37 [PATCH v3] mtd: rawnand: Add support for Macronix NAND randomizer Mason Yang
2019-10-07 8:18 ` Miquel Raynal [this message]
2019-10-14 9:27 ` 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=20191007101847.7fcfcfc7@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=bbrezillon@kernel.org \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=frieder.schrempf@kontron.de \
--cc=juliensu@mxic.com.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=masonccyang@mxic.com.tw \
--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).