From: Dinh Nguyen <dinguyen@kernel.og>
To: mahesh.rao@altera.com, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Matthew Gerlach <matthew.gerlach@altera.com>
Subject: Re: [PATCH RESEND v2 4/4] firmware: stratix10-svc: Add for SDM mailbox doorbell interrupt
Date: Mon, 1 Sep 2025 10:21:37 -0500 [thread overview]
Message-ID: <5c616645-cbfe-4c7d-b4bd-72497a90f497@kernel.og> (raw)
In-Reply-To: <f2411365-9443-43cf-8420-3afd2c5bf6e2@kernel.og>
On 9/1/25 10:16, Dinh Nguyen wrote:
>
>
> On 8/12/25 07:59, Mahesh Rao via B4 Relay wrote:
>> From: Mahesh Rao <mahesh.rao@altera.com>
>>
>> Add support for SDM (Secure Device Manager) mailbox
>> doorbell interrupt for async transactions. On interrupt,
>> a workqueue is triggered which polls the ATF for
>> pending responses and retrieves the bitmap of all
>> retrieved and unprocessed transaction ids of mailbox
>> responses from SDM. It then triggers the corresponding
>> registered callbacks.
>
> You should configure your editor to use a full 80-char width. Why stop
> at ~50? When you're unsure, look at that other commit logs from other
> developers. If yours doesn't look similar, its probably a problem. For
> example:
>
> "Add support for SDM (Secure Device Manager) mailbox doorbell interrupt
> for async transactions. On interrupt, a workqueue is triggered which
> polls the ATF for pending responses and retrieves the bitmap of all
> retrieved and unprocessed transaction ids of mailbox responses from SDM.
> It then triggers the corresponding registered callbacks."
>
>>
>> Signed-off-by: Mahesh Rao <mahesh.rao@altera.com>
>> Reviewed-by: Matthew Gerlach <matthew.gerlach@altera.com>
>> ---
<snip>
>> @@ -1784,13 +1874,14 @@ static int stratix10_svc_async_init(struct
>> stratix10_svc_controller *controller)
>> * service controller
>> * @ctrl: Pointer to the stratix10_svc_controller structure
>> *
>> - * This function performs the necessary cleanup for the asynchronous
>> - * service controller. It checks if the controller is valid and if it
>> - * has been initialized. It then locks the transaction list and safely
>> - * removes and deallocates each handler in the list. The function also
>> - * removes any asynchronous clients associated with the controller's
>> - * channels and destroys the asynchronous ID pool. Finally, it resets
>> - * the asynchronous ID pool and invoke function pointers to NULL.
>> + * This function performs the necessary cleanup for the asynchronous
>> service
>> + * controller. It checks if the controller is valid and if it has been
>> + * initialized. Also If the controller has an IRQ assigned, it frees
>> the IRQ
>> + * and flushes any pending asynchronous work. It then locks the
>> transaction
>> + * list and safely removes and deallocates each handler in the list.
>> + * The function also removes any asynchronous clients associated with
>> the
>> + * controller's channels and destroys the asynchronous ID pool.
>> Finally, it
>> + * resets the asynchronous ID pool and invoke function pointers to NULL.
>
> Did you mean to repeat the same paragraph twice?
>
Ignore this comment...
next prev parent reply other threads:[~2025-09-01 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 12:59 [PATCH RESEND v2 0/4] stratix10: Add Interrupt support for asynchronous communication with SDM Mahesh Rao via B4 Relay
2025-08-12 12:59 ` [PATCH RESEND v2 1/4] dt-bindings: firmware: Add interrupt specification for Intel Stratix 10 Service Layer Mahesh Rao via B4 Relay
2025-08-12 12:59 ` [PATCH RESEND v2 2/4] dts: stratix10: Add support for SDM mailbox interrupt for Intel Stratix10 SoC FPGA Mahesh Rao via B4 Relay
2025-08-12 12:59 ` [PATCH RESEND v2 3/4] dts: agilex: Add support for SDM mailbox interrupt for Intel Agilex " Mahesh Rao via B4 Relay
2025-08-12 12:59 ` [PATCH RESEND v2 4/4] firmware: stratix10-svc: Add for SDM mailbox doorbell interrupt Mahesh Rao via B4 Relay
2025-09-01 15:16 ` Dinh Nguyen
2025-09-01 15:21 ` Dinh Nguyen [this message]
2025-09-02 10:08 ` Mahesh Rao
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=5c616645-cbfe-4c7d-b4bd-72497a90f497@kernel.og \
--to=dinguyen@kernel.og \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahesh.rao@altera.com \
--cc=matthew.gerlach@altera.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).