From: Rosen Penev <rosenp@gmail.com>
To: linux-usb@vger.kernel.org
Cc: Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mark Brown <broonie@kernel.org>,
Wesley Cheng <quic_wcheng@quicinc.com>,
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH] usb: xhci: sideband: add missing kernel-doc parameters
Date: Wed, 3 Jun 2026 17:04:42 -0700 [thread overview]
Message-ID: <20260604000442.15679-1-rosenp@gmail.com> (raw)
Add @imod_interval and @intr_num to
xhci_sideband_create_interrupter(), and @type and @notify_client
to xhci_sideband_register().
Fixes: de66754e9f80 ("xhci: sideband: add initial api to register a secondary interrupter entity")
Assisted-by: opencode:big-pickle
Signed-off-by: Rosen Penev <rosenp@gmail.com>
---
drivers/usb/host/xhci-sideband.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/usb/host/xhci-sideband.c b/drivers/usb/host/xhci-sideband.c
index 23153e136d4b..d892567079b7 100644
--- a/drivers/usb/host/xhci-sideband.c
+++ b/drivers/usb/host/xhci-sideband.c
@@ -308,6 +308,8 @@ EXPORT_SYMBOL_GPL(xhci_sideband_check);
* @sb: sideband instance for this usb device
* @num_seg: number of event ring segments to allocate
* @ip_autoclear: IP autoclearing support such as MSI implemented
+ * @imod_interval: interrupt moderation interval
+ * @intr_num: interrupter number
*
* Sets up a xhci interrupter that can be used for this sideband accessed usb
* device. Transfer events for this device can be routed to this interrupters
@@ -389,6 +391,8 @@ EXPORT_SYMBOL_GPL(xhci_sideband_interrupter_id);
/**
* xhci_sideband_register - register a sideband for a usb device
* @intf: usb interface associated with the sideband device
+ * @type: sideband type
+ * @notify_client: callback for notifying the client of events
*
* Allows for clients to utilize XHCI interrupters and fetch transfer and event
* ring parameters for executing data transfers.
--
2.54.0
reply other threads:[~2026-06-04 0:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260604000442.15679-1-rosenp@gmail.com \
--to=rosenp@gmail.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=quic_wcheng@quicinc.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