From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Boris Brezillon <boris.brezillon@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: Re: [PATCH] mtd: rawnand: Allow selection of ECC byte ordering at runtime
Date: Sun, 23 Sep 2018 13:30:19 +0200 [thread overview]
Message-ID: <20180923133019.1c6c9cbc@xps13> (raw)
In-Reply-To: <20180904142328.26577-1-boris.brezillon@bootlin.com>
Hi Boris,
Boris Brezillon <boris.brezillon@bootlin.com> wrote on Tue, 4 Sep 2018
16:23:28 +0200:
> Currently, the selection of ECC byte ordering for software hamming is
> done at compilation time, which doesn't make sense when ECC byte
> calculation is done in hardware and byte ordering is forced by the
> hardware engine.
> In this case, only the correction is done and software and we want to
^ in
> force the byte-ordering no matter the value of CONFIG_MTD_NAND_ECC_SMC.
>
> This is typically the case for the FSMC (Smart Media ordering), TMIO and
> TXX9NDFMC (regular byte ordering) blocks.
>
> For all other use cases (pure software implementation, SM FTL and
> nandecctest), we keep selecting the byte ordering based on the
> CONFIG_MTD_NAND_ECC_SMC value. It might not be ideal for SM FTL (I'd
> expect Smart Media ordering to be employed by the Smart Media FTL), but
> this option doesn't seem to be enabled in the existing _defconfig, so
> I can't tell setting sm_order to true is the right choice.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> ---
Applied to nand/next with the above typo corrected.
Thanks,
Miquèl
prev parent reply other threads:[~2018-09-23 11:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 14:23 [PATCH] mtd: rawnand: Allow selection of ECC byte ordering at runtime Boris Brezillon
2018-09-23 11:30 ` Miquel Raynal [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=20180923133019.1c6c9cbc@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linus.walleij@linaro.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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