From: Ivan Djelic <ivan.djelic@parrot.com>
To: Tony Lindgren <tony@atomide.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH v2] ARM: OMAP3: gpmc: add BCH ecc api and modes
Date: Wed, 25 Apr 2012 20:28:36 +0200 [thread overview]
Message-ID: <20120425182836.GA17023@parrot.com> (raw)
In-Reply-To: <20120425170313.GW3739@atomide.com>
Hi Tony,
Thanks for the review,
On Wed, Apr 25, 2012 at 06:03:14PM +0100, Tony Lindgren wrote:
(...)
> > #define GPMC_ECC1_RESULT 0x200
> > +#define GPMC_ECC_BCH_RESULT_0 0x240
>
> Can you please add a comment here saying something like:
>
> #define GPMC_ECC_BCH_RESULT_0 0x240 /* Not available on omap2 */
OK sure.
> > + /* check if ecc module is in use */
> > + if (gpmc_ecc_used != -EINVAL)
> > + return -EINVAL;
> > + /*
> > + * FIXME: some OMAP3 revisions have a hardware bug which prevents
> > + * the 4-bit BCH mode from working properly. Such revisions could be
> > + * detected and rejected here.
> > + */
>
> This should then be disabled to avoid corruption. Maybe only allow it
> initially on omaps that have been tested? And for omap2 it should return
> error for sure.
OK I'll add a check.
>
> Or do you know the broken omap3 versions?
Well, I was hoping that someone from linux-omap could tell me :)
I found this HW ECC feature table in
http://processors.wiki.ti.com/index.php/Raw_NAND_ECC:
1b 4b 8b
---------------------------
OMAP35x YES NO YES
AM35x YES YES YES
AM/DM37x YES YES YES
and other wiki pages confirmed that 4-bit mode is not supported on all OMAP35xx chips.
OTOH, I know from TI support that 4-bit mode is at least supported on
OMAP3630 ES1.x (x >= 1).
So, a conservative approach would be to reject 4-bit mode on all chips but
omap3630 with rev >= 1.1. Other revisions/chips could be added later if they are
confirmed to work; what do you think ?
> Also, should you first request this feature in case multiple drivers
> need to share it?
According to TI documentation (OMAP36xx ES1.x TRM, §10.1.4, GPMC functional diagram),
the GPMC ECC engines (Hamming and BCH) are dedicated to NAND access only; therefore
I believe the mtd driver is the only potential user of this feature.
Also, the existing Hamming ecc API does not perform any request; or did I miss
something? If I need to perform the request, is there an existing api to do so?
Thanks,
--
Ivan
next prev parent reply other threads:[~2012-04-25 18:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 18:43 [PATCH v2] ARM: OMAP3: gpmc: add BCH ecc api and modes Ivan Djelic
2012-04-25 17:03 ` Tony Lindgren
2012-04-25 18:28 ` Ivan Djelic [this message]
2012-04-25 20:57 ` Tony Lindgren
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=20120425182836.GA17023@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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).