From: "NG, TZE YEE" <tze.yee.ng@altera.com>
To: Dinh Nguyen <dinguyen@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "NG, ADRIAN HO YIN" <adrian.ho.yin.ng@altera.com>,
"Nazle Asmade,
Muhammad Nazim Amirul"
<muhammad.nazim.amirul.nazle.asmade@altera.com>
Subject: Re: [PATCH] firmware: stratix10-rsu: Add synchronous fallback for async SVC operations
Date: Fri, 10 Jul 2026 07:10:10 +0000 [thread overview]
Message-ID: <84ee4b6c-4530-4055-9f1c-3a4c7b335274@altera.com> (raw)
In-Reply-To: <adf41452-7e7e-4ab0-b07e-567646d480c6@kernel.org>
On 9/7/2026 11:19 pm, Dinh Nguyen wrote:
>
>
> On 7/9/26 04:13, NG, TZE YEE wrote:
>> On 26/5/2026 5:41 pm, NG, TZE YEE wrote:
>>> From: Mahesh Rao <mahesh.rao@altera.com>
>>>
>>> The RSU driver was migrated to the Stratix10 asynchronous service
>>> framework, which assumes async client registration always succeeds. On
>>> platforms where the async controller is unavailable or RSU async support
>>> is not present, probe fails or sysfs operations cannot reach firmware.
>>>
>>> Detect async capability at probe via stratix10_svc_add_async_client()
>>> and
>>> fall back to the legacy synchronous rsu_send_msg() path when
>>> registration
>>> fails. Track capability in priv->async and branch accordingly for:
>>>
>>> - Initial RSU status and retry counter during probe (retry is
>>> bundled in
>>> async status; issue COMMAND_RSU_RETRY separately in sync mode)
>>> - notify sysfs store (notify, status, and retry)
>>> - SPT table retrieval (COMMAND_RSU_GET_SPT_TABLE async vs mbox
>>> COMMAND_MBOX_SEND_CMD synchronous)
>>>
>>> Restore synchronous callbacks (rsu_status_callback, rsu_retry_callback,
>>> rsu_get_spt_callback) and wire COMMAND_MBOX_SEND_CMD payload handling in
>>> rsu_send_msg().
>>>
>>> Improve probe and remove cleanup: return on intermediate probe failures,
>>> remove the async client when registered, and free the SPT response
>>> buffer
>>> on sync-path allocation errors.
>>>
>
>
>>> }
>>
>> Hi,
>>
>> Gentle ping on this patch — any chance for a review when you have time?
>> Happy to rebase or revise based on your feedback.
>>
>
> Sorry for missing this. Can you please rebase this to
> socfpga_firmware_for_v7.3 on my tree and I will review it.
>
> Thanks,
> Dinh
>
Hi Dinh,
Sure. I have rebased to socfpga_firmware_for_v7.3 in v2:
https://lore.kernel.org/all/e991a29b0c7bd567da6b9e9a3a59486774a34ab2.1783666551.git.tze.yee.ng@altera.com/
Thanks for checking.
Tze Yee
prev parent reply other threads:[~2026-07-10 7:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 9:41 tze.yee.ng
2026-07-09 9:13 ` NG, TZE YEE
2026-07-09 15:19 ` Dinh Nguyen
2026-07-10 7:10 ` NG, TZE YEE [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=84ee4b6c-4530-4055-9f1c-3a4c7b335274@altera.com \
--to=tze.yee.ng@altera.com \
--cc=adrian.ho.yin.ng@altera.com \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=muhammad.nazim.amirul.nazle.asmade@altera.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
all inboxes | Powered by JetHome®