From: Greg KH <gregkh@linuxfoundation.org>
To: raoxu <raoxu@uniontech.com>
Cc: kenny@panix.com, linux-usb@vger.kernel.org,
mathias.nyman@linux.intel.com, michal.pecio@gmail.com,
niklas.neronin@linux.intel.com, zhanjun@uniontech.com
Subject: Re: [PATCH v10 1/2] usb: xhci: refactor IRQ/interrupter plumbing for
Date: Mon, 26 Jan 2026 10:06:23 +0100 [thread overview]
Message-ID: <2026012607-seducing-serotonin-f0fc@gregkh> (raw)
In-Reply-To: <0D5BB0174F3D24D9+20260126085812.803496-1-raoxu@uniontech.com>
On Mon, Jan 26, 2026 at 04:58:12PM +0800, raoxu wrote:
> Prepare xHCI for multiple IRQ vectors/interrupters without changing the
> current behavior.
>
> Introduce a per-vector irq context (hcd + intr_num) to use as request_irq()
> dev_id, and track the active vector count in xhci->irqs_enabled. Use this
> single bound to enable/disable interrupters consistently across run/stop/
> resume and to sync/free IRQs.
>
> Legacy IRQ fallback also keeps irqs_enabled >= 1 so interrupter 0 remains
> functional when MSI/MSI-X is unavailable.
>
> No functional change intended: still uses interrupter 0 only.
>
> Signed-off-by: raoxu <raoxu@uniontech.com>
We need a real name, not an email alias please.
thanks,
greg k-h
next prev parent reply other threads:[~2026-01-26 9:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-26 8:55 [PATCH v10 0/2] usb:xhc:route device to secondary interrupters raoxu
2026-01-26 8:58 ` [PATCH v10 1/2] usb: xhci: refactor IRQ/interrupter plumbing for raoxu
2026-01-26 9:06 ` Greg KH [this message]
2026-01-26 8:58 ` [PATCH v10 2/2] usb: xhci: enable secondary interrupters and route raoxu
2026-01-26 9:10 ` Greg KH
2026-01-26 14:49 ` kernel test robot
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=2026012607-seducing-serotonin-f0fc@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=kenny@panix.com \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=michal.pecio@gmail.com \
--cc=niklas.neronin@linux.intel.com \
--cc=raoxu@uniontech.com \
--cc=zhanjun@uniontech.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