From: Ivan Djelic <ivan.djelic@parrot.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: Jan Weitzel <J.Weitzel@phytec.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: nand: omap: add support for hardware BCH ecc
Date: Fri, 20 Apr 2012 13:22:52 +0200 [thread overview]
Message-ID: <20120420112252.GA12151@parrot.com> (raw)
In-Reply-To: <CANOLnOOjrZEbPByOD3EQTZ3vn2ZO0SMdyYo1oME_NLRyYciXUQ@mail.gmail.com>
On Fri, Apr 20, 2012 at 12:12:27PM +0100, Grazvydas Ignotas wrote:
> On Fri, Apr 20, 2012 at 12:48 PM, Ivan Djelic <ivan.djelic@parrot.com> wrote:
> > Hello,
> > This patch provides hardware NAND BCH ecc support for OMAP3 boards.
> > It depends on the following patches:
> >
> > new GPMC BCH api (linux-omap):
> > http://lists.infradead.org/pipermail/linux-mtd/2012-April/040757.html
> >
> > race condition fix in OMAP mtd driver:
> > http://lists.infradead.org/pipermail/linux-mtd/2012-April/040724.html
>
> I don't have this one in my mailbox (looked up through the archives),
> so commenting about it here. What about just dropping omap_wait()
> instead? I think gpmc_nand_read(.. GPMC_NAND_DATA) is equivalent to
> ordinary data read, knowing that omap_wait() looks like a duplicate of
> generic nand_wait(), just without LED support.
Yes, I agree; I also comtemplated getting rid of omap_wait(), but I needed this
quick fix out of the way to submit my BCH patch. But you're right, and there
are plenty other things to improve in omap2.c (look at omap_compare_ecc() for
a good example).
BR,
--
Ivan
WARNING: multiple messages have this Message-ID (diff)
From: Ivan Djelic <ivan.djelic@parrot.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Jan Weitzel <J.Weitzel@phytec.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: [PATCH] mtd: nand: omap: add support for hardware BCH ecc
Date: Fri, 20 Apr 2012 13:22:52 +0200 [thread overview]
Message-ID: <20120420112252.GA12151@parrot.com> (raw)
In-Reply-To: <CANOLnOOjrZEbPByOD3EQTZ3vn2ZO0SMdyYo1oME_NLRyYciXUQ@mail.gmail.com>
On Fri, Apr 20, 2012 at 12:12:27PM +0100, Grazvydas Ignotas wrote:
> On Fri, Apr 20, 2012 at 12:48 PM, Ivan Djelic <ivan.djelic@parrot.com> wrote:
> > Hello,
> > This patch provides hardware NAND BCH ecc support for OMAP3 boards.
> > It depends on the following patches:
> >
> > new GPMC BCH api (linux-omap):
> > http://lists.infradead.org/pipermail/linux-mtd/2012-April/040757.html
> >
> > race condition fix in OMAP mtd driver:
> > http://lists.infradead.org/pipermail/linux-mtd/2012-April/040724.html
>
> I don't have this one in my mailbox (looked up through the archives),
> so commenting about it here. What about just dropping omap_wait()
> instead? I think gpmc_nand_read(.. GPMC_NAND_DATA) is equivalent to
> ordinary data read, knowing that omap_wait() looks like a duplicate of
> generic nand_wait(), just without LED support.
Yes, I agree; I also comtemplated getting rid of omap_wait(), but I needed this
quick fix out of the way to submit my BCH patch. But you're right, and there
are plenty other things to improve in omap2.c (look at omap_compare_ecc() for
a good example).
BR,
--
Ivan
next prev parent reply other threads:[~2012-04-20 11:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 9:48 [PATCH] mtd: nand: omap: add support for hardware BCH ecc Ivan Djelic
2012-04-20 9:48 ` Ivan Djelic
2012-04-20 11:12 ` Grazvydas Ignotas
2012-04-20 11:12 ` Grazvydas Ignotas
2012-04-20 11:22 ` Ivan Djelic [this message]
2012-04-20 11:22 ` Ivan Djelic
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=20120420112252.GA12151@parrot.com \
--to=ivan.djelic@parrot.com \
--cc=J.Weitzel@phytec.de \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=notasas@gmail.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.