diff options
author | Fabio Estevam <fabio.estevam@freescale.com> | 2015-11-05 12:43:42 -0200 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2015-11-05 16:47:06 -0500 |
commit | c3c016cf75360c2a0d0a065b64b438aaf7720576 (patch) | |
tree | 4152dc73b153374e211552a472daa21de5d6f0a9 /doc/feature-removal-schedule.txt | |
parent | 41b358d7a7c9f29eca4a439fba0ae679100a9ad5 (diff) | |
download | u-boot-imx-c3c016cf75360c2a0d0a065b64b438aaf7720576.zip u-boot-imx-c3c016cf75360c2a0d0a065b64b438aaf7720576.tar.gz u-boot-imx-c3c016cf75360c2a0d0a065b64b438aaf7720576.tar.bz2 |
sf: Add SPI NOR protection mechanism
Many SPI flashes have protection bits (BP2, BP1 and BP0) in the
status register that can protect selected regions of the SPI NOR.
Take these bits into account when performing erase operations,
making sure that the protected areas are skipped.
Tested on a mx6qsabresd:
=> sf probe
SF: Detected M25P32 with page size 256 Bytes, erase size 64 KiB, total 4 MiB
=> sf protect lock 0x3f0000 0x10000
=> sf erase 0x3f0000 0x10000
offset 0x3f0000 is protected and cannot be erased
SF: 65536 bytes @ 0x3f0000 Erased: ERROR
=> sf protect unlock 0x3f0000 0x10000
=> sf erase 0x3f0000 0x10000
SF: 65536 bytes @ 0x3f0000 Erased: OK
Signed-off-by: Fabio Estevam <fabio.estevam@freescale.com>
[re-worked to fit the lock common to dm and non-dm]
Signed-off-by: Jagan Teki <jteki@openedev.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
Reviewed-by: Heiko Schocher <hs@denx.de>
Reviewed-by: Jagan Teki <jteki@openedev.com>
Diffstat (limited to 'doc/feature-removal-schedule.txt')
0 files changed, 0 insertions, 0 deletions