From: Baolin Wang <baolin.wang7@gmail.com>
To: srinivas.kandagatla@linaro.org
Cc: orsonzhai@gmail.com, zhang.lyra@gmail.com,
freeman.liu@unisoc.com, baolin.wang7@gmail.com,
linux-kernel@vger.kernel.org
Subject: [PATCH 1/3] nvmem: sprd: Fix the block lock operation
Date: Fri, 13 Mar 2020 12:07:07 +0800 [thread overview]
Message-ID: <03c391fc1bbc3575ed47d5d249106de9e0b7d508.1584072223.git.baolin.wang7@gmail.com> (raw)
In-Reply-To: <cover.1584072223.git.baolin.wang7@gmail.com>
In-Reply-To: <cover.1584072223.git.baolin.wang7@gmail.com>
From: Freeman Liu <freeman.liu@unisoc.com>
According to the Spreadtrum eFuse specification, we should write 0 to
the block to trigger the lock operation.
Fixes: 096030e7f449 ("nvmem: sprd: Add Spreadtrum SoCs eFuse support")
Signed-off-by: Freeman Liu <freeman.liu@unisoc.com>
Signed-off-by: Baolin Wang <baolin.wang7@gmail.com>
---
drivers/nvmem/sprd-efuse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/nvmem/sprd-efuse.c b/drivers/nvmem/sprd-efuse.c
index 2f1e0fb..7a189ef 100644
--- a/drivers/nvmem/sprd-efuse.c
+++ b/drivers/nvmem/sprd-efuse.c
@@ -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);
}
--
1.9.1
next prev parent reply other threads:[~2020-03-13 4:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-13 4:07 [PATCH 0/3] Optimize the Spreadtrum eFuse controller Baolin Wang
2020-03-13 4:07 ` Baolin Wang [this message]
2020-03-18 13:40 ` [PATCH 1/3] nvmem: sprd: Fix the block lock operation Srinivas Kandagatla
2020-03-13 4:07 ` [PATCH 2/3] nvmem: sprd: Optimize " Baolin Wang
2020-03-13 4:07 ` [PATCH 3/3] nvmem: sprd: Determine double data programming from device data Baolin Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=03c391fc1bbc3575ed47d5d249106de9e0b7d508.1584072223.git.baolin.wang7@gmail.com \
--to=baolin.wang7@gmail.com \
--cc=freeman.liu@unisoc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=orsonzhai@gmail.com \
--cc=srinivas.kandagatla@linaro.org \
--cc=zhang.lyra@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®