From: tze.yee.ng@altera.com
To: Dinh Nguyen <dinguyen@kernel.org>, linux-kernel@vger.kernel.org
Subject: [PATCH v4 0/3] firmware: stratix10-rsu: expose QSPI flash size and erase size from firmware
Date: Thu, 9 Jul 2026 23:52:36 -0700 [thread overview]
Message-ID: <cover.1783665493.git.tze.yee.ng@altera.com> (raw)
From: Tze Yee Ng <tze.yee.ng@altera.com>
This series lets user space read per-device QSPI flash size and erase
size for the Intel Stratix 10 RSU driver, using the existing service
layer SMC path.
Patch 1 documents the new sysfs attributes (size0-size3 and
erase_size0-erase_size3).
Patch 2 implements COMMAND_RSU_GET_DEVICE_INFO in the RSU and service
drivers, caches up to four devices in the driver, and adds the sysfs
files.
Patch 3 fixes remove() teardown after the async client is registered:
call stratix10_svc_remove_async_client() before
stratix10_svc_free_channel() so async state is not leaked.
Changes in v4:
- Rebased onto dinguyen/socfpga_svc_fixes_for_v7.2 (for v7.2
integration), instead of torvalds/master.
- Probe error-path teardown from v3 patch 3/3 is dropped; that is
already in dinguyen's tree in commit
bfd2eb9bba54 ("firmware: stratix10-rsu: Fix NULL deref on rsu_send_msg() timeout in probe"),
which centralizes probe cleanup with goto labels.
- Patch 3/3 is narrowed to stratix10_rsu_remove() only (1 line); probe
paths and return 0 on success are no longer in this series.
- Patch 2/3 wires COMMAND_RSU_GET_DEVICE_INFO probe errors into the
rebased goto remove_async_client path.
Changes in v3:
- No code changes in all patches, only put Cc: stable@vger.kernel.org
# 6.19+ in the sign-off block for the Fixes: tag in Patch 3.
Changes in v2:
- No code changes in all patches, only documentation updates to fix commit
title and description in Patch 3.
Tze Yee Ng (3):
Documentation: ABI: add stratix10-rsu QSPI size and erase_size sysfs
firmware: stratix10-rsu: Add flash device info retrieval via SMC
firmware: stratix10-rsu: remove async client before freeing channel in
remove()
.../sysfs-devices-platform-stratix10-rsu | 58 +++++
drivers/firmware/stratix10-rsu.c | 201 +++++++++++++++++-
drivers/firmware/stratix10-svc.c | 94 +++++++-
include/linux/firmware/intel/stratix10-smc.h | 25 ++-
.../firmware/intel/stratix10-svc-client.h | 12 +-
5 files changed, 373 insertions(+), 17 deletions(-)
--
2.43.7
next reply other threads:[~2026-07-10 6:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 6:52 tze.yee.ng [this message]
2026-07-10 6:52 ` [PATCH v4 1/3] Documentation: ABI: add stratix10-rsu QSPI size and erase_size sysfs tze.yee.ng
2026-07-10 6:52 ` [PATCH v4 2/3] firmware: stratix10-rsu: Add flash device info retrieval via SMC tze.yee.ng
2026-07-10 6:52 ` [PATCH v4 3/3] firmware: stratix10-rsu: remove async client before freeing channel in remove() tze.yee.ng
2026-07-10 13:42 ` Dinh Nguyen
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=cover.1783665493.git.tze.yee.ng@altera.com \
--to=tze.yee.ng@altera.com \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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