From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Yidong Zhang <yidong.zhang@amd.com>,
linux-kernel@vger.kernel.org, linux-fpga@vger.kernel.org,
mdf@kernel.org, hao.wu@intel.com, yilun.xu@intel.com
Cc: lizhi.hou@amd.com, Nishad Saraf <nishads@amd.com>
Subject: Re: [PATCH V2 2/4] drivers/fpga/amd: Add communication channel
Date: Sun, 26 Jan 2025 11:19:29 +0100 [thread overview]
Message-ID: <f35c40fc-7afa-4fef-bab2-0b30302b9b21@wanadoo.fr> (raw)
In-Reply-To: <20241210183734.30803-3-yidong.zhang@amd.com>
Le 10/12/2024 à 19:37, Yidong Zhang a écrit :
> The communication channel (comm_chan) service is between versal-pci and the
> user PF driver. When the user PF driver requests PL data download, the
> comm_chan service will handle the request by versal_pci_load_xclbin.
...
> +enum comm_chan_req_ops {
> + COMM_CHAN_REQ_OPS_UNKNOWN = 0,
> + COMM_CHAN_REQ_OPS_HOT_RESET = 5,
> + COMM_CHAN_REQ_OPS_GET_PROTOCOL_VERSION = 19,
> + COMM_CHAN_REQ_OPS_LOAD_XCLBIN_UUID = 20,
> + COMM_CHAN_REQ_OPS_MAX,
Unneeded comma after a terminator.
> +};
...
> +static void comm_chan_check_request(struct work_struct *w)
> +{
> + struct comm_chan_device *ccdev = to_ccdev_work(w);
> + u32 status = 0, request[COMM_CHAN_DATA_LEN] = {0};
These 2 initialisations are not needed.
> + struct comm_chan_hw_msg *hw_msg;
> + u8 type, eom;
> + int i;
> +
> + status = comm_chan_read(ccdev, COMM_CHAN_REG_IS_OFF);
> + if (!STATUS_IS_READY(status))
> + return;
> + if (STATUS_IS_ERROR(status)) {
> + vdev_err(ccdev->vdev, "An error has occurred with comms");
> + return;
> + }
> +
> + /* ACK status */
> + comm_chan_write(ccdev, COMM_CHAN_REG_IS_OFF, status);
> +
> + for (i = 0; i < COMM_CHAN_DATA_LEN; i++)
> + request[i] = comm_chan_read(ccdev, COMM_CHAN_REG_RDDATA_OFF);
> +
...
CJ
next prev parent reply other threads:[~2025-01-26 10:20 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 18:37 [PATCH V2 0/4] Add versal-pci driver Yidong Zhang
2024-12-10 18:37 ` [PATCH V2 1/4] drivers/fpga/amd: Add new driver amd versal-pci Yidong Zhang
2025-01-26 9:24 ` Xu Yilun
2025-01-26 19:50 ` Yidong Zhang
2025-01-26 10:12 ` Christophe JAILLET
2025-01-26 19:56 ` Yidong Zhang
2025-01-26 10:16 ` Christophe JAILLET
2025-01-26 10:32 ` Xu Yilun
2025-01-26 19:46 ` Yidong Zhang
2025-02-06 4:15 ` Xu Yilun
2025-02-06 4:31 ` Yidong Zhang
2025-02-07 2:19 ` Xu Yilun
2025-02-07 3:16 ` Yidong Zhang
2025-02-07 4:40 ` Xu Yilun
2025-02-10 11:33 ` Yidong Zhang
2025-02-11 9:09 ` Xu Yilun
2025-02-11 11:31 ` Yidong Zhang
2025-03-01 8:20 ` Xu Yilun
2025-03-01 19:03 ` Yidong Zhang
2025-03-03 7:57 ` Xu Yilun
2025-03-03 17:00 ` Yidong Zhang
2024-12-10 18:37 ` [PATCH V2 2/4] drivers/fpga/amd: Add communication channel Yidong Zhang
2025-01-26 10:19 ` Christophe JAILLET [this message]
2025-01-26 19:57 ` Yidong Zhang
2024-12-10 18:37 ` [PATCH V2 3/4] drivers/fpga/amd: Add remote queue Yidong Zhang
2025-01-26 10:24 ` Christophe JAILLET
2024-12-10 18:37 ` [PATCH V2 4/4] drivers/fpga/amd: Add load xclbin and load firmware Yidong Zhang
2025-01-26 9:27 ` [PATCH V2 0/4] Add versal-pci driver Xu Yilun
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=f35c40fc-7afa-4fef-bab2-0b30302b9b21@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=mdf@kernel.org \
--cc=nishads@amd.com \
--cc=yidong.zhang@amd.com \
--cc=yilun.xu@intel.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;
as well as URLs for NNTP newsgroup(s).