From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Oliver Neukum <oneukum@suse.de>, Thomas Renninger <trenn@suse.de>,
Yinghai Lu <yinghai@kernel.org>,
Frederik Himpe <fhimpe@vub.ac.be>,
David Haerdeman <david@hardeman.nu>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [PATCH][v2] xhci: correctly enable interrupts
Date: Mon, 04 Mar 2013 17:27:47 +0400 [thread overview]
Message-ID: <5134A153.6080707@cogentembedded.com> (raw)
In-Reply-To: <1362385324-15228-1-git-send-email-hare@suse.de>
Hello.
On 04-03-2013 12:22, Hannes Reinecke wrote:
> xhci has its own interrupt enabling routine, which will try to
> use MSI-X/MSI if present. So the usb core shouldn't try to enable
> legacy interrupts; on some machines the xhci legacy IRQ setting
> is invalid.
> Cc: Bjorn Helgaas <bhelgaas@google.com>
> Cc: Oliver Neukum <oneukum@suse.de>
> Cc: Thomas Renninger <trenn@suse.de>
> Cc: Yinghai Lu <yinghai@kernel.org>
> Cc: Frederik Himpe <fhimpe@vub.ac.be>
> Cc: David Haerdeman <david@hardeman.nu>
> Cc: Alan Stern <stern@rowland.harvard.edu>
> Signed-off-by: Hannes Reinecke <hare@suse.de>
> diff --git a/drivers/usb/core/hcd-pci.c b/drivers/usb/core/hcd-pci.c
> index 622b4a4..2647e75 100644
> --- a/drivers/usb/core/hcd-pci.c
> +++ b/drivers/usb/core/hcd-pci.c
[...]
> @@ -187,15 +188,21 @@ int usb_hcd_pci_probe(struct pci_dev *dev, const struct pci_device_id *id)
> return -ENODEV;
> dev->current_state = PCI_D0;
>
> - /* The xHCI driver supports MSI and MSI-X,
> - * so don't fail if the BIOS doesn't provide a legacy IRQ.
> + /*
> + * The xHCI driver supports MSI and MSI-X,
> + * so don't fail if the BIOS doesn't provide a legacy IRQ
> + * and do not try to enable legacy IRQs.
> */
> - if (!dev->irq && (driver->flags & HCD_MASK) != HCD_USB3) {
> - dev_err(&dev->dev,
> - "Found HC with no IRQ. Check BIOS/PCI %s setup!\n",
> - pci_name(dev));
> - retval = -ENODEV;
> - goto disable_pci;
> + if ((driver->flags & HCD_MASK) != HCD_USB3) {
> + if (!dev->irq) {
> + dev_err(&dev->dev,
> + "Found HC with no IRQ. "
> + "Check BIOS/PCI %s setup!\n",
The message strings are allowed to take more than 80 chars (to facilitate
grepping for them), so no need to break this one; checkpatch.pl should not
complain...
> + pci_name(dev));
> + retval = -ENODEV;
> + goto disable_pci;
> + }
> + hcd_irq = dev->irq;
> }
>
> hcd = usb_create_hcd(driver, &dev->dev, pci_name(dev));
WBR, Sergei
next prev parent reply other threads:[~2013-03-04 13:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-04 8:22 [PATCH][v2] xhci: correctly enable interrupts Hannes Reinecke
2013-03-04 11:25 ` David Härdeman
2013-03-04 13:27 ` Sergei Shtylyov [this message]
2013-03-04 15:26 ` Alan Stern
2013-03-04 16:11 ` Thomas Renninger
2013-03-04 16:14 ` [PATCH][v3] " Thomas Renninger
2013-03-04 18:08 ` Sergei Shtylyov
2013-03-04 17:36 ` Alan Stern
2013-03-05 10:45 ` Thomas Renninger
2013-03-15 18:34 ` Greg KH
2013-03-05 23:37 ` Sarah Sharp
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=5134A153.6080707@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=bhelgaas@google.com \
--cc=david@hardeman.nu \
--cc=fhimpe@vub.ac.be \
--cc=hare@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=stern@rowland.harvard.edu \
--cc=trenn@suse.de \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox