From: Frank Li <Frank.li@oss.nxp.com>
To: Nathan Lynch <nathan.lynch@amd.com>
Cc: Vinod Koul <vkoul@kernel.org>, Frank Li <Frank.Li@kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
David Rientjes <rientjes@google.com>,
John.Kariuki@amd.com, Jonathan Cameron <jic23@kernel.org>,
Kinsey Ho <kinseyho@google.com>,
Mario Limonciello <mario.limonciello@amd.com>,
PradeepVineshReddy.Kodamati@amd.com,
Shivank Garg <shivankg@amd.com>,
Stephen Bates <Stephen.Bates@amd.com>,
Tycho Andersen <tycho@kernel.org>, Wei Huang <wei.huang2@amd.com>,
Wei Xu <weixugc@google.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH v4 18/25] dmaengine: sdxi: Add context submission helper
Date: Fri, 13 Nov 2026 12:12:13 -0500 [thread overview]
Message-ID: <avdE7dckg2azmum3@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20261103-sdxi-base-v4-18-3668ccc7aab8@amd.com>
On Tue, Nov 03, 2026 at 08:49:59PM -0600, Nathan Lynch wrote:
> Add sdxi_cxt_submit() to consolidate optional fence and completion-status
> block setup, valid-bit publication, and doorbell ringing. An optional
> struct sdxi_completion input identifies storage already claimed and
> initialized by the caller.
>
> Introduce generic descriptor helpers for attaching completion storage,
> setting completion-status mode, fencing, and publishing the valid bit.
> Publishing orders prior descriptor writes before transferring ownership
> to hardware; the helpers warn if a caller attempts to modify an already
> valid descriptor.
>
> Provide sdxi_cxt_attach_cst() for attaching completion storage without
> publishing the descriptor, and sdxi_cxt_kick() for ringing a context
> doorbell.
>
> Co-developed-by: Wei Huang <wei.huang2@amd.com>
> Signed-off-by: Wei Huang <wei.huang2@amd.com>
> Signed-off-by: Nathan Lynch <nathan.lynch@amd.com>
> ---
> drivers/dma/sdxi/context.c | 36 ++++++++++++++++++++++++
> drivers/dma/sdxi/context.h | 28 +++++++++++++++++++
> drivers/dma/sdxi/descriptor.h | 64 +++++++++++++++++++++++++++++++++++++++++++
> drivers/dma/sdxi/hw.h | 10 +++++++
> 4 files changed, 138 insertions(+)
>
> diff --git a/drivers/dma/sdxi/context.c b/drivers/dma/sdxi/context.c
> index 60cc812df204..679c5cfab19d 100644
> --- a/drivers/dma/sdxi/context.c
> +++ b/drivers/dma/sdxi/context.c
> @@ -24,6 +24,7 @@
>
> #include "completion.h"
> #include "context.h"
> +#include "descriptor.h"
> #include "hw.h"
> #include "ring.h"
> #include "sdxi.h"
> @@ -362,3 +363,38 @@ void sdxi_client_cxts_exit(struct sdxi_dev *sdxi)
> sdxi_free_cxt(cxt);
> xa_destroy(&sdxi->client_cxts);
> }
> +
> +/*
> + * Attach a claimed, initialized completion block to a descriptor slot.
> + * The descriptor is not published; the caller sets the valid bit (and
> + * kicks) once the operation is fully encoded.
> + */
> +void sdxi_cxt_attach_cst(struct sdxi_slot slot,
> + const struct sdxi_completion *comp)
> +{
> + struct sdxi_desc *desc = sdxi_slot_desc(slot);
> +
> + /*
> + * We use simple (non-atomic) completion status mode only; set the
> + * descriptor's CSR bit. See SDXI 1.0 4.4.2 Completion-Status Modes.
> + */
> + sdxi_desc_set_csr(desc);
> + sdxi_desc_set_csb(desc, comp->cst_blk_dma);
> +}
> +
> +void sdxi_cxt_submit(struct sdxi_cxt *cxt, struct sdxi_slot slot,
> + const struct sdxi_completion *comp, enum sdxi_submit_flags flags)
> +{
> + struct sdxi_desc *desc = sdxi_slot_desc(slot);
> +
> + if (flags & SDXI_CXT_SUBMIT_FENCE)
> + sdxi_desc_set_fence(desc);
> +
> + if (comp)
> + sdxi_cxt_attach_cst(slot, comp);
> +
> + sdxi_desc_make_valid(desc);
> +
> + if (flags & SDXI_CXT_SUBMIT_KICK)
> + sdxi_cxt_kick(cxt);
> +}
> diff --git a/drivers/dma/sdxi/context.h b/drivers/dma/sdxi/context.h
> index 94e0fc45f281..f048e298f6de 100644
> --- a/drivers/dma/sdxi/context.h
> +++ b/drivers/dma/sdxi/context.h
> @@ -9,10 +9,12 @@
> #include <linux/array_size.h>
> #include <linux/dma-mapping.h>
> #include <linux/idr.h>
> +#include <linux/io.h>
> #include <linux/string.h>
> #include <linux/types.h>
>
> #include "hw.h"
> +#include "ring.h"
> #include "sdxi.h"
> #include "submission.h"
>
> @@ -52,6 +54,16 @@ int sdxi_admin_cxt_init(struct sdxi_dev *sdxi);
> struct sdxi_cxt *sdxi_cxt_new(struct sdxi_dev *sdxi);
> void sdxi_client_cxts_exit(struct sdxi_dev *sdxi);
>
> +enum sdxi_submit_flags {
> + SDXI_CXT_SUBMIT_KICK = BIT(0),
> + SDXI_CXT_SUBMIT_FENCE = BIT(1),
> +};
> +
> +void sdxi_cxt_attach_cst(struct sdxi_slot slot,
> + const struct sdxi_completion *comp);
> +void sdxi_cxt_submit(struct sdxi_cxt *cxt, struct sdxi_slot slot,
> + const struct sdxi_completion *comp, enum sdxi_submit_flags flags);
> +
> static inline struct sdxi_cxt *to_admin_cxt(const struct sdxi_cxt *cxt)
> {
> return cxt->sdxi->admin_cxt;
> @@ -62,6 +74,22 @@ static inline bool sdxi_cxt_is_admin(const struct sdxi_cxt *cxt)
> return cxt == to_admin_cxt(cxt);
> }
>
> +static inline void sdxi_cxt_kick(struct sdxi_cxt *cxt)
> +{
> + /*
> + * Ring the context's doorbell with its current write index.
> + *
> + * It's OK to locklessly sample the index for this purpose: it
> + * monotonically increases and the implementation is required
> + * to ignore out-of-order doorbell values (SDXI 1.0 5.2.1
> + * Multi-Producer Enqueue).
> + *
> + * writeq() orders the descriptors' valid bits ahead of the
> + * doorbell, so no explicit barrier is needed here.
> + */
> + writeq(le64_to_cpu(READ_ONCE(cxt->sq->write_index)), cxt->sq->doorbell);
> +}
> +
> static inline struct sdxi_akey_ent *sdxi_alloc_akey(struct sdxi_cxt *cxt)
> {
> unsigned int max = ARRAY_SIZE(cxt->akey_table->entry) - 1;
> diff --git a/drivers/dma/sdxi/descriptor.h b/drivers/dma/sdxi/descriptor.h
> new file mode 100644
> index 000000000000..b19d5d329e43
> --- /dev/null
> +++ b/drivers/dma/sdxi/descriptor.h
> @@ -0,0 +1,64 @@
> +/* SPDX-License-Identifier: GPL-2.0-only */
> +#ifndef DMA_SDXI_DESCRIPTOR_H
> +#define DMA_SDXI_DESCRIPTOR_H
> +
> +/*
> + * Facilities for encoding SDXI descriptors.
> + *
> + * Copyright Advanced Micro Devices, Inc.
> + */
> +
> +#include <linux/bitfield.h>
> +#include <linux/ratelimit.h>
> +#include <linux/types.h>
> +#include <asm/byteorder.h>
> +
> +#include "hw.h"
> +
> +static inline void sdxi_desc_vl_expect(const struct sdxi_desc *desc, bool expected)
> +{
> + u8 vl = FIELD_GET(SDXI_DSC_VL, le32_to_cpu(desc->opcode));
> +
> + WARN_RATELIMIT(vl != expected, "expected vl=%u but got %u\n", expected, vl);
> +}
> +
> +static inline void sdxi_desc_set_csb(struct sdxi_desc *desc, dma_addr_t addr)
> +{
> + sdxi_desc_vl_expect(desc, 0);
> + desc->csb_ptr = cpu_to_le64(FIELD_PREP(SDXI_DSC_CSB_PTR, addr >> 5));
> +}
> +
> +static inline void sdxi_desc_make_valid(struct sdxi_desc *desc)
> +{
> + u32 opcode = le32_to_cpu(desc->opcode);
> +
> + sdxi_desc_vl_expect(desc, 0);
> + FIELD_MODIFY(SDXI_DSC_VL, &opcode, 1);
> + /*
> + * Once vl is set, no more modifications to the descriptor
> + * payload are allowed. Ensure the vl update is ordered after
> + * all other initialization of the descriptor.
> + */
> + dma_wmb();
> + WRITE_ONCE(desc->opcode, cpu_to_le32(opcode));
> +}
> +
> +static inline void sdxi_desc_set_fence(struct sdxi_desc *desc)
> +{
> + u32 opcode = le32_to_cpu(desc->opcode);
> +
> + sdxi_desc_vl_expect(desc, 0);
> + FIELD_MODIFY(SDXI_DSC_FE, &opcode, 1);
why no dma_wmb() here?
Frank
> + desc->opcode = cpu_to_le32(opcode);
> +}
> +
> +static inline void sdxi_desc_set_csr(struct sdxi_desc *desc)
> +{
> + u32 opcode = le32_to_cpu(desc->opcode);
> +
> + sdxi_desc_vl_expect(desc, 0);
> + FIELD_MODIFY(SDXI_DSC_CSR, &opcode, 1);
> + desc->opcode = cpu_to_le32(opcode);
> +}
> +
> +#endif /* DMA_SDXI_DESCRIPTOR_H */
> diff --git a/drivers/dma/sdxi/hw.h b/drivers/dma/sdxi/hw.h
> index c1bff631a5ae..edc43190148c 100644
> --- a/drivers/dma/sdxi/hw.h
> +++ b/drivers/dma/sdxi/hw.h
> @@ -136,6 +136,16 @@ struct sdxi_desc {
> __u8 operation[52];
> __le64 csb_ptr;
> );
> +
> +/* For opcode field */
> +#define SDXI_DSC_VL BIT(0)
> +#define SDXI_DSC_SE BIT(1)
> +#define SDXI_DSC_FE BIT(2)
> +#define SDXI_DSC_CSR BIT(4)
> +
> +/* For csb_ptr field */
> +#define SDXI_DSC_CSB_PTR GENMASK_ULL(63, 5)
> +
> };
> } __packed __aligned(64);
> static_assert(sizeof(struct sdxi_desc) == 64);
>
> --
> 2.56.0
>
next prev parent reply other threads:[~2026-11-13 17:12 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 2:49 [PATCH v4 00/25] dmaengine: Smart Data Accelerator Interface (SDXI) basic support Nathan Lynch via B4 Relay
2026-11-04 2:49 ` [PATCH v4 01/25] PCI: Add SNIA SDXI accelerator sub-class Nathan Lynch via B4 Relay
2026-11-05 18:10 ` Frank Li
2026-11-05 18:25 ` Lynch, Nathan
2026-11-12 21:28 ` Bjorn Helgaas
2026-11-04 2:49 ` [PATCH v4 02/25] MAINTAINERS: Add entry for SDXI driver Nathan Lynch via B4 Relay
2026-11-12 21:19 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 03/25] dmaengine: sdxi: Add PCI initialization Nathan Lynch via B4 Relay
2026-11-05 17:59 ` Frank Li
2026-11-05 18:07 ` Lynch, Nathan
2026-11-04 2:49 ` [PATCH v4 04/25] dmaengine: sdxi: Prepare function and sanitize MMIO state Nathan Lynch via B4 Relay
2026-11-12 21:26 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 05/25] dmaengine: sdxi: Feature discovery and initial configuration Nathan Lynch via B4 Relay
2026-11-12 21:32 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 06/25] dmaengine: sdxi: Configure context tables Nathan Lynch via B4 Relay
2026-11-12 21:49 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 07/25] dmaengine: sdxi: Allocate context control DMA pool Nathan Lynch via B4 Relay
2026-11-12 21:50 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 08/25] dmaengine: sdxi: Introduce submission queue Nathan Lynch via B4 Relay
2026-11-12 21:58 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 09/25] dmaengine: sdxi: Allocate administrative context Nathan Lynch via B4 Relay
2026-11-12 22:10 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 10/25] dmaengine: sdxi: Install " Nathan Lynch via B4 Relay
2026-11-12 22:17 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 11/25] dmaengine: sdxi: Start functions on probe, stop on remove Nathan Lynch via B4 Relay
2026-11-13 16:44 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 12/25] dmaengine: sdxi: Add client context allocation API Nathan Lynch via B4 Relay
2026-11-13 16:46 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 13/25] dmaengine: sdxi: Add descriptor ring management Nathan Lynch via B4 Relay
2026-11-13 16:51 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 14/25] dmaengine: sdxi: Add unit tests for descriptor ring reservations Nathan Lynch via B4 Relay
2026-11-13 16:53 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 15/25] dmaengine: sdxi: Per-context access key (AKey) table entry allocator Nathan Lynch via B4 Relay
2026-11-13 16:55 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 16/25] dmaengine: sdxi: Add completion status block API Nathan Lynch via B4 Relay
2026-11-13 17:04 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 17/25] dmaengine: sdxi: Add unit tests for completion pool ownership Nathan Lynch via B4 Relay
2026-11-13 17:07 ` Frank Li
2026-11-04 2:49 ` [PATCH v4 18/25] dmaengine: sdxi: Add context submission helper Nathan Lynch via B4 Relay
2026-11-13 17:12 ` Frank Li [this message]
2026-11-04 2:50 ` [PATCH v4 19/25] dmaengine: sdxi: Encode context start, stop, update, and sync descriptors Nathan Lynch via B4 Relay
2026-11-05 16:52 ` Tycho Andersen
2026-11-13 17:17 ` Frank Li
2026-11-04 2:50 ` [PATCH v4 20/25] dmaengine: sdxi: Add client context release with update and sync Nathan Lynch via B4 Relay
2026-11-13 17:23 ` Frank Li
2026-11-04 2:50 ` [PATCH v4 21/25] dmaengine: sdxi: Provide context start and stop APIs Nathan Lynch via B4 Relay
2026-11-13 17:24 ` Frank Li
2026-11-04 2:50 ` [PATCH v4 22/25] dmaengine: sdxi: Encode copy and interrupt descriptors Nathan Lynch via B4 Relay
2026-11-05 17:00 ` Tycho Andersen
2026-11-13 17:28 ` Frank Li
2026-11-04 2:50 ` [PATCH v4 23/25] dmaengine: sdxi: Add unit tests for descriptor encoding Nathan Lynch via B4 Relay
2026-11-13 17:29 ` Frank Li
2026-11-04 2:50 ` [PATCH v4 24/25] dmaengine: sdxi: MSI/MSI-X vector allocation and mapping Nathan Lynch via B4 Relay
2026-11-13 17:36 ` Frank Li
2026-11-04 2:50 ` [PATCH v4 25/25] dmaengine: sdxi: Add DMA engine provider Nathan Lynch via B4 Relay
2026-11-13 17:50 ` Frank Li
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=avdE7dckg2azmum3@lizhi-Precision-Tower-5810 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=John.Kariuki@amd.com \
--cc=PradeepVineshReddy.Kodamati@amd.com \
--cc=Stephen.Bates@amd.com \
--cc=bhelgaas@google.com \
--cc=dmaengine@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=kinseyho@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=nathan.lynch@amd.com \
--cc=rientjes@google.com \
--cc=shivankg@amd.com \
--cc=tycho@kernel.org \
--cc=vkoul@kernel.org \
--cc=wei.huang2@amd.com \
--cc=weixugc@google.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®