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 0/5] cmd: fuse: Introduce fuse writebuff sub-system and clean up
Date: Fri, 14 Mar 2025 19:27:01 +0530 [thread overview]
Message-ID: <20250314135706.184807-1-h-vm@ti.com> (raw)
This patch series introduces the fuse writebuff sub-system command and
makes improvements to the existing fuse implementation by removing the
custom string functions. The patches are required to be applied in
sequence.
The series consists of the following changes:
Patch 1 removes custom string functions and replaces them with standard
string functions.
Patch 2 introduces fuse.rst documentation for fuse commands.
Patch 3 introduces the fuse writebuff sub-system command, allowing to
write a structured buffer in memory to fuses, and implementing the
necessary function calls.
Patch 4 enables the fuse sub-system in the K3 platform.
Patch 5 updates the fuse.rst documentation to include details about the
new fuse writebuff command.
These changes aim to improve the fuse sub-system by the removal of
custom string functions and the addition of the fuse writebuff
command improves fuse programming workflows by allowing to write a
structured buffer in memory to efuses.
Changes in v2:
1.Convert doc/README.fuse to doc/usage/cmd/fuse.rst as patch #2,
as requested by trini@konsulko.com.
2.Add fuse writebuff documentation in fuse.rst in the final patch.
Harsha Vardhan V M (5):
cmd: fuse: Remove custom string functions
doc: cmd: add documentation for fuse command
cmd: fuse: Add fuse writebuff sub-system command
drivers: k3_fuse: Add fuse sub-system func calls
doc: cmd: add fuse writebuff cmd documentation
cmd/Kconfig | 8 ++
cmd/fuse.c | 49 +++++++-----
doc/usage/cmd/fuse.rst | 176 +++++++++++++++++++++++++++++++++++++++++
drivers/misc/Kconfig | 7 ++
drivers/misc/Makefile | 1 +
drivers/misc/k3_fuse.c | 78 ++++++++++++++++++
include/fuse.h | 9 +++
7 files changed, 307 insertions(+), 21 deletions(-)
create mode 100644 doc/usage/cmd/fuse.rst
create mode 100644 drivers/misc/k3_fuse.c
--
2.34.1
next reply other threads:[~2025-03-14 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-14 13:57 Harsha Vardhan V M [this message]
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 ` [RFC PATCH v2 5/5] doc: cmd: add fuse writebuff cmd documentation Harsha Vardhan V M
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-1-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