<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/nvmem/sprd-efuse.c, branch v5.7.4</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=v5.7.4</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=v5.7.4'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2020-03-23T19:05:23+00:00</updated>
<entry>
<title>nvmem: sprd: Determine double data programming from device data</title>
<updated>2020-03-23T19:05:23+00:00</updated>
<author>
<name>Baolin Wang</name>
<email>baolin.wang7@gmail.com</email>
</author>
<published>2020-03-23T15:00:05+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4bd5a15d933c1703910c756d961dbbd2e6d52181'/>
<id>urn:sha1:4bd5a15d933c1703910c756d961dbbd2e6d52181</id>
<content type='text'>
We've saved the double data flag in the device data, so we should
use it when programming a block.

Signed-off-by: Baolin Wang &lt;baolin.wang7@gmail.com&gt;
Signed-off-by: Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;
Link: https://lore.kernel.org/r/20200323150007.7487-4-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>nvmem: sprd: Optimize the block lock operation</title>
<updated>2020-03-23T19:05:23+00:00</updated>
<author>
<name>Freeman Liu</name>
<email>freeman.liu@unisoc.com</email>
</author>
<published>2020-03-23T15:00:04+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=5af25388ba250ae9624a22587cc98685dc6d4e9e'/>
<id>urn:sha1:5af25388ba250ae9624a22587cc98685dc6d4e9e</id>
<content type='text'>
We have some cases that will programme the eFuse block partially multiple
times, so we should allow the block to be programmed again if it was
programmed partially. But we should lock the block if the whole block
was programmed. Thus add a condition to validate if we need lock the
block or not.

Moreover we only enable the auto-check function when locking the block.

Signed-off-by: Freeman Liu &lt;freeman.liu@unisoc.com&gt;
Signed-off-by: Baolin Wang &lt;baolin.wang7@gmail.com&gt;
Signed-off-by: Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;
Link: https://lore.kernel.org/r/20200323150007.7487-3-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>nvmem: sprd: Fix the block lock operation</title>
<updated>2020-03-23T19:05:23+00:00</updated>
<author>
<name>Freeman Liu</name>
<email>freeman.liu@unisoc.com</email>
</author>
<published>2020-03-23T15:00:03+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=c66ebde4d988b592e8f0008e04c47cc4950a49d3'/>
<id>urn:sha1:c66ebde4d988b592e8f0008e04c47cc4950a49d3</id>
<content type='text'>
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")
Cc: stable &lt;stable@vger.kernel.org&gt;
Signed-off-by: Freeman Liu &lt;freeman.liu@unisoc.com&gt;
Signed-off-by: Baolin Wang &lt;baolin.wang7@gmail.com&gt;
Signed-off-by: Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;
Link: https://lore.kernel.org/r/20200323150007.7487-2-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>nvmem: sprd: Add Spreadtrum SoCs eFuse support</title>
<updated>2019-11-05T17:35:31+00:00</updated>
<author>
<name>Freeman Liu</name>
<email>freeman.liu@unisoc.com</email>
</author>
<published>2019-10-29T11:42:37+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=096030e7f449caac81ee140d10d9b4b360b723fd'/>
<id>urn:sha1:096030e7f449caac81ee140d10d9b4b360b723fd</id>
<content type='text'>
The Spreadtrum eFuse controller is widely used to dump chip ID,
configuration setting, function select and so on, as well as
supporting one-time programming.

Signed-off-by: Freeman Liu &lt;freeman.liu@unisoc.com&gt;
Signed-off-by: Baolin Wang &lt;baolin.wang@linaro.org&gt;
Signed-off-by: Srinivas Kandagatla &lt;srinivas.kandagatla@linaro.org&gt;
Link: https://lore.kernel.org/r/20191029114240.14905-8-srinivas.kandagatla@linaro.org
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
</feed>
