diff options
author | Ivan Mikhaylov <fr0st61te@gmail.com> | 2020-07-10 19:54:18 +0300 |
---|---|---|
committer | Tom Rini <trini@konsulko.com> | 2020-07-31 10:13:00 -0400 |
commit | db82015929aeff6b58982a22d61ab8c5b87752f3 (patch) | |
tree | 671af1a640f1fbb27f87a82685d8be9e632ee564 /board/ti/am57xx/Kconfig | |
parent | d045cbacf2529266bb312add023e12c0d400bf67 (diff) |
fw_setenv: lock the flash only if it was locked before
With current implementation of fw_setenv, it is always locks u-boot-env
region if lock interface is implemented for such mtd device. You can
not control lock of this region with fw_setenv, there is no option for
it in config or in application itself. Because of this situation may
happen problems like in this thread on xilinx forum:
https://forums.xilinx.com/t5/Embedded-Linux/Flash-be-locked-after-use-fw-setenv-from-user-space
/td-p/1027851
A short summary of that link is: some person has issue with some spi
chip which has lock interface but doesn't locks properly which leads to
lock of whole flash memory on lock of u-boot-env region. As resulted
solution hack was added into spi-nor.c driver for this chip with lock
disablement.
Instead fix this problem by adding logic to fw_setenv only lock the
flash if it was already locked when we attempted to use it.
Signed-off-by: Ivan Mikhaylov <fr0st61te@gmail.com>
Diffstat (limited to 'board/ti/am57xx/Kconfig')
0 files changed, 0 insertions, 0 deletions