From: Clemens Ladisch <clemens@ladisch.de>
To: "Alex,Shi" <alex.shi@intel.com>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
stern@rowland.harvard.edu, Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, andiry.xu@amd.com,
linux-kernel@vger.kernel.org, Oliver Neukum <oneukum@suse.de>,
Takashi Iwai <tiwai@suse.de>,
trenn@suse.de, linux-pci@vger.kernel.org,
Michal Marek <MMarek@suse.com>
Subject: Re: [PATCH] usb: enable pci MSI/MSIX in usb core
Date: Fri, 17 Feb 2012 09:13:49 +0100 [thread overview]
Message-ID: <4F3E0C3D.4030307@ladisch.de> (raw)
In-Reply-To: <1329461087.12669.2911.camel@debian>
Alex,Shi wrote:
> On Thu, 2012-02-16 at 10:36 +0800, Alex,Shi wrote:
>>>> +/* msi irq handler should be here, if driver has */
>>>> +irqreturn_t hcd_msi_irq(int irq, struct usb_hcd *hcd)
>>>> +{
>>>> + return hcd->driver->irq(hcd);
>>>> +}
>>>
>>> This works for now, but it isn't going to work in the future. We need
>>> the USB core to provide us with the irq number so we can map the MSI-X
>>> interrupt to the event ring that generated the interrupt, whenever we
>>> get around to adding multiple event rings.
>>
>> Do you mean to add 2 new vectors for MSI/MSIX in hc_driver?
>
> + irqreturn_t (*msi_irq) (struct usb_hcd *hcd);
> + irqreturn_t (*msix_irq) (struct usb_hcd *hcd);
The controller driver will need to know which of the multiple MSI-X
interrupts has been raised:
irqreturn_t (*msix_irq)(struct usb_hcd *hcd, unsigned int nr_or_index);
Regards,
Clemens
next prev parent reply other threads:[~2012-02-17 8:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 12:29 [PATCH] usb: enable pci MSI/MSIX in usb core Alex Shi
2012-02-07 11:59 ` Alex Shi
2012-02-07 14:42 ` Greg KH
2012-02-07 17:27 ` Sarah Sharp
2012-02-07 22:13 ` Sarah Sharp
2012-02-08 1:26 ` Alex,Shi
2012-02-08 6:27 ` Alex,Shi
2012-02-08 9:11 ` Alex,Shi
2012-02-14 0:20 ` Sarah Sharp
2012-02-14 0:25 ` [RFT] USB: Try MSI first before line IRQ for Intel PCIe USB3 HCD Sarah Sharp
2012-02-14 4:43 ` Alex,Shi
2012-02-16 2:36 ` [PATCH] usb: enable pci MSI/MSIX in usb core Alex,Shi
2012-02-17 6:44 ` Alex,Shi
2012-02-17 8:13 ` Clemens Ladisch [this message]
2012-02-17 8:46 ` Alex,Shi
2012-02-17 10:15 ` Clemens Ladisch
2012-02-18 6:28 ` Andiry Xu
2012-02-20 0:57 ` Alex,Shi
2012-02-20 3:52 ` Alex,Shi
2012-02-08 15:07 ` Alan Stern
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=4F3E0C3D.4030307@ladisch.de \
--to=clemens@ladisch.de \
--cc=MMarek@suse.com \
--cc=alex.shi@intel.com \
--cc=andiry.xu@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tiwai@suse.de \
--cc=trenn@suse.de \
/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.