From: Dinh Nguyen <dinguyen@kernel.org>
To: Mahesh Rao <mahesh.rao@altera.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: Matthew Gerlach <matthew.gerlach@altera.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 3/7] firmware: stratix10-svc: Add initial support for asynchronous communication with Stratix 10 service channel
Date: Wed, 21 May 2025 15:18:48 -0500 [thread overview]
Message-ID: <40b939d6-9339-444f-a2e4-3e4cd4bcb317@kernel.org> (raw)
In-Reply-To: <0eab3179-645c-41e8-8d21-111b11ba5c6d@altera.com>
On 5/21/25 03:42, Mahesh Rao wrote:
>
>
> On 19-05-2025 05:28 pm, Dinh Nguyen wrote:
>> On 5/12/25 06:39, Mahesh Rao via B4 Relay wrote:
>>> From: Mahesh Rao <mahesh.rao@altera.com>
>>>
<snip>
>>> +
>>> +/**
>>> + * stratix10_svc_async_prepare_response - Prepare the response data
>>> for an asynchronous transaction.
>>> + * @chan: Pointer to the service channel structure.
>>> + * @handle: Pointer to the asynchronous handler structure.
>>> + * @data: Pointer to the callback data structure.
>>> + *
>>> + * This function prepares the response data for an asynchronous
>>> transaction. It
>>> + * extracts the response data from the SMC response structure and
>>> stores it in
>>> + * the callback data structure. The function also logs the
>>> completion of the
>>> + * asynchronous transaction.
>>> + *
>>> + * Return: 0 on success, -ENOENT if the command is invalid
>>> + */
>>> +static int stratix10_svc_async_prepare_response(struct
>>> stratix10_svc_chan *chan,
>>> + struct stratix10_svc_async_handler *handle,
>>> + struct stratix10_svc_cb_data *data)
>>> +{
>>> + struct stratix10_svc_client_msg *p_msg =
>>> + (struct stratix10_svc_client_msg *)handle->msg;
>>> + struct stratix10_svc_controller *ctrl = chan->ctrl;
>>> +
>>> + data->status = STRATIX10_GET_SDM_STATUS_CODE(handle->res.a1);
>>> +
>>> + switch (p_msg->command) {
>>> + default:
>>> + dev_alert(ctrl->dev, "Invalid command\n ,%d", p_msg->command);
>>> + return -ENOENT;
>>> + }
>>
>> What is the above code doing?
>
> This function prepares the response for clients after retriving the
> response from the Arm Trusted Firmware using the polling call. Currently
> only the negative scenario is shown for incvalid command, the last patch
> in series adds command for hwmon for the positive scenario.
>
Okay, but this is confusing. Please just add this to the last patch then.
next prev parent reply other threads:[~2025-05-21 20:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 11:39 [PATCH v2 0/7] stratix10: Add framework for asynchronous communication with SDM Mahesh Rao via B4 Relay
2025-05-12 11:39 ` [PATCH v2 1/7] firmware: stratix10-svc: Add mutex lock and unlock in stratix10 memory allocation/free Mahesh Rao via B4 Relay
2025-05-12 11:39 ` [PATCH v2 2/7] firmware: stratix10-svc: Implement ID pool management for asynchronous operations Mahesh Rao via B4 Relay
2025-05-12 11:39 ` [PATCH v2 3/7] firmware: stratix10-svc: Add initial support for asynchronous communication with Stratix 10 service channel Mahesh Rao via B4 Relay
2025-05-19 11:58 ` Dinh Nguyen
2025-05-21 8:42 ` Mahesh Rao
2025-05-21 20:18 ` Dinh Nguyen [this message]
2025-05-22 10:33 ` Mahesh Rao
2025-05-22 18:47 ` Dinh Nguyen
2025-05-23 9:20 ` Mahesh Rao
2025-05-12 11:39 ` [PATCH v2 4/7] dt-bindings: firmware: Add interrupt specification for Intel Stratix 10 Service Layer Mahesh Rao via B4 Relay
2025-05-12 11:39 ` [PATCH v2 5/7] dts: agilex: Add support for SDM mailbox interrupt for Intel Agilex SoC FPGA Mahesh Rao via B4 Relay
2025-05-21 20:22 ` Dinh Nguyen
2025-05-22 10:37 ` Mahesh Rao
2025-05-12 11:39 ` [PATCH v2 6/7] firmware: stratix10-svc: Add for SDM mailbox doorbell interrupt Mahesh Rao via B4 Relay
2025-05-12 11:39 ` [PATCH v2 7/7] firmware: stratix10-svc: Add support for HWMON temperature and voltage read command Mahesh Rao via B4 Relay
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=40b939d6-9339-444f-a2e4-3e4cd4bcb317@kernel.org \
--to=dinguyen@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.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).