From: sashiko-bot@kernel.org
To: "Nathan Lynch" <nathan.lynch@amd.com>
Cc: dmaengine@vger.kernel.org, linux-pci@vger.kernel.org,
vkoul@kernel.org, Frank.Li@kernel.org
Subject: Re: [PATCH v4 24/25] dmaengine: sdxi: MSI/MSI-X vector allocation and mapping
Date: Wed, 04 Nov 2026 03:15:50 +0000 [thread overview]
Message-ID: <sashiko-outbox-196592@kernel.org> (raw)
In-Reply-To: <20261103-sdxi-base-v4-24-3668ccc7aab8@amd.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dmaengine: sdxi: incomplete kernel-doc comments in sdxi.h
--
commit fccd22f95bf4bdc550267ac2709b80e00e1e9267
Author: Nathan Lynch <nathan.lynch@amd.com>
dmaengine: sdxi: MSI/MSI-X vector allocation and mapping
This commit allocates MSI/MSI-X vectors for the SDXI error log interrupt
and client contexts, tracking non-reserved vectors with an IDA. It also
adds helpers to allocate, free, and map device-relative vector indices to
Linux IRQ numbers via a new get_irq bus operation.
> diff --git a/drivers/dma/sdxi/sdxi.h b/drivers/dma/sdxi/sdxi.h
> index aaa43eab00b33..07044d837d9af 100644
> --- a/drivers/dma/sdxi/sdxi.h
> +++ b/drivers/dma/sdxi/sdxi.h
[ ... ]
> @@ -69,6 +90,38 @@ struct sdxi_dev {
> const struct sdxi_bus_ops *bus_ops;
> };
>
> +/**
> + * sdxi_alloc_vector() - Allocate an interrupt vector.
> + *
> + * A vector that will have the same lifetime as the device does not
> + * need to be released explicitly. Otherwise the vector must be
> + * released with sdxi_free_vector().
> + */
> +static inline int sdxi_alloc_vector(struct sdxi_dev *sdxi)
> +{
> + return ida_alloc_range(&sdxi->vectors, SDXI_MIN_VECTORS,
> + sdxi->nr_vectors - 1, GFP_KERNEL);
> +}
> +
> +/**
> + * sdxi_free_vector() - Release a previously allocated index.
> + */
> +static inline void sdxi_free_vector(struct sdxi_dev *sdxi, unsigned int nr)
> +{
> + ida_free(&sdxi->vectors, nr);
> +}
> +
> +/**
> + * sdxi_vector_to_irq() - Translate an allocated interrupt vector to
> + * Linux IRQ number suitable for passing to
> + * request_irq() et al.
> + */
> +static inline int sdxi_vector_to_irq(struct sdxi_dev *sdxi, unsigned int nr)
> +{
> + WARN_ON_ONCE(!ida_exists(&sdxi->vectors, nr));
> + return sdxi->bus_ops->get_irq(sdxi, nr);
> +}
[Severity: Low]
sdxi_alloc_vector(), sdxi_free_vector(), and sdxi_vector_to_irq() in
drivers/dma/sdxi/sdxi.h use the /** kernel-doc comment marker without
describing the @sdxi and @nr parameters or including Return: sections for
sdxi_alloc_vector() and sdxi_vector_to_irq().
Running scripts/kernel-doc on drivers/dma/sdxi/sdxi.h (for example via
make HEADER_CHECK=drivers/dma/sdxi headercheck) emits kernel-doc warnings
for the undescribed parameters and missing return value descriptions.
Should these comments document @sdxi, @nr, and Return:, or use regular /*
comments instead?
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103-sdxi-base-v4-0-3668ccc7aab8@amd.com?part=24
next prev parent reply other threads:[~2026-11-04 3:15 UTC|newest]
Thread overview: 82+ 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
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:49 ` [PATCH v4 01/25] PCI: Add SNIA SDXI accelerator sub-class Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:55 ` sashiko-bot
2026-11-05 18:10 ` Frank Li
2026-11-05 18:25 ` Lynch, Nathan
2026-11-04 2:49 ` [PATCH v4 02/25] MAINTAINERS: Add entry for SDXI driver Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:49 ` [PATCH v4 03/25] dmaengine: sdxi: Add PCI initialization Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:56 ` sashiko-bot
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
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:06 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 05/25] dmaengine: sdxi: Feature discovery and initial configuration Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:54 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 06/25] dmaengine: sdxi: Configure context tables Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:55 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 07/25] dmaengine: sdxi: Allocate context control DMA pool Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:54 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 08/25] dmaengine: sdxi: Introduce submission queue Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:56 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 09/25] dmaengine: sdxi: Allocate administrative context Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:56 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 10/25] dmaengine: sdxi: Install " Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:58 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 11/25] dmaengine: sdxi: Start functions on probe, stop on remove Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:04 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 12/25] dmaengine: sdxi: Add client context allocation API Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:02 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 13/25] dmaengine: sdxi: Add descriptor ring management Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:08 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 14/25] dmaengine: sdxi: Add unit tests for descriptor ring reservations Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:02 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 15/25] dmaengine: sdxi: Per-context access key (AKey) table entry allocator Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:59 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 16/25] dmaengine: sdxi: Add completion status block API Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 2:59 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 17/25] dmaengine: sdxi: Add unit tests for completion pool ownership Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:00 ` sashiko-bot
2026-11-04 2:49 ` [PATCH v4 18/25] dmaengine: sdxi: Add context submission helper Nathan Lynch
2026-11-04 2:49 ` Nathan Lynch via B4 Relay
2026-11-04 3:01 ` sashiko-bot
2026-11-04 2:50 ` [PATCH v4 19/25] dmaengine: sdxi: Encode context start, stop, update, and sync descriptors Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:01 ` sashiko-bot
2026-11-05 16:52 ` Tycho Andersen
2026-11-04 2:50 ` [PATCH v4 20/25] dmaengine: sdxi: Add client context release with update and sync Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:12 ` sashiko-bot
2026-11-04 2:50 ` [PATCH v4 21/25] dmaengine: sdxi: Provide context start and stop APIs Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:04 ` sashiko-bot
2026-11-04 2:50 ` [PATCH v4 22/25] dmaengine: sdxi: Encode copy and interrupt descriptors Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:07 ` sashiko-bot
2026-11-05 17:00 ` Tycho Andersen
2026-11-04 2:50 ` [PATCH v4 23/25] dmaengine: sdxi: Add unit tests for descriptor encoding Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:05 ` sashiko-bot
2026-11-04 2:50 ` [PATCH v4 24/25] dmaengine: sdxi: MSI/MSI-X vector allocation and mapping Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:15 ` sashiko-bot [this message]
2026-11-04 2:50 ` [PATCH v4 25/25] dmaengine: sdxi: Add DMA engine provider Nathan Lynch
2026-11-04 2:50 ` Nathan Lynch via B4 Relay
2026-11-04 3:24 ` sashiko-bot
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=sashiko-outbox-196592@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=Frank.Li@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nathan.lynch@amd.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=vkoul@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.