From: Jeffrey Hugo <quic_jhugo@quicinc.com>
To: Lizhi Hou <lizhi.hou@amd.com>, <ogabbay@kernel.org>,
<dri-devel@lists.freedesktop.org>
Cc: <linux-kernel@vger.kernel.org>, <min.ma@amd.com>,
<max.zhen@amd.com>, <sonal.santan@amd.com>, <king.tam@amd.com>,
George Yang <George.Yang@amd.com>
Subject: Re: [PATCH V3 03/11] accel/amdxdna: Support hardware mailbox
Date: Mon, 7 Oct 2024 09:34:58 -0600 [thread overview]
Message-ID: <38be2c5c-8543-968b-e91e-a7f485909171@quicinc.com> (raw)
In-Reply-To: <7e337655-a0ff-0c9f-f074-35ca61b0d934@amd.com>
On 10/6/2024 10:15 PM, Lizhi Hou wrote:
>
> On 10/4/24 10:34, Jeffrey Hugo wrote:
>> On 9/11/2024 12:05 PM, Lizhi Hou wrote:
>>> +struct create_ctx_req {
>>> + __u32 aie_type;
>>> + __u8 start_col;
>>> + __u8 num_col;
>>> + __u16 reserved;
>>> + __u8 num_cq_pairs_requested;
>>> + __u8 reserved1;
>>> + __u16 pasid;
>>> + __u32 pad[2];
>>> + __u32 sec_comm_target_type;
>>> + __u32 context_priority;
>>
>> Alignment
> Will fix it.
>>
>>> +} __packed;
>>> +
>>> +struct create_ctx_resp {
>>> + enum aie2_msg_status status;
>>> + __u32 context_id;
>>> + __u16 msix_id;
>>> + __u8 num_cq_pairs_allocated;
>>> + __u8 reserved;
>>> + struct cq_pair cq_pair[MAX_CQ_PAIRS];
>>> +} __packed;
>>> +
>>> +struct destroy_ctx_req {
>>> + __u32 context_id;
>>> +} __packed;
>>> +
>>> +struct destroy_ctx_resp {
>>> + enum aie2_msg_status status;
>>> +} __packed;
>>> +
>>> +struct execute_buffer_req {
>>> + __u32 cu_idx;
>>> + __u32 payload[19];
>>> +} __packed;
>>> +
>>> +struct exec_dpu_req {
>>> + __u64 inst_buf_addr;
>>> + __u32 inst_size;
>>> + __u32 inst_prop_cnt;
>>> + __u32 cu_idx;
>>
>> Alignment
> will fix it.
>>
>>> + __u32 payload[35];
>>> +} __packed;
>>> +
>>> diff --git a/drivers/accel/amdxdna/aie2_psp.c
>>> b/drivers/accel/amdxdna/aie2_psp.c
>>> index c87ca322e206..ac5296f4f2ae 100644
>>> --- a/drivers/accel/amdxdna/aie2_psp.c
>>> +++ b/drivers/accel/amdxdna/aie2_psp.c
>>> @@ -8,6 +8,8 @@
>>> #include <drm/drm_print.h>
>>> #include <linux/iopoll.h>
>>> +#include "amdxdna_mailbox.h"
>>> +#include "amdxdna_pci_drv.h"
>>> #include "aie2_pci.h"
>>
>> Doesn't look like alphabetical order to me. Also similar instances in
>> the *_regs.c files below
>
> aie2 is one type of amdxdna hw platform. I would put amdxdna_*.h ahead
> of aie_*.h. Otherwise I probably need to add include in aie2_*.h. Is it
> acceptable reason? Or I must use alphabetical for #include?
Sorting the includes is part of the Linux coding style, and the current
style document mentions using clang-format for ordering them (in
alphabetical order). Requesting ordered includes is common feedback per
Lore.
Relying on include ordering seems very fragile.
-Jeff
next prev parent reply other threads:[~2024-10-07 15:35 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-11 18:05 [PATCH V3 00/11] AMD XDNA driver Lizhi Hou
2024-09-11 18:05 ` [PATCH V3 01/11] accel/amdxdna: Add documentation for AMD NPU accelerator driver Lizhi Hou
2024-10-04 17:06 ` Jeffrey Hugo
2024-10-05 0:27 ` Lizhi Hou
2024-09-11 18:05 ` [PATCH V3 02/11] accel/amdxdna: Add a new driver for AMD AI Engine Lizhi Hou
2024-10-04 17:21 ` Jeffrey Hugo
2024-10-07 4:01 ` Lizhi Hou
2024-09-11 18:05 ` [PATCH V3 03/11] accel/amdxdna: Support hardware mailbox Lizhi Hou
2024-10-04 17:34 ` Jeffrey Hugo
2024-10-07 4:15 ` Lizhi Hou
2024-10-07 15:34 ` Jeffrey Hugo [this message]
2024-09-11 18:05 ` [PATCH V3 04/11] accel/amdxdna: Add hardware resource solver Lizhi Hou
2024-10-04 17:36 ` Jeffrey Hugo
2024-09-11 18:05 ` [PATCH V3 05/11] accel/amdxdna: Add hardware context Lizhi Hou
2024-10-04 17:50 ` Jeffrey Hugo
2024-10-07 5:02 ` Lizhi Hou
2024-10-07 15:37 ` Jeffrey Hugo
2024-09-11 18:05 ` [PATCH V3 06/11] accel/amdxdna: Add GEM buffer object management Lizhi Hou
2024-09-14 14:07 ` kernel test robot
2024-10-04 17:56 ` Jeffrey Hugo
2024-10-07 22:35 ` Lizhi Hou
2024-09-11 18:06 ` [PATCH V3 07/11] accel/amdxdna: Add command execution Lizhi Hou
2024-10-04 18:01 ` Jeffrey Hugo
2024-10-07 22:51 ` Lizhi Hou
2024-09-11 18:06 ` [PATCH V3 08/11] accel/amdxdna: Add suspend and resume Lizhi Hou
2024-10-04 18:08 ` Jeffrey Hugo
2024-10-08 5:52 ` Lizhi Hou
2024-09-11 18:06 ` [PATCH V3 09/11] accel/amdxdna: Add error handling Lizhi Hou
2024-10-04 18:20 ` Jeffrey Hugo
2024-09-11 18:06 ` [PATCH V3 10/11] accel/amdxdna: Add query functions Lizhi Hou
2024-10-04 18:23 ` Jeffrey Hugo
2024-10-09 16:19 ` Lizhi Hou
2024-09-11 18:06 ` [PATCH V3 11/11] accel/amdxdna: Add firmware debug buffer support Lizhi Hou
2024-10-04 18:33 ` Jeffrey Hugo
2024-10-09 16:22 ` Lizhi Hou
2024-10-09 23:51 ` Lizhi Hou
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=38be2c5c-8543-968b-e91e-a7f485909171@quicinc.com \
--to=quic_jhugo@quicinc.com \
--cc=George.Yang@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=king.tam@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.hou@amd.com \
--cc=max.zhen@amd.com \
--cc=min.ma@amd.com \
--cc=ogabbay@kernel.org \
--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®