U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Harsha Vardhan V M <h-vm@ti.com>
To: <u-boot@lists.denx.de>
Cc: <trini@konsulko.com>
Subject: [RFC PATCH 4/4] docs: fuse: Add fuse writebuff cmd docs
Date: Thu, 13 Mar 2025 17:25:17 +0530	[thread overview]
Message-ID: <20250313115517.1181829-5-h-vm@ti.com> (raw)
In-Reply-To: <20250313115517.1181829-1-h-vm@ti.com>

Add fuse writebuff sub-system command documentation

Signed-off-by: Harsha Vardhan V M <h-vm@ti.com>
---
 doc/README.fuse | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/doc/README.fuse b/doc/README.fuse
index 1bc91c44a6a..b150f39cc16 100644
--- a/doc/README.fuse
+++ b/doc/README.fuse
@@ -61,7 +61,21 @@ Functions / commands:
       fuses have already been programmed or are locked (if the SoC allows to
       override a locked fuse).
 
+   int fuse_writebuff(ulong addr);
+   fuse writebuff [-y] <addr>
+      Program 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.
+
 Configuration:
 
    CONFIG_CMD_FUSE
       Define this to enable the fuse commands.
+
+   CONFIG_CMD_FUSE_WRITEBUFF
+      Define this to enable the fuse writebuff command.
-- 
2.34.1


  parent reply	other threads:[~2025-03-13 11:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 11:55 [RFC PATCH 0/4] cmd: fuse: Introduce fuse writebuff sub-system and clean up Harsha Vardhan V M
2025-03-13 11:55 ` [RFC PATCH 1/4] cmd: fuse: Remove custom string functions Harsha Vardhan V M
2025-03-13 16:15   ` Tom Rini
2025-03-14 13:43     ` [EXTERNAL] " Harsha Vardhan V M
2025-03-14 14:09       ` Tom Rini
2025-03-17  8:59         ` Harsha Vardhan V M
2025-03-17 14:23           ` Tom Rini
2025-03-13 11:55 ` [RFC PATCH 2/4] cmd: fuse: Add fuse writebuff sub-system command Harsha Vardhan V M
2025-03-13 16:18   ` Tom Rini
2025-03-14 13:45     ` [EXTERNAL] " Harsha Vardhan V M
2025-03-13 11:55 ` [RFC PATCH 3/4] drivers: k3_fuse: Add fuse sub-system func calls Harsha Vardhan V M
2025-03-13 16:19   ` Tom Rini
2025-03-17  9:11     ` Harsha Vardhan V M
2025-03-13 11:55 ` Harsha Vardhan V M [this message]
2025-03-13 16:20   ` [RFC PATCH 4/4] docs: fuse: Add fuse writebuff cmd docs Tom Rini

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=20250313115517.1181829-5-h-vm@ti.com \
    --to=h-vm@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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