From: "Neronin, Niklas" <niklas.neronin@linux.intel.com>
To: raoxu <raoxu@uniontech.com>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
mathias.nyman@linux.intel.com, michal.pecio@gmail.com
Subject: Re: [PATCH 3/4] usb: xhci-pci: use the interrupter entry as MSI dev_id
Date: Tue, 5 May 2026 12:53:48 +0300 [thread overview]
Message-ID: <131c6e0f-59bc-4d41-9314-3539681f88e0@linux.intel.com> (raw)
In-Reply-To: <85CC13362072C2B0+20260430064208.1725201-1-raoxu@uniontech.com>
On 30/04/2026 9.42, raoxu wrote:
> From: Xu Rao <raoxu@uniontech.com>
>
> After routing xhci_msi_irq() through xhci_interrupter, PCI
> MSI setup still registers the primary vector with usb_hcd as
> the request_irq() dev_id.
>
> Use &xhci->interrupters[0] instead, pass the same dev_id to
> free_irq(), and release the IRQ before xhci_stop() tears
> down the interrupter array.
>
...
>
> @@ -225,10 +225,10 @@ static void xhci_pci_stop(struct usb_hcd *hcd)
> {
> struct xhci_hcd *xhci = hcd_to_xhci(hcd);
>
> - xhci_stop(hcd);
> -
> if (usb_hcd_is_primary_hcd(hcd))
> xhci_cleanup_msix(xhci);
> +
> + xhci_stop(hcd);
Won't this now free the MSI-X interrupt before it has been disabled?
Best Regards,
Niklas
> }
>
> /* called after powerup, by probe or system-pm "wakeup" */
> --
> 2.50.1
>
next prev parent reply other threads:[~2026-05-05 9:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-30 6:38 [PATCH 0/4] usb: xhci: prepare MSI path for secondary interrupters Xu Rao
2026-04-30 6:41 ` [PATCH 1/4] usb: xhci: store xhci pointer in xhci_interrupter raoxu
2026-04-30 6:41 ` [PATCH 2/4] usb: xhci: route MSI through interrupter context raoxu
2026-04-30 6:42 ` [PATCH 3/4] usb: xhci-pci: use the interrupter entry as MSI dev_id raoxu
2026-05-05 9:53 ` Neronin, Niklas [this message]
2026-05-06 5:11 ` Xu Rao
2026-04-30 6:42 ` [PATCH 4/4] usb: xhci: clear USBSTS EINT only for interrupter 0 raoxu
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=131c6e0f-59bc-4d41-9314-3539681f88e0@linux.intel.com \
--to=niklas.neronin@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@linux.intel.com \
--cc=michal.pecio@gmail.com \
--cc=raoxu@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