From: Harsha Vardhan V M <h-vm@ti.com>
To: <u-boot@lists.denx.de>
Cc: <trini@konsulko.com>
Subject: [RFC PATCH 0/4] cmd: fuse: Introduce fuse writebuff sub-system and clean up
Date: Thu, 13 Mar 2025 17:25:13 +0530 [thread overview]
Message-ID: <20250313115517.1181829-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 the fuse writebuff sub-system command, allowing to
write a structured buffer in memory to fuses, and implementing the
necessary function calls.
Patch 3 enables the fuse sub-system in the K3 platform.
Patch 4 updates the 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.
Harsha Vardhan V M (4):
cmd: fuse: Remove custom string functions
cmd: fuse: Add fuse writebuff sub-system command
drivers: k3_fuse: Add fuse sub-system func calls
docs: fuse: Add fuse writebuff cmd docs
cmd/Kconfig | 8 +++++
cmd/fuse.c | 49 ++++++++++++++------------
doc/README.fuse | 14 ++++++++
drivers/misc/Kconfig | 7 ++++
drivers/misc/Makefile | 1 +
drivers/misc/k3_fuse.c | 78 ++++++++++++++++++++++++++++++++++++++++++
include/fuse.h | 9 +++++
7 files changed, 145 insertions(+), 21 deletions(-)
create mode 100644 drivers/misc/k3_fuse.c
--
2.34.1
next reply other threads:[~2025-03-13 11:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 11:55 Harsha Vardhan V M [this message]
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 ` [RFC PATCH 4/4] docs: fuse: Add fuse writebuff cmd docs Harsha Vardhan V M
2025-03-13 16:20 ` 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-1-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