Skip to contentSkip to conversation

spi/atmel: add AT45DB321D support

PATCH New Mike Frysinger 5 participants 10 messages Dec 30, 2008 – Mar 19, 2009

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

From: Brad Bozarth <[email protected]>

---
 drivers/mtd/spi/atmel.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
drivers/mtd/spi/atmel.c +8 -0
index 10fcf0c..581b710 100644
@@ -52,6 +52,14 @@ to_atmel_spi_flash(struct spi_flash *flash)
 
 static const struct atmel_spi_flash_params atmel_spi_flash_table[] = {
 	{
+		.idcode1		= 0x27,
+		.l2_page_size		= 9,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 32,
+		.nr_sectors		= 32,
+		.name			= "AT45DB321D",
+	},
+	{
 		.idcode1		= 0x28,
 		.l2_page_size		= 10,
 		.pages_per_block	= 8,
Signature · 1 line
1.6.0.6
#1 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

Quoted 13 lines · Mike Frysinger

From: Brad Bozarth <[email protected]>

---
 drivers/mtd/spi/atmel.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
drivers/mtd/spi/atmel.c +0 -0
index 10fcf0c..581b710 100644

drivers/mtd/spi/atmel.c to_atmel_spi_flash(struct spi_flash *flash) · line 60

Quoted 9 lines
drivers/mtd/spi/atmel.c +6 -0
@@ -52,6 +52,14 @@ to_atmel_spi_flash(struct spi_flash *flash)
 
 static const struct atmel_spi_flash_params atmel_spi_flash_table[] = {
 	{
+		.idcode1		= 0x27,
+		.l2_page_size		= 9,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 32,
+		.nr_sectors		= 32,
+		.name			= "AT45DB321D",

the AT45DB321D is supposed to be 64 block per sector and 64 sectors

Best Regards,
J.

#2 lore raw

PATCH 1/1 mtd: add some at45 spi flash support

- AT45DB321D
- AT45DB161D
- AT45DB081D
- AT45DB041D
- AT45DB021D
- AT45DB011D

---
 drivers/mtd/spi/atmel.c |   48 +++++++++++++++++++++++++++++++++++++++++++++++
 1 files changed, 48 insertions(+), 0 deletions(-)
drivers/mtd/spi/atmel.c +48 -0
index 10fcf0c..129475a 100644
@@ -52,6 +52,54 @@ to_atmel_spi_flash(struct spi_flash *flash)
 
 static const struct atmel_spi_flash_params atmel_spi_flash_table[] = {
 	{
+		.idcode1		= 0x22,
+		.l2_page_size		= 8,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 16,
+		.nr_sectors		= 4,
+		.name			= "AT45DB011D",
+	},
+	{
+		.idcode1		= 0x23,
+		.l2_page_size		= 8,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 16,
+		.nr_sectors		= 8,
+		.name			= "AT45DB021D",
+	},
+	{
+		.idcode1		= 0x24,
+		.l2_page_size		= 8,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 32,
+		.nr_sectors		= 8,
+		.name			= "AT45DB041D",
+	},
+	{
+		.idcode1		= 0x25,
+		.l2_page_size		= 8,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 32,
+		.nr_sectors		= 16,
+		.name			= "AT45DB081D",
+	},
+	{
+		.idcode1		= 0x26,
+		.l2_page_size		= 9,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 32,
+		.nr_sectors		= 16,
+		.name			= "AT45DB161D",
+	},
+	{
+		.idcode1		= 0x27,
+		.l2_page_size		= 9,
+		.pages_per_block	= 8,
+		.blocks_per_sector	= 64,
+		.nr_sectors		= 64,
+		.name			= "AT45DB321D",
+	},
+	{
 		.idcode1		= 0x28,
 		.l2_page_size		= 10,
 		.pages_per_block	= 8,
Signature · 1 line
1.5.6.5
#3 lore raw

PATCH 1/1 mtd: add some at45 spi flash support

Quoted 8 lines · On Sunday 04 January 2009 01:44:07 Jean-Christophe PLAGNIOL-VILLARD wrote:

- AT45DB321D
- AT45DB161D
- AT45DB081D
- AT45DB041D
- AT45DB021D
- AT45DB011D

whatever happened to this patch ? it isnt in mainline, i dont know of a "mtd" or "spi" git tree, and it should apply cleanly still ...

it shouldnt cause any regressions considering the existing atmel driver has all of 1 id in it today
-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/20090319/0c1229e7/attachment.pgp

#4 lore raw

PATCH 1/1 mtd: add some at45 spi flash support

Quoted 8 lines · Mike Frysinger
Quoted 7 lines · On Sunday 04 January 2009 01:44:07 Jean-Christophe PLAGNIOL-VILLARD wrote:

- AT45DB321D
- AT45DB161D
- AT45DB081D
- AT45DB041D
- AT45DB021D
- AT45DB011D

Quoted 7 lines
Quoted 1 line

whatever happened to this patch ? it isnt in mainline, i dont know of a "mtd" or "spi" git tree, and it should apply cleanly still ...

it shouldnt cause any regressions considering the existing atmel driver has all of 1 id in it today

Normally it's still apply but it's still not in mainline

Best Regards,
J.

#5 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

In reply to Jean-Christophe PLAGNIOL-VILLARD

Hmm... looking in the datasheet I have, it says:
Flexible Erase Options
? Page Erase (512 Bytes)
? Block Erase (4 Kbytes)
? Sector Erase (64 Kbytes)
? Chip Erase (32 Mbits)

which would indicate a third combo, different from mine and yours :) --- 16 blocks/sector and 64 sectors... The code only does page based so far, so I didn't catch this.

-brad

Quoted 28 lines · Jean-Christophe PLAGNIOL-VILLARD
Quoted 13 lines · Mike Frysinger

From: Brad Bozarth <[email protected]>

---
 drivers/mtd/spi/atmel.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
drivers/mtd/spi/atmel.c +0 -0
index 10fcf0c..581b710 100644

drivers/mtd/spi/atmel.c to_atmel_spi_flash(struct spi_flash *flash) · line 60

Quoted 9 lines
drivers/mtd/spi/atmel.c +6 -0
@@ -52,6 +52,14 @@ to_atmel_spi_flash(struct spi_flash *flash)
 
 static const struct atmel_spi_flash_params atmel_spi_flash_table[] = {
      {
+             .idcode1                = 0x27,
+             .l2_page_size           = 9,
+             .pages_per_block        = 8,
+             .blocks_per_sector      = 32,
+             .nr_sectors             = 32,
+             .name                   = "AT45DB321D",

the AT45DB321D is supposed to be 64 block per sector and 64 sectors

Best Regards,
J.

#6 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

tis 2009-01-06 klockan 14:48 -0800 skrev Brad Bozarth:

Quoted 7 lines

Hmm... looking in the datasheet I have, it says:
Flexible Erase Options
? Page Erase (512 Bytes)
? Block Erase (4 Kbytes)
? Sector Erase (64 Kbytes)
? Chip Erase (32 Mbits)

The dataflash is normally 528/1056 bytes per page.
D versions can be configured to have a 512/1024 bytes per page but that is wasting a couple of percent of the dataflash.

Best Regards
Ulf Samuelsson

Quoted 40 lines

which would indicate a third combo, different from mine and yours :) --- 16 blocks/sector and 64 sectors... The code only does page based so far, so I didn't catch this.

-brad

Quoted 25 lines · Jean-Christophe PLAGNIOL-VILLARD
Quoted 13 lines · Mike Frysinger

From: Brad Bozarth <[email protected]>

---
 drivers/mtd/spi/atmel.c |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)
drivers/mtd/spi/atmel.c +0 -0
index 10fcf0c..581b710 100644

drivers/mtd/spi/atmel.c to_atmel_spi_flash(struct spi_flash *flash) · line 60

Quoted 9 lines
drivers/mtd/spi/atmel.c +6 -0
@@ -52,6 +52,14 @@ to_atmel_spi_flash(struct spi_flash *flash)
 
 static const struct atmel_spi_flash_params atmel_spi_flash_table[] = {
      {
+             .idcode1                = 0x27,
+             .l2_page_size           = 9,
+             .pages_per_block        = 8,
+             .blocks_per_sector      = 32,
+             .nr_sectors             = 32,
+             .name                   = "AT45DB321D",

the AT45DB321D is supposed to be 64 block per sector and 64 sectors

Quoted 3 lines

Best Regards,
J.

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
http://lists.denx.de/mailman/listinfo/u-boot

#7 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

Quoted 11 lines · On Wednesday 07 January 2009 14:40:30 Ulf Samuelsson wrote:

tis 2009-01-06 klockan 14:48 -0800 skrev Brad Bozarth:

Quoted 6 lines

Hmm... looking in the datasheet I have, it says:
Flexible Erase Options
? Page Erase (512 Bytes)
? Block Erase (4 Kbytes)
? Sector Erase (64 Kbytes)
? Chip Erase (32 Mbits)

The dataflash is normally 528/1056 bytes per page.
D versions can be configured to have a 512/1024 bytes per page but that is wasting a couple of percent of the dataflash.

Blackfins can only boot with power of two flashes, so power of two page mode has to be supported for us ... not sure if the latest drivers have been fixed yet (both in u-boot and Linux)
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090108/f18afde0/attachment.pgp

#8 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

Linux - yes, it's supported. Uboot - I have another patch that allows power of 2 mode (I believe it's on the blackfin portal).

Sent from my mobile

Quoted 19 lines · Mike Frysinger
Quoted 11 lines · On Wednesday 07 January 2009 14:40:30 Ulf Samuelsson wrote:

tis 2009-01-06 klockan 14:48 -0800 skrev Brad Bozarth:

Quoted 6 lines

Hmm... looking in the datasheet I have, it says:
Flexible Erase Options
? Page Erase (512 Bytes)
? Block Erase (4 Kbytes)
? Sector Erase (64 Kbytes)
? Chip Erase (32 Mbits)

The dataflash is normally 528/1056 bytes per page.
D versions can be configured to have a 512/1024 bytes per page but that is wasting a couple of percent of the dataflash.

Blackfins can only boot with power of two flashes, so power of two page mode
has to be supported for us ... not sure if the latest drivers have been fixed
yet (both in u-boot and Linux)
-mike

#9 lore raw

PATCH 1/1 spi/atmel: add AT45DB321D support

Quoted 2 lines · On Thursday 08 January 2009 15:33:09 Brad Bozarth wrote:

Linux - yes, it's supported. Uboot - I have another patch that allows power of 2 mode (I believe it's on the blackfin portal).

istr said patch was against the Blackfin eeprom/spi driver and not the new common layer ? ive been largely ignoring changes to that driver and focusing on adding support for spi flashes to the new subsystem (spansion/sst/etc...). -mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 835 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090108/80ea87c2/attachment.pgp