All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: Adrian Hunter <hunter.programmer@gmail.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND: read-while-load (known problem)
Date: Tue, 09 Jan 2007 01:14:42 +0000 (GMT)	[thread overview]
Message-ID: <21965393.307811168305282593.JavaMail.weblogic@ep_ml29> (raw)

Ah, I see

please try this patch. In my test program. It passed.

Thank you,
Kyungmin Park

--

@@ -747,6 +819,14 @@ static int onenand_read(struct mtd_info *mtd, loff_t from, size_t len,
                from += thislen;
                if (read + thislen < len) {
                        this->command(mtd, ONENAND_CMD_READ, from, mtd->writesize);
+                       /*
+                        * Chip boundary handling in DDP
+                        * Now we issued chip 1 read and pointed chip 1
+                        * bufferam so we have to point chip 0 bufferam.
+                        */
+                       if (this->device_id & ONENAND_DEVICE_IS_DDP &&
+                           from == (this->chipsize >> 1))
+                               this->write_word(0, this->base + ONENAND_REG_START_ADDRESS2);
                        ONENAND_SET_PREV_BUFFERRAM(this);
                }
                /* While load is going, read from last bufferRAM */




------- Original Message -------
Sender : Adrian Hunter<hunter.programmer@gmail.com> 
Date   : Jan 08, 2007 18:29
Title  : Re: OneNAND: read-while-load (known problem)

On 1/8/07, Kyungmin Park <kyungmin.park@samsung.com> wrote:
> Hi Adrian,
>
> > Do you think there could be a problem with onenand_check_bufferram also?
>
> No, onenand_check_bufferram & onenand_update_bufferram is right.
>

What I meant was this:

1. Read page x from chip 0. It goes to dataRAM 0 in chip 0
2. Read page y from chip 1. It goes to dataRAM 1 in chip 1
3. Read page x from chip 0. Now the read incorrectly comes from
dataRAM 0 in chip 1 because that was the last chip selected.



             reply	other threads:[~2007-01-09  1:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-09  1:14 Kyungmin Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-01-08  8:13 OneNAND: read-while-load (known problem) Kyungmin Park
2007-01-08  9:29 ` Adrian Hunter
2007-01-08 14:41   ` Adrian Hunter
2007-01-08  3:37 Kyungmin Park
2007-01-08  7:47 ` Adrian Hunter

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=21965393.307811168305282593.JavaMail.weblogic@ep_ml29 \
    --to=kyungmin.park@samsung.com \
    --cc=hunter.programmer@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    /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.