[U-Boot] [PATCH] spi/atmel: add AT45DB321D support
From: Brad Bozarth bflinux@yumbrad.com
Signed-off-by: Brad Bozarth bflinux@yumbrad.com Signed-off-by: Mike Frysinger vapier@gentoo.org --- drivers/mtd/spi/atmel.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/spi/atmel.c b/drivers/mtd/spi/atmel.c index 10fcf0c..581b710 100644 --- a/drivers/mtd/spi/atmel.c +++ b/drivers/mtd/spi/atmel.c @@ -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,
On 02:59 Tue 30 Dec , Mike Frysinger wrote:
From: Brad Bozarth bflinux@yumbrad.com
Signed-off-by: Brad Bozarth bflinux@yumbrad.com Signed-off-by: Mike Frysinger vapier@gentoo.org
drivers/mtd/spi/atmel.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/spi/atmel.c b/drivers/mtd/spi/atmel.c index 10fcf0c..581b710 100644 --- a/drivers/mtd/spi/atmel.c +++ b/drivers/mtd/spi/atmel.c @@ -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.
- AT45DB321D - AT45DB161D - AT45DB081D - AT45DB041D - AT45DB021D - AT45DB011D
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com --- drivers/mtd/spi/atmel.c | 48 +++++++++++++++++++++++++++++++++++++++++++++++ 1 files changed, 48 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/spi/atmel.c b/drivers/mtd/spi/atmel.c index 10fcf0c..129475a 100644 --- a/drivers/mtd/spi/atmel.c +++ b/drivers/mtd/spi/atmel.c @@ -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,
On Sunday 04 January 2009 01:44:07 Jean-Christophe PLAGNIOL-VILLARD wrote:
- AT45DB321D
- AT45DB161D
- AT45DB081D
- AT45DB041D
- AT45DB021D
- AT45DB011D
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com
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
On 03:18 Thu 19 Mar , Mike Frysinger wrote:
On Sunday 04 January 2009 01:44:07 Jean-Christophe PLAGNIOL-VILLARD wrote:
- AT45DB321D
- AT45DB161D
- AT45DB081D
- AT45DB041D
- AT45DB021D
- AT45DB011D
Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com
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.
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
On Sat, Jan 3, 2009 at 10:36 PM, Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com wrote:
On 02:59 Tue 30 Dec , Mike Frysinger wrote:
From: Brad Bozarth bflinux@yumbrad.com
Signed-off-by: Brad Bozarth bflinux@yumbrad.com Signed-off-by: Mike Frysinger vapier@gentoo.org
drivers/mtd/spi/atmel.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/spi/atmel.c b/drivers/mtd/spi/atmel.c index 10fcf0c..581b710 100644 --- a/drivers/mtd/spi/atmel.c +++ b/drivers/mtd/spi/atmel.c @@ -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.
tis 2009-01-06 klockan 14:48 -0800 skrev Brad Bozarth:
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
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
On Sat, Jan 3, 2009 at 10:36 PM, Jean-Christophe PLAGNIOL-VILLARD plagnioj@jcrosoft.com wrote:
On 02:59 Tue 30 Dec , Mike Frysinger wrote:
From: Brad Bozarth bflinux@yumbrad.com
Signed-off-by: Brad Bozarth bflinux@yumbrad.com Signed-off-by: Mike Frysinger vapier@gentoo.org
drivers/mtd/spi/atmel.c | 8 ++++++++ 1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/drivers/mtd/spi/atmel.c b/drivers/mtd/spi/atmel.c index 10fcf0c..581b710 100644 --- a/drivers/mtd/spi/atmel.c +++ b/drivers/mtd/spi/atmel.c @@ -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.
U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
On Wednesday 07 January 2009 14:40:30 Ulf Samuelsson wrote:
tis 2009-01-06 klockan 14:48 -0800 skrev Brad Bozarth:
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
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
On Jan 8, 2009, at 2:51 AM, Mike Frysinger vapier@gentoo.org wrote:
On Wednesday 07 January 2009 14:40:30 Ulf Samuelsson wrote:
tis 2009-01-06 klockan 14:48 -0800 skrev Brad Bozarth:
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
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
participants (5)
-
Brad Bozarth -
Brad Bozarth -
Jean-Christophe PLAGNIOL-VILLARD -
Mike Frysinger -
Ulf Samuelsson