mirror of
https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git
synced 2026-10-11 23:24:22 -04:00
UPSTREAM: nvmem: sprd: Fix the block lock operation
According to the Spreadtrum eFuse specification, we should write 0 to
the block to trigger the lock operation.
bug: 153500755
Fixes: 096030e7f449 ("nvmem: sprd: Add Spreadtrum SoCs eFuse support")
Change-Id: I4080e4a4ed1de45f79ce2fbadd1b66aa53b8495b
Cc: stable <stable@vger.kernel.org>
Signed-off-by: Freeman Liu <freeman.liu@unisoc.com>
Signed-off-by: Baolin Wang <baolin.wang7@gmail.com>
Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Link: https://lore.kernel.org/r/20200323150007.7487-2-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
(cherry picked from commit c66ebde4d988b592e8f0008e04c47cc4950a49d3)
This commit is contained in:
parent
601cd6e2ce
commit
13ebd2bf97
1 changed files with 1 additions and 1 deletions
|
|
@ -239,7 +239,7 @@ static int sprd_efuse_raw_prog(struct sprd_efuse *efuse, u32 blk, bool doub,
|
|||
ret = -EBUSY;
|
||||
} else {
|
||||
sprd_efuse_set_prog_lock(efuse, lock);
|
||||
writel(*data, efuse->base + SPRD_EFUSE_MEM(blk));
|
||||
writel(0, efuse->base + SPRD_EFUSE_MEM(blk));
|
||||
sprd_efuse_set_prog_lock(efuse, false);
|
||||
}
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue