From: Stefan Roese <sr@denx.de>
To: Pekon Gupta <pekon@ti.com>,
Brian Norris <computersforpeace@gmail.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Cc: Steven Kipisz <s-kipisz2@ti.com>,
Marek Belisko <marek.belisko@gmail.com>,
linux-mtd <linux-mtd@lists.infradead.org>,
Bacem Daassi <Bacem.Daassi@spansion.com>,
Samuel Egli <samuel.egli@siemens.com>
Subject: Re: [PATCH v2] mtd: nand: Fix problem with NAND_CMD_RNDOUT (05h-E0h)
Date: Thu, 08 May 2014 13:13:27 +0200 [thread overview]
Message-ID: <536B66D7.3000007@denx.de> (raw)
In-Reply-To: <1399372120-24089-1-git-send-email-pekon@ti.com>
On 06.05.2014 12:28, Pekon Gupta wrote:
> From: Bacem Daassi <Bacem.Daassi@spansion.com>
>
> Though the NAND_CMD_READ "Page Read" command expects the full address footprint
> (2bytes for column address + 3bytes for row address).
> But once the page is loaded into the read buffer, NAND_CMD_RNDOUT (05h-E0h) also
> called "Random Data Output" command expects to see only the column address that
> should be addressed within the already loaded page present in read buffers.
> Only 2 address cycles with ALE active should be provided between the 05h and E0h
> So expected sequence for NAND_CMD_RNDOUT is
> <05h> <column-addr-byte1> <column-address-byte2> <E0h>
>
> Though most NAND Devices mentioned above tend to work even if extra cycles of
> page-address is issued between <05h> .... <E0h> command. But some Spansion and
> Hynix devices break on this non-compliance.
> The same issue has been reported by Bacem Daassi
> http://e2e.ti.com/support/arm/sitara_arm/f/791/t/259699.aspx
>
> This patch fixes nand_command for all vendors devices as datasheet of all
> devices expect same sequence.
>
> +--------+------------------------+---------------------------------------------
> |Vendor | Datasheet/Part# | Reference
> +--------+------------------------+---------------------------------------------
> |Spansion| S34ML{01|02|04}G2 | Figure 6.12 Random Data Output In a Page
> |Micron | MT29F{16|32|64|128}G08A| Figure 47: CHANGE READ COLUMN (05h-E0h) Operation
> |Macronix| MX30LF1G08AA | Figure 10. AC Waveforms for Random Data Output
> |Toshiba | TC58NVG1S3ETAI0 | Figure Column Address Change in Read Cycle Timing Diagram (2/2)
> +--------+------------------------+---------------------------------------------
>
> Reported-by: Bacem Daassi <Bacem.Daassi@spansion.com>
> Reported-by: Marek Belisko <marek.belisko@gmail.com>
> Reported-by: Steven Kipisz <s-kipisz2@ti.com>
> Signed-off-by: Pekon Gupta <pekon@ti.com>
Looks good, so:
Reviewed-by: Stefan Roese <sr@denx.de>
Thanks,
Stefan
next prev parent reply other threads:[~2014-05-08 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-06 10:28 [PATCH v2] mtd: nand: Fix problem with NAND_CMD_RNDOUT (05h-E0h) Pekon Gupta
2014-05-08 11:13 ` Stefan Roese [this message]
2014-05-13 0:05 ` Brian Norris
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=536B66D7.3000007@denx.de \
--to=sr@denx.de \
--cc=Bacem.Daassi@spansion.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.belisko@gmail.com \
--cc=pekon@ti.com \
--cc=s-kipisz2@ti.com \
--cc=samuel.egli@siemens.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.