From: Kishore Kadiyala <kishorek.kadiyala@gmail.com>
To: Kishore Kadiyala <kishore.kadiyala@ti.com>
Cc: Vimal Singh <vimal.newwork@gmail.com>,
linux-omap@vger.kernel.org, linux-mtd@lists.infradead.org,
dedekind1@gmail.com
Subject: Re: [PATCH RESEND] omap : nand : fix subpage ecc issue with prefetch
Date: Wed, 11 May 2011 19:45:39 +0530 [thread overview]
Message-ID: <BANLkTi=OenjvSObPg8=ynwhCH8CEyUeMqA@mail.gmail.com> (raw)
In-Reply-To: <1304950899-26009-1-git-send-email-kishore.kadiyala@ti.com>
Oops forgot to CC stable@kernel.org, posting again without any changes.
Regards,
Kishore
On Mon, May 9, 2011 at 7:51 PM, Kishore Kadiyala
<kishore.kadiyala@ti.com> wrote:
> When reading/writing a subpage (When HW ECC is not available/enabled)
> for number of bytes not aligned to 4, the mis-aligned bytes are handled
> first (by cpu copy method) before enabling the Prefetch engine to/from
> 'p'(start of buffer 'buf'). Then it reads/writes rest of the bytes with
> the help of Prefetch engine, if available, or again using cpu copy method.
> Currently, reading/writing of rest of bytes, is not done correctly since
> its trying to read/write again to/from begining of buffer 'buf',
> overwriting the mis-aligned bytes.
>
> Read & write using prefetch engine got broken in commit '2c01946c'.
> We never hit a scenario of not getting 'gpmc_prefetch_enable' call
> success. So, problem did not get caught up.
>
> Signed-off-by: Kishore Kadiyala <kishore.kadiyala@ti.com>
> Signed-off-by: Vimal Singh <vimal.newwork@gmail.com>
> Reported-by: Bryan DE FARIA <bdefaria@adeneo-embedded.com>
> ---
> drivers/mtd/nand/omap2.c | 12 +++++-------
> 1 files changed, 5 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/mtd/nand/omap2.c b/drivers/mtd/nand/omap2.c
> index da9a351..2c8040f 100644
> --- a/drivers/mtd/nand/omap2.c
> +++ b/drivers/mtd/nand/omap2.c
> @@ -263,11 +263,10 @@ static void omap_read_buf_pref(struct mtd_info *mtd, u_char *buf, int len)
> if (ret) {
> /* PFPW engine is busy, use cpu copy method */
> if (info->nand.options & NAND_BUSWIDTH_16)
> - omap_read_buf16(mtd, buf, len);
> + omap_read_buf16(mtd, (u_char *)p, len);
> else
> - omap_read_buf8(mtd, buf, len);
> + omap_read_buf8(mtd, (u_char *)p, len);
> } else {
> - p = (u32 *) buf;
> do {
> r_count = gpmc_read_status(GPMC_PREFETCH_FIFO_CNT);
> r_count = r_count >> 2;
> @@ -293,7 +292,7 @@ static void omap_write_buf_pref(struct mtd_info *mtd,
> struct omap_nand_info, mtd);
> uint32_t w_count = 0;
> int i = 0, ret = 0;
> - u16 *p;
> + u16 *p = (u16 *)buf;
> unsigned long tim, limit;
>
> /* take care of subpage writes */
> @@ -309,11 +308,10 @@ static void omap_write_buf_pref(struct mtd_info *mtd,
> if (ret) {
> /* PFPW engine is busy, use cpu copy method */
> if (info->nand.options & NAND_BUSWIDTH_16)
> - omap_write_buf16(mtd, buf, len);
> + omap_write_buf16(mtd, (u_char *)p, len);
> else
> - omap_write_buf8(mtd, buf, len);
> + omap_write_buf8(mtd, (u_char *)p, len);
> } else {
> - p = (u16 *) buf;
> while (len) {
> w_count = gpmc_read_status(GPMC_PREFETCH_FIFO_CNT);
> w_count = w_count >> 1;
> --
> 1.7.4.1
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2011-05-11 14:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 14:21 [PATCH RESEND] omap : nand : fix subpage ecc issue with prefetch Kishore Kadiyala
2011-05-11 14:15 ` Kishore Kadiyala [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-11 14:24 Kishore Kadiyala
2011-05-11 14:54 ` Greg KH
2011-05-11 15:37 ` Kishore Kadiyala
2011-05-11 15:47 Kishore Kadiyala
2011-05-12 12:56 ` Artem Bityutskiy
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='BANLkTi=OenjvSObPg8=ynwhCH8CEyUeMqA@mail.gmail.com' \
--to=kishorek.kadiyala@gmail.com \
--cc=dedekind1@gmail.com \
--cc=kishore.kadiyala@ti.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=vimal.newwork@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 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).