| #
acc23754 |
| 21-Jun-2013 |
Jagannadha Sutradharudu Teki <jagannadha.sutradharudu-teki@xilinx.com> |
sf: Unify spi_flash write code
Move common flash write code into spi_flash_write_common().
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Acked-by: Simon Glass <sjg@chromium.org>
|
| #
615a1561 |
| 21-Jun-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Add flag status register polling support
Flag status register polling is required for micron 512Mb flash devices onwards, for performing erase/program operations.
Like polling for WIP(Write-In-
sf: Add flag status register polling support
Flag status register polling is required for micron 512Mb flash devices onwards, for performing erase/program operations.
Like polling for WIP(Write-In-Progress) bit in read status register, spi_flash_cmd_wait_ready will poll for PEC(Program-Erase-Control) bit in flag status register.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
ba549de6 |
| 26-May-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Remove spi_flash_cmd_poll_bit()
There is no other call other than spi_flash_cmd_wait_ready(), hence removed spi_flash_cmd_poll_bit and use the poll status code spi_flash_cmd_wait_ready() itself.
sf: Remove spi_flash_cmd_poll_bit()
There is no other call other than spi_flash_cmd_wait_ready(), hence removed spi_flash_cmd_poll_bit and use the poll status code spi_flash_cmd_wait_ready() itself.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
f76b1bd0 |
| 11-Jun-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Use spi_flash_addr() in write call
Use the existing spi_flash_addr() for 3-byte addressing cmd filling in write call.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-b
sf: Use spi_flash_addr() in write call
Use the existing spi_flash_addr() for 3-byte addressing cmd filling in write call.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
1dcd6d03 |
| 19-Jun-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Add bank addr code in CONFIG_SPI_FLASH_BAR
Defined bank addr code on CONFIG_SPI_FLASH_BAR macro, to reduce the size for existing boards which has < 16Mbytes SPI flashes.
It's upto user which ha
sf: Add bank addr code in CONFIG_SPI_FLASH_BAR
Defined bank addr code on CONFIG_SPI_FLASH_BAR macro, to reduce the size for existing boards which has < 16Mbytes SPI flashes.
It's upto user which has provision to use the bank addr code for flashes which has > 16Mbytes.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
fc207ee4 |
| 31-May-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Update sf read to support all sizes of flashes
This patch updated the spi_flash read func to support all sizes of flashes using bank reg addr facility.
The same support has been added in below
sf: Update sf read to support all sizes of flashes
This patch updated the spi_flash read func to support all sizes of flashes using bank reg addr facility.
The same support has been added in below patch for erase/write spi_flash functions: "sf: Support all sizes of flashes using bank addr reg facility" (sha1: c956f600cbb0943d0afe1004cdb503f4fcd8f415)
With these new updates on sf framework, the flashes which has < 16MB are not effected as per as performance is concern and but the u-boot.bin size incrased ~460 bytes.
sf update(for first 16MBytes), Changes before: U-Boot> sf update 0x1000000 0x0 0x1000000 - N25Q256 16777216 bytes written, 0 bytes skipped in 199.72s, speed 86480 B/s - W25Q128BV 16777216 bytes written, 0 bytes skipped in 351.739s, speed 48913 B/s - S25FL256S_64K 16777216 bytes written, 0 bytes skipped in 65.659s, speed 262144 B/s
sf update(for first 16MBytes), Changes before: U-Boot> sf update 0x1000000 0x0 0x1000000 - N25Q256 16777216 bytes written, 0 bytes skipped in 198.953s, speed 86480 B/s - W25Q128BV 16777216 bytes written, 0 bytes skipped in 350.90s, speed 49200 B/s - S25FL256S_64K 16777216 bytes written, 0 bytes skipped in 66.521s, speed 262144 B/s
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
e3ff9d51 |
| 30-May-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Update sf to support all sizes of flashes
Updated the spi_flash framework to handle all sizes of flashes using bank/extd addr reg facility
The current implementation in spi_flash supports 3-byt
sf: Update sf to support all sizes of flashes
Updated the spi_flash framework to handle all sizes of flashes using bank/extd addr reg facility
The current implementation in spi_flash supports 3-byte address mode due to this up to 16Mbytes amount of flash is able to access for those flashes which has an actual size of > 16MB.
As most of the flashes introduces a bank/extd address registers for accessing the flashes in 16Mbytes of banks if the flash size is > 16Mbytes, this new scheme will add the bank selection feature for performing write/erase operations on all flashes.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
e612ddf5 |
| 19-Jun-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Read flash bank addr register at probe time
Read the flash bank addr register to get the state of bank in a perticular flash. and also bank write happens only when there is a change in bank sele
sf: Read flash bank addr register at probe time
Read the flash bank addr register to get the state of bank in a perticular flash. and also bank write happens only when there is a change in bank selection from user.
bank read only valid for flashes which has > 16Mbytes those are opearted in 3-byte addr mode, each bank occupies 16Mytes.
Suppose if the flash has 64Mbytes size consists of 4 banks like bank0, bank1, bank2 and bank3.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
cf6b11dc |
| 19-Jun-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Discover the bank addr commands
Bank/Extended addr commands are specific to particular flash vendor so discover them based on the idocode0.
Assign the discovered bank commands to spi_flash memb
sf: Discover the bank addr commands
Bank/Extended addr commands are specific to particular flash vendor so discover them based on the idocode0.
Assign the discovered bank commands to spi_flash members so-that the bank read/write will use their specific operations.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com>
show more ...
|
| #
c9fcb59d |
| 13-Jun-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
sf: Add bank address register writing support
This patch provides support to program a flash bank address register.
extended/bank address register contains an information to access the 4th byte add
sf: Add bank address register writing support
This patch provides support to program a flash bank address register.
extended/bank address register contains an information to access the 4th byte addressing in 3-byte address mode.
reff' the spec for more details about bank addr register in Page-63, Table 8.16 http://www.spansion.com/Support/Datasheets/S25FL128S_256S_00.pdf
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
348e47f7 |
| 22-Jun-2013 |
Tom Rini <trini@ti.com> |
Merge branch 'master' of git://git.denx.de/u-boot-arm
|
| #
69f14dc2 |
| 19-Jun-2013 |
Albert ARIBAUD <albert.u.boot@aribaud.net> |
Merge branch 'u-boot-samsung/master' into 'u-boot-arm/master'
Conflicts: spl/Makefile
|
| #
f0df2546 |
| 13-Jun-2013 |
Tom Rini <trini@ti.com> |
Merge branch 'master' of git://git.denx.de/u-boot-spi
|
| #
60b6614a |
| 26-May-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
cmd_sf: Add print mesgs on sf read/write commands
This patch adds a print messages while using 'sf read' and 'sf write' commands to make sure that how many bytes read/written from/into flash device.
cmd_sf: Add print mesgs on sf read/write commands
This patch adds a print messages while using 'sf read' and 'sf write' commands to make sure that how many bytes read/written from/into flash device.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Acked-by: Tom Rini <trini@ti.com>
show more ...
|
| #
96bbf556 |
| 25-May-2013 |
Jagannadha Sutradharudu Teki <jaganna@xilinx.com> |
cmd_sf: Add print mesg for 'sf erase' command
This patch adds a print messages while using 'sf erase' command to make sure that how many bytes erased in flash device.
Signed-off-by: Jagannadha Sutr
cmd_sf: Add print mesg for 'sf erase' command
This patch adds a print messages while using 'sf erase' command to make sure that how many bytes erased in flash device.
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Acked-by: Tom Rini <trini@ti.com>
show more ...
|
| #
0d3b596a |
| 27-May-2013 |
Jagannadha Sutradharudu Teki <jagannadha.sutradharudu-teki@xilinx.com> |
sf: Fix sf read for memory-mapped SPI flashes
Missing return after memcpy is done for memory-mapped SPI flashes, hence added retun 0 after memcpy done.
The return is missing in below patch "sf: Ena
sf: Fix sf read for memory-mapped SPI flashes
Missing return after memcpy is done for memory-mapped SPI flashes, hence added retun 0 after memcpy done.
The return is missing in below patch "sf: Enable FDT-based configuration and memory mapping" (sha1: bb8215f437a7c948eec82a6abe754c226978bd6d)
Signed-off-by: Jagannadha Sutradharudu Teki <jaganna@xilinx.com> Acked-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
f10b4c0e |
| 22-Jan-2013 |
Rajeshwari Shinde <rajeshwari.s@samsung.com> |
SF: Add driver for Gigabyte device GD25LQ and GD25Q64B
This patch adds driver for the gigabyte devices GD25LQ and GD25Q64B required for Snow Board.
Signed-off-by: Rajeshwari Shinde <rajeshwari.s@sa
SF: Add driver for Gigabyte device GD25LQ and GD25Q64B
This patch adds driver for the gigabyte devices GD25LQ and GD25Q64B required for Snow Board.
Signed-off-by: Rajeshwari Shinde <rajeshwari.s@samsung.com> Acked-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@ti.com> Signed-off-by: Minkyu Kang <mk7.kang@samsung.com>
show more ...
|
| #
8b906a9f |
| 20-Mar-2013 |
Tom Rini <trini@ti.com> |
Merge branch 'spi' of git://git.denx.de/u-boot-x86
|
| #
bb8215f4 |
| 11-Mar-2013 |
Simon Glass <sjg@chromium.org> |
sf: Enable FDT-based configuration and memory mapping
Enable device tree control of SPI flash, and use this to implement memory-mapped SPI flash, which is supported on Intel chips.
Signed-off-by: S
sf: Enable FDT-based configuration and memory mapping
Enable device tree control of SPI flash, and use this to implement memory-mapped SPI flash, which is supported on Intel chips.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
1e566bc6 |
| 11-Mar-2013 |
Simon Glass <sjg@chromium.org> |
sf: Respect maximum SPI write size
Some SPI flash controllers (e.g. Intel ICH) have a limit on the number of bytes that can be in a write transaction. Support this by breaking the writes into multip
sf: Respect maximum SPI write size
Some SPI flash controllers (e.g. Intel ICH) have a limit on the number of bytes that can be in a write transaction. Support this by breaking the writes into multiple transactions.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
b5aec142 |
| 11-Mar-2013 |
Simon Glass <sjg@chromium.org> |
sf: Add spi_flash_alloc() to create a new SPI flash struct
At present it is difficult to extend the SPI flash structure since all devices allocate it themselves, and few of them zero all fields. Add
sf: Add spi_flash_alloc() to create a new SPI flash struct
At present it is difficult to extend the SPI flash structure since all devices allocate it themselves, and few of them zero all fields. Add a new function spi_flash_alloc() which can be used by SPI devices to perform this allocation, and thus ensure that all devices can better cope with SPI structure changes.
Signed-off-by: Simon Glass <sjg@chromium.org>
show more ...
|
| #
41e17134 |
| 05-Mar-2012 |
Mike Frysinger <vapier@gentoo.org> |
sf: unify status register writing (and thus block unlocking)
The only two drivers to write the status register do it in the same way, so unify the implementations. This also makes the block unlock
sf: unify status register writing (and thus block unlocking)
The only two drivers to write the status register do it in the same way, so unify the implementations. This also makes the block unlock logic the same.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
show more ...
|
| #
c4e932ce |
| 05-Mar-2012 |
Mike Frysinger <vapier@gentoo.org> |
sf: unify erase commands
Analysis of the flash drivers shows that they all use 0x20 if the erase size is 4KiB, or 0xd8 if it's larger. So with this info in hand, we can unify all the erase function
sf: unify erase commands
Analysis of the flash drivers shows that they all use 0x20 if the erase size is 4KiB, or 0xd8 if it's larger. So with this info in hand, we can unify all the erase functionality in one place.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
show more ...
|
| #
d194837f |
| 05-Dec-2011 |
Wolfgang Denk <wd@denx.de> |
Merge branch 'agust@denx.de' of git://git.denx.de/u-boot-staging
* 'agust@denx.de' of git://git.denx.de/u-boot-staging: Makefile: add tools/mkenvimage to target 'clean' mv_common.c: get rid of '
Merge branch 'agust@denx.de' of git://git.denx.de/u-boot-staging
* 'agust@denx.de' of git://git.denx.de/u-boot-staging: Makefile: add tools/mkenvimage to target 'clean' mv_common.c: get rid of 'defined but not used' warning m68k: fix ambiguous bit testing sparc: fix unknown escape sequence warnings sparc: fix unused variable warnings sf: fix erase debug output
show more ...
|
| #
1f6734cf |
| 12-Oct-2011 |
Vadim Bendebury <vbendeb@chromium.org> |
sf: fix erase debug output
We want to show the length, so multiplying by sector size makes no sense. This is a hold over from the erase code before the big refactor.
Signed-off-by: Vadim Bendebury
sf: fix erase debug output
We want to show the length, so multiplying by sector size makes no sense. This is a hold over from the erase code before the big refactor.
Signed-off-by: Vadim Bendebury <vbendeb@chromium.org> Signed-off-by: Mike Frysinger <vapier@gentoo.org>
show more ...
|