mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yidong Zhang <yidong.zhang@amd.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
	<ogabbay@kernel.org>, <quic_jhugo@quicinc.com>,
	<maciej.falkowski@linux.intel.com>,
	<dri-devel@lists.freedesktop.org>
Cc: <linux-kernel@vger.kernel.org>, <sonal.santan@amd.com>,
	<mario.limonciello@amd.com>, <lizhi.hou@amd.com>,
	Nishad Saraf <nishads@amd.com>
Subject: Re: [PATCH V1 5/5] accel/amd_vpci: Add communication channel service
Date: Wed, 12 Nov 2025 20:53:18 -0800	[thread overview]
Message-ID: <05f478f4-b492-4f4a-8b87-a3224e604702@amd.com> (raw)
In-Reply-To: <2c0da6a9-e766-49be-a679-9d19e5d14992@wanadoo.fr>



On 11/11/25 01:59, Christophe JAILLET wrote:
> Caution: This message originated from an External Source. Use proper 
> caution when opening attachments, clicking links, or responding.
> 
> 
> Le 11/11/2025 à 02:15, David Zhang a écrit :
>> This patch introduces the communication channel (comm_chan) service, 
>> which
>> enables communication between the management PF driver and the user PF
>> driver.
>>
>> The comm_chan service provides a shared-memory-based command channel
>> located in a BAR-mapped region. The user PF driver issues requests by
>> writing command messages into this region. The management PF driver
>> periodically polls the region and process any pending requests.
>>
>> Supported operations include firmware (xclbin) reloads, where the
>> management PF invokes 'versal_pci_load_xclbin' to reprogram the embedded
>> firmware through the remote management queue service.
>>
>> This service provides the foundation for dynamic firmware updates and 
>> other
>> management requests from the user PFs.
>>
>> Co-developed-by: Nishad Saraf <nishads@amd.com>
>> Signed-off-by: Nishad Saraf <nishads@amd.com>
>> Signed-off-by: David Zhang <yidong.zhang@amd.com>
> 
> ...
> 
>> @@ -160,10 +222,13 @@ static const struct config_item_type 
>> versal_pci_cfs_table = {
>>   static int versal_pci_cfs_init(struct versal_pci_device *vdev)
>>   {
>>       struct configfs_subsystem *subsys = &vdev->cfs_subsys;
>> +     char dev_name[64] = "";
> 
> No need to init I think.
> 

Ok, I will fix this.

>> +
>> +     snprintf(dev_name, sizeof(dev_name), "%s%x", DRV_NAME, 
>> versal_pci_devid(vdev));
> 
> This hunk could already be in patch 1. This would make this patch smaller.
> 
>>
>>       snprintf(subsys->su_group.cg_item.ci_namebuf,
>>                sizeof(subsys->su_group.cg_item.ci_namebuf),
>> -              "%s%x", DRV_NAME, versal_pci_devid(vdev));
>> +              "%s", dev_name);
>>
>>       subsys->su_group.cg_item.ci_type = &versal_pci_cfs_table;
>>
> 
> ...

      reply	other threads:[~2025-11-13  4:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-11  1:15 [PATCH V1 0/5] accel/amd_vpci: Add new driver for AMD Versal PCI David Zhang
2025-11-11  1:15 ` [PATCH V1 1/5] accel/amd_vpci: Add documentation for AMD Versal PCI accelerator management David Zhang
2025-11-11  1:15 ` [PATCH V1 2/5] accel/amd_vpci: Add new driver for AMD Versal PCI accelerator David Zhang
2025-11-11  9:38   ` Christophe JAILLET
2025-12-27 19:17     ` Yidong Zhang
2025-11-11  1:15 ` [PATCH V1 3/5] accel/amd_vpci: Add Remote Management(RM) queue infrastructure David Zhang
2025-11-11  9:44   ` Christophe JAILLET
2025-11-13  4:50     ` Yidong Zhang
2025-11-11  1:15 ` [PATCH V1 4/5] accel/amd_vpci: Add Remote Management (RM) queue service APIs David Zhang
2025-11-11  9:51   ` Christophe JAILLET
2025-11-13  4:52     ` Yidong Zhang
2025-11-11  1:15 ` [PATCH V1 5/5] accel/amd_vpci: Add communication channel service David Zhang
2025-11-11  9:59   ` Christophe JAILLET
2025-11-13  4:53     ` Yidong Zhang [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=05f478f4-b492-4f4a-8b87-a3224e604702@amd.com \
    --to=yidong.zhang@amd.com \
    --cc=christophe.jaillet@wanadoo.fr \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhi.hou@amd.com \
    --cc=maciej.falkowski@linux.intel.com \
    --cc=mario.limonciello@amd.com \
    --cc=nishads@amd.com \
    --cc=ogabbay@kernel.org \
    --cc=quic_jhugo@quicinc.com \
    --cc=sonal.santan@amd.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®