From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] Atmel Dataflash: convert to C struct accessors
Date: Wed, 9 Jun 2010 17:33:43 -0400 [thread overview]
Message-ID: <201006091733.44984.vapier@gentoo.org> (raw)
In-Reply-To: <20100609090626.7a1c67ca@surf>
On Wednesday, June 09, 2010 03:06:26 Thomas Petazzoni wrote:
> On Tue, 8 Jun 2010 15:20:57 -0400 Mike Frysinger wrote:
> > speaking historically, the dataflash code absolutely has its place.
> > it existed long before the SPI flash framework. but i'm looking
> > forward only now.
>
> Yes, of course, understood.
>
> However, the Dataflash aren't normal SPI flash, they don't have the
> same opcodes. For example, drivers/mtd/spi/spi_flash.c assumes that it
> can probe the "ID code" of the SPI flash by sending the CMD_READ_ID
> (0x9F) command (in spi_flash_probe()). This works for SPI flashes, but
> not for Dataflashes. The identification of Dataflashes takes place with
> command GET_STATUS (0xD7) in drivers/mtd/at45.c, which has a different
> return value than the 0x9F command of SPI flashes. Am I missing
> something ?
i see drivers/mtd/spi/atmel.c with all the same IDs as drivers/mtd/dataflash.c
so presumably it works. i also vaguely recall having tested one or two myself
with the SPI flash subsystem.
according to the datasheet for the AT45DB642D, 0x9F is the "get the ID code"
while 0xDF is the "get flash status". i dont see how you can get the flash id
info out of the flash status register. perhaps you're confusing the code
bases ?
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100609/9b4217e4/attachment.pgp
next prev parent reply other threads:[~2010-06-09 21:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 16:04 [U-Boot] [PATCH 0/4] Support for board Calao USB A9263 Thomas Petazzoni
2010-06-02 16:04 ` [U-Boot] [PATCH 1/4] Atmel Dataflash: convert to C struct accessors Thomas Petazzoni
2010-06-02 16:04 ` [U-Boot] [PATCH 2/4] at91_spi: remove register offsets Thomas Petazzoni
2010-06-02 16:04 ` [U-Boot] [PATCH 3/4] at91sam9263: add new style definition for SPI0_BASE Thomas Petazzoni
2010-06-02 16:04 ` [U-Boot] [PATCH 4/4] Support for Calao USB A9263 board based on AT91SAM9263 CPU Thomas Petazzoni
2010-06-07 12:40 ` [U-Boot] [PATCH 0/4] Support for board Calao USB A9263 Tom Rix
2010-06-07 21:56 ` [U-Boot] [PATCH 0/4] Calao USB-A9263 v2 Thomas Petazzoni
2010-06-07 21:56 ` [U-Boot] [PATCH 1/4] Atmel Dataflash: convert to C struct accessors Thomas Petazzoni
2010-06-07 22:52 ` Mike Frysinger
2010-06-08 12:24 ` Thomas Petazzoni
2010-06-08 19:20 ` Mike Frysinger
2010-06-09 7:06 ` Thomas Petazzoni
2010-06-09 21:33 ` Mike Frysinger [this message]
2010-06-07 21:56 ` [U-Boot] [PATCH 2/4] at91_spi: remove register offsets Thomas Petazzoni
2010-06-07 21:56 ` [U-Boot] [PATCH 3/4] Add new style definition for SPI0_BASE Thomas Petazzoni
2010-06-07 21:56 ` [U-Boot] [PATCH 4/4] Support for Calao USB A9263 board based on AT91SAM9263 CPU Thomas Petazzoni
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=201006091733.44984.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=u-boot@lists.denx.de \
/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