linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.de>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: linux-usb@vger.kernel.org, gregkh@linuxfoundation.org,
	Takashi Iwai <tiwai@suse.de>,
	trenn@suse.de, linux-pci@vger.kernel.org,
	Michal Marek <MMarek@suse.com>,
	Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [RFC] xhci: Fix BIOS handoff failure on some Intel systems.
Date: Wed, 8 Feb 2012 16:11:37 +0100	[thread overview]
Message-ID: <201202081611.37097.oneukum@suse.de> (raw)
In-Reply-To: <20120207233118.GA6947@xanatos>

Am Mittwoch, 8. Februar 2012, 00:31:18 schrieb Sarah Sharp:
> The downside is that the xHCI BIOS handoff mechanism will fail because
> memory mapped I/O is not enabled for the disabled PCI device.  Make the
> xHCI quirk handler call pci_enable_device() to re-enable MMIO, and call
> pci_disable_device() once it's done with the BIOS handoff.  This will
> balance the ref counts in the PCI core.  When the xHCI PCI probe is
> called, usb_hcd_pci_probe() will call pci_enable_device() again.
> 
> Also add some debugging to the xHCI quirk failure paths, so we can pin
> point the problem when a user says their xHCI PCI quirk function fails.
> 
> Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
> ---
> 
> Hi Oliver,
> 
> What about this approach instead?  This means the PCI quirk sequence
> doesn't change, and the xHCI ports are still switched over before the
> EHCI PCI probe starts.  With your original patch, the ports could be
> switched over after the EHCI driver has already started to enumerate
> devices.
> 
> Can you test and make sure this fixes the issue on your test systems?

I've tested it and it works. Are you sure it is safe to enable a PCI device
at that point? If so, your patch is better than mine.

	Regards
		Oliver

  reply	other threads:[~2012-02-08 15:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-03 11:22 [PATCH] USB:xhci: fix port switching on PantherPoint Oliver Neukum
2012-02-03 15:16 ` Alan Stern
2012-02-03 16:21   ` Oliver Neukum
2012-02-03 15:27 ` Sarah Sharp
2012-02-07 23:31   ` [RFC] xhci: Fix BIOS handoff failure on some Intel systems Sarah Sharp
2012-02-08 15:11     ` Oliver Neukum [this message]
2012-02-08 21:48       ` Sarah Sharp
2012-02-09  8:56         ` Oliver Neukum
2012-02-09 15:08           ` Sarah Sharp
2012-02-09 20:13             ` [RFC v2] USB: Fix handoff when BIOS disables host PCI device Sarah Sharp
2012-02-14 20:33               ` Sarah Sharp
2012-02-15  8:48                 ` Oliver Neukum
2012-02-15 16:38                   ` Sarah Sharp
2012-02-16 10:15                     ` Oliver Neukum
2012-02-16 14:33                       ` Sarah Sharp
2012-02-16 14:48                         ` Oliver Neukum
2012-02-16 16:54                           ` Sarah Sharp
2012-02-16 17:50                             ` Oliver Neukum

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=201202081611.37097.oneukum@suse.de \
    --to=oneukum@suse.de \
    --cc=MMarek@suse.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).