All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Ivan Djelic <ivan.djelic@parrot.com>,
	linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ARM: OMAP3: gpmc: add BCH ecc api and modes
Date: Wed, 25 Apr 2012 17:48:49 +0300	[thread overview]
Message-ID: <1335365341.6356.5.camel@koala> (raw)
In-Reply-To: <1334652536-4442-1-git-send-email-ivan.djelic@parrot.com>

[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]

On Tue, 2012-04-17 at 10:48 +0200, Ivan Djelic wrote:
> This patch adds a simple BCH ecc computation api, similar to the
> existing Hamming ecc api. It is intended to be used by the MTD layer.
> It implements the following features:
> 
> - support 4-bit and 8-bit ecc computation
> - do not protect user bytes in spare area, only data area is protected
> - ecc for an erased NAND page (0xFFs) is also a sequence of 0xFFs
> 
> This last feature is obtained by adding a constant polynomial to
> the hardware computed ecc. It allows to correct bitflips in blank pages
> and is extremely useful to support filesystems such as UBIFS, which expect
> erased pages to contain only 0xFFs.
> 
> This api has been tested on an OMAP3630 board.
> 
> Signed-off-by: Ivan Djelic <ivan.djelic@parrot.com>

Hi Tony,

what do you think about merging this patch? This is the enabler for
making UBIFS actually usable on OMAP platforms which use BCH ECC. There
are 2 other MTD patches which depend on this - so I wonder if it is
easier to merge this one via the MTD tree, providing it has your/others'
ack(s).

Thanks!

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
	Ivan Djelic <ivan.djelic@parrot.com>
Subject: Re: [PATCH] ARM: OMAP3: gpmc: add BCH ecc api and modes
Date: Wed, 25 Apr 2012 17:48:49 +0300	[thread overview]
Message-ID: <1335365341.6356.5.camel@koala> (raw)
In-Reply-To: <1334652536-4442-1-git-send-email-ivan.djelic@parrot.com>

[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]

On Tue, 2012-04-17 at 10:48 +0200, Ivan Djelic wrote:
> This patch adds a simple BCH ecc computation api, similar to the
> existing Hamming ecc api. It is intended to be used by the MTD layer.
> It implements the following features:
> 
> - support 4-bit and 8-bit ecc computation
> - do not protect user bytes in spare area, only data area is protected
> - ecc for an erased NAND page (0xFFs) is also a sequence of 0xFFs
> 
> This last feature is obtained by adding a constant polynomial to
> the hardware computed ecc. It allows to correct bitflips in blank pages
> and is extremely useful to support filesystems such as UBIFS, which expect
> erased pages to contain only 0xFFs.
> 
> This api has been tested on an OMAP3630 board.
> 
> Signed-off-by: Ivan Djelic <ivan.djelic@parrot.com>

Hi Tony,

what do you think about merging this patch? This is the enabler for
making UBIFS actually usable on OMAP platforms which use BCH ECC. There
are 2 other MTD patches which depend on this - so I wonder if it is
easier to merge this one via the MTD tree, providing it has your/others'
ack(s).

Thanks!

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-04-25 14:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  8:48 [PATCH] ARM: OMAP3: gpmc: add BCH ecc api and modes Ivan Djelic
2012-04-25 14:48 ` Artem Bityutskiy [this message]
2012-04-25 14:48   ` Artem Bityutskiy
2012-04-25 15:23   ` Tony Lindgren
2012-04-25 15:23     ` Tony Lindgren
2012-04-25 15:44     ` Artem Bityutskiy
2012-04-25 15:44       ` Artem Bityutskiy
2012-04-25 15:58       ` Tony Lindgren
2012-04-25 15:58         ` Tony Lindgren
2012-04-25 16:49         ` Tony Lindgren
2012-04-25 16:49           ` 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=1335365341.6356.5.camel@koala \
    --to=dedekind1@gmail.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.