From: Harsha Vardhan V M <h-vm@ti.com>
To: <u-boot@lists.denx.de>
Cc: <trini@konsulko.com>, <vigneshr@ti.com>, <k-malarvizhi@ti.com>,
<kamlesh@ti.com>
Subject: [RFC PATCH v2 5/5] doc: cmd: add fuse writebuff cmd documentation
Date: Fri, 14 Mar 2025 19:27:06 +0530 [thread overview]
Message-ID: <20250314135706.184807-6-h-vm@ti.com> (raw)
In-Reply-To: <20250314135706.184807-1-h-vm@ti.com>
Add fuse writebuff sub-system command documentation.
Signed-off-by: Harsha Vardhan V M <h-vm@ti.com>
---
doc/usage/cmd/fuse.rst | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/doc/usage/cmd/fuse.rst b/doc/usage/cmd/fuse.rst
index 6e330eddfea..42c6e209f99 100644
--- a/doc/usage/cmd/fuse.rst
+++ b/doc/usage/cmd/fuse.rst
@@ -17,6 +17,7 @@ Synopsis
fuse sense <bank> <word> [<cnt>]
fuse prog [-y] <bank> <word> <hexval> [<hexval>...]
fuse override <bank> <word> <hexval> [<hexval>...]
+ fuse writebuff [-y] <addr>
Description
-----------
@@ -79,6 +80,16 @@ Commands
fuses have already been programmed or are locked (if the SoC allows to
override a locked fuse).
+- **fuse writebuff [-y] <addr>**
+ Programs fuse data using a structured buffer in memory starting at 'addr'.
+ This operation directly affects the fusebox and is irreversible.
+
+ The structure of the buffer should contain all necessary details for
+ programming fuses, such as the values to be written to the fuse, optional
+ metadata for validation or programming constraints and any configuration
+ data required for the operation. Define CONFIG_CMD_FUSE_WRITEBUFF to
+ enable the fuse writebuff command.
+
Examples
--------
@@ -144,10 +155,19 @@ fuse override
u-boot=> fuse override 0 1 0x00000003
Overriding bank 0 word 0x00000001 with 0x00000003...
+fuse writebuff
+~~~~~~~~~~~~~~
+
+::
+
+ u-boot=> fuse writebuff -y 0x84000000
+ Programming fuses with buffer at addr 0x84000000
+
Configuration
-------------
The fuse commands are available if CONFIG_CMD_FUSE=y.
+The fuse writebuff command is available if CONFIG_CMD_FUSE_WRITEBUFF=y.
Return code
-----------
--
2.34.1
prev parent reply other threads:[~2025-03-14 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 13:57 [RFC PATCH v2 0/5] cmd: fuse: Introduce fuse writebuff sub-system and clean up Harsha Vardhan V M
2025-03-14 13:57 ` [RFC PATCH v2 1/5] cmd: fuse: Remove custom string functions Harsha Vardhan V M
2025-03-14 13:57 ` [RFC PATCH v2 2/5] doc: cmd: add documentation for fuse command Harsha Vardhan V M
2025-03-14 16:38 ` Tom Rini
2025-03-17 9:04 ` Harsha Vardhan V M
2025-03-14 13:57 ` [RFC PATCH v2 3/5] cmd: fuse: Add fuse writebuff sub-system command Harsha Vardhan V M
2025-03-14 13:57 ` [RFC PATCH v2 4/5] drivers: k3_fuse: Add fuse sub-system func calls Harsha Vardhan V M
2025-03-14 13:57 ` Harsha Vardhan V M [this message]
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=20250314135706.184807-6-h-vm@ti.com \
--to=h-vm@ti.com \
--cc=k-malarvizhi@ti.com \
--cc=kamlesh@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.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