From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 1/5] mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform
Date: Mon, 7 Oct 2013 21:59:32 -0400 [thread overview]
Message-ID: <52536704.8020904@ti.com> (raw)
In-Reply-To: <1381194371.7979.191.camel@snotra.buserror.net>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/07/2013 09:06 PM, Scott Wood wrote:
> On Sat, 2013-10-05 at 06:11 +0000, Gupta, Pekon wrote:
>> Hi,
>> Please see the replies inline..
>>
>>> From: Scott Wood [mailto:scottwood at freescale.com]
>>>> On Mon, 2013-09-30 at 19:43 +0530, Pekon Gupta wrote:
>>>> +Platform specific options
>>>> +=========================
>>>> +
>>>> + CONFIG_NAND_OMAP_ECCSCHEME
>>>> + On OMAP platforms, this specifies NAND ECC scheme.
>>>> + 1 - HAM1_SW 1-bit Hamming code using software library
>>>> + (for legacy devices only)
>>>> + 2 - HAM1_HW 1-bit Hamming code using GPMC hardware engine
>>>> + (for legacy devices only)
>>>> + 3 - BCH4_SW 4-bit BCH code (unsupported)
>>>> + 4 - BCH4_HW 4-bit BCH code (unsupported)
>>>> + 5 - BCH8_SW 8-bit BCH code with
>>>> + - ecc calculation using GPMC hardware engine,
>>>> + - error detection using software library.
>>>> + - requires CONFIG_BCH to enable software BCH
>>> library
>>>> + (For legacy device which do not have ELM h/w
>>> engine)
>>>> + 6 - BCH8_HW 8-bit BCH code with
>>>> + - ecc calculation using GPMC hardware engine,
>>>> + - error detection using ELM hardware engine.
>>>
>>> You should document the symbols, not the numbers that happen to be
>>> assigned to them.
>>>
>> Sorry din't get you. This is based on your below feedback
>> http://lists.denx.de/pipermail/u-boot/2013-September/162773.html
>>
>> Example: "6 - BCH8_HW" means 8-bit BCH ECC scheme using h/w engine.
>> It is this number is what user needs to specify in include/configs/*.h
>> Any other internal symbol like "OMAP_ECC_BCH8_CODE_SW" should
>> not be exposed to user, user-interface should remain constant.
>
> I disagree. The user should specify OMAP_ECC_BCH8_CODE_SW. It's more
> greppable, and it's more likely that the number will change than that
> the name will.
I agree with Scott, enum (if it's not already one) and use the name so
it's clear what you're picking.
- --
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBAgAGBQJSU2cEAAoJENk4IS6UOR1WnOQP/30AInl+d0QVU6QHq+DsGC/q
Wh/yfXbN/EkWVPEvpASS5gftTSd+UjLSzUSWca+TcQxUVdzD64H1u4j8An2cSwJp
vQuX1QZzMWA+g6D+u75BKMs/cIXb6rwX9A5is5R/k5cU4mew+ecLmBeRLcTENfpM
+ROD7XfSJsXYff+dLhpOeVWC6ELzjgmHWajoqpdZNefrMtsrRHOeLd9ccbqYxoNZ
Td56vwMYfk8f+BBRmGlFRdAf+xN+9ssou1CipK6E/H0QHnexRkuPINRdmPD4/p0o
yP+opvOUq8XMYiO76HOGb37tMJvjgziEcZUy4S3Q0gbhRlC9EXz1D0qxs6ti1EFs
9M/Wsl8bsKx4rgdf12hj8iebFxvTdT1lXejJGNk9ThHqsHE0pl+K1cyouZ/GL0NA
sk/UCPe7DL3RIAtkUy+pLT7A3nOKIhqJY1kTsPN24qTF7UVlatWov6C33d42jDzp
YH5CkdP1FRffkRj1in1ex0CiVB/3h3SuI4kA+hceWdx0rGYRT/PRKQA3qSulU1p4
lx3jtzt07fSflPdeX9PxW5k9CqAmXut4rw5USU1OAdpRKANzp1FPXcKXjEVd2uQ1
zkfgUB4MeR6xs6HE6q5xBbaaRhy9zJX415ZG10NtKUXCrVBIoif51EQQmlvehgcy
ufn39bBOmsjkXYXzJI8W
=tQHU
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2013-10-08 1:59 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-30 14:13 [U-Boot] [PATCH v7 0/5] mtd: nand: omap: optimize and clean-up of OMAP NAND driver Pekon Gupta
2013-09-30 14:13 ` [U-Boot] [PATCH v7 1/5] mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform Pekon Gupta
2013-09-30 15:11 ` Stefan Roese
2013-10-04 22:30 ` Scott Wood
2013-10-05 6:11 ` Gupta, Pekon
2013-10-08 1:06 ` Scott Wood
2013-10-08 1:59 ` Tom Rini [this message]
2013-10-08 5:30 ` Gupta, Pekon
2013-10-08 16:52 ` Scott Wood
2013-10-08 17:38 ` Scott Wood
2013-10-08 19:06 ` Gupta, Pekon
2013-09-30 14:13 ` [U-Boot] [PATCH v7 2/5] mtd: nand: omap: optimize chip->ecc.hwctl() for H/W ECC schemes Pekon Gupta
2013-09-30 14:13 ` [U-Boot] [PATCH v7 3/5] mtd: nand: omap: optimize chip->ecc.calculate() " Pekon Gupta
2013-10-08 17:28 ` Scott Wood
2013-09-30 14:13 ` [U-Boot] [PATCH v7 4/5] mtd: nand: omap: optimized chip->ecc.correct() " Pekon Gupta
2013-10-08 17:35 ` Scott Wood
2013-09-30 14:13 ` [U-Boot] [PATCH v7 5/5] board/ti/am335x/README: update for NAND boot Pekon Gupta
2013-10-04 20:19 ` [U-Boot] [PATCH v7 0/5] mtd: nand: omap: optimize and clean-up of OMAP NAND driver Gupta, Pekon
2013-10-17 17:24 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2013-09-30 17:53 [U-Boot] [PATCH v7 1/5] mtd: nand: omap: enable BCH ECC scheme using ELM for generic platform Gupta, Pekon
2013-09-30 18:31 ` Gupta, Pekon
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=52536704.8020904@ti.com \
--to=trini@ti.com \
--cc=u-boot@lists.denx.de \
/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