public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Denis Turischev <denis@compulab.co.il>
Cc: Sarah Sharp <sarah.a.sharp@linux.intel.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [PATCH 1/2] xhci: provide usb_disable_xhci_ports function for Intel chipsets.
Date: Mon, 23 Jul 2012 18:45:09 +0400	[thread overview]
Message-ID: <500D6375.1070102@mvista.com> (raw)
In-Reply-To: <500D398E.1060000@compulab.co.il>

Hello.

On 07/23/2012 03:46 PM, Denis Turischev wrote:

> Some devices with Intel Panther Point chipset may require switchover
> usb ports from XHCI back to EHCI controller before shutdown.
> Overwise various BIOS bugs related to power management may be
> triggered.

> Signed-off-by: Denis Turischev <denis@compulab.co.il>
> ---
>  drivers/usb/host/pci-quirks.c |   14 ++++++++++++++
>  drivers/usb/host/pci-quirks.h |    1 +
>  2 files changed, 15 insertions(+)

> diff --git a/drivers/usb/host/pci-quirks.c b/drivers/usb/host/pci-quirks.c
> index df0828c..b19a84a 100644
> --- a/drivers/usb/host/pci-quirks.c
> +++ b/drivers/usb/host/pci-quirks.c
> @@ -800,6 +800,20 @@ void usb_enable_xhci_ports(struct pci_dev *xhci_pdev)
>  }
>  EXPORT_SYMBOL_GPL(usb_enable_xhci_ports);
> 
> +void usb_disable_xhci_ports(struct pci_dev *xhci_pdev)
> +{
> +	u32		ports_available;
> +
> +	ports_available = 0x0;

   Why not make it an initializer? And why do you need the variable at all?

> +
> +	pci_write_config_dword(xhci_pdev, USB_INTEL_USB3_PSSEN,
> +			cpu_to_le32(ports_available));

   cpu_to_le32() not needed.

> +
> +	pci_write_config_dword(xhci_pdev, USB_INTEL_XUSB2PR,
> +			cpu_to_le32(ports_available));
> +}
> +EXPORT_SYMBOL_GPL(usb_disable_xhci_ports);
> +
>  /**
>   * PCI Quirks for xHCI.
>   *

WBR, Sergei


  reply	other threads:[~2012-07-23 14:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-16 16:46 [PATCH] xhci: EHCI/xHCI ports switching on Intense-PC Denis Turischev
2012-07-17  4:54 ` Sarah Sharp
2012-07-18  6:57   ` Denis Turischev
2012-07-18 16:59     ` Sarah Sharp
2012-07-23 11:46       ` [PATCH 1/2] xhci: provide usb_disable_xhci_ports function for Intel chipsets Denis Turischev
2012-07-23 14:45         ` Sergei Shtylyov [this message]
2012-07-23 15:59           ` [PATCH 1/2 v2] " Denis Turischev
2012-07-23 11:46       ` [PATCH 2/2] xhci: EHCI/XHCI ports switching on Intense-PC Denis Turischev
2012-07-23 17:44         ` Sarah Sharp
2012-07-24  8:50           ` Denis Turischev
2012-07-24 19:46             ` Sarah Sharp
2012-07-30 22:34               ` Sarah Sharp
2012-07-31  4:49                 ` Oliver Neukum
2012-07-31 17:06                   ` Sarah Sharp
2012-07-31 18:39                     ` Sarah Sharp
2012-07-31 10:42                 ` Denis Turischev
2012-08-07 17:35         ` Sarah Sharp
2012-08-07 17:39           ` [RFT] xhci: Switch PPT ports to EHCI on shutdown Sarah Sharp
2012-08-09 14:31             ` Denis Turischev
2012-08-23  4:30             ` Robert Hancock
2012-07-17 12:20 ` [PATCH] xhci: EHCI/xHCI ports switching on Intense-PC Sergei Shtylyov

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=500D6375.1070102@mvista.com \
    --to=sshtylyov@mvista.com \
    --cc=denis@compulab.co.il \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=sarah.a.sharp@linux.intel.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