mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Stuge <peter@stuge.se>
To: "Alexis R. Cortes" <alexis.cortes@ti.com>
Cc: sarah.a.sharp@linux.intel.com, gregkh@linuxfoundation.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	brian.quach@ti.com, jorge.llamas@ti.com
Subject: Re: [PATCH] usb: host: xhci: Fix Compliance Mode on SN65LVPE502CP Hardware
Date: Thu, 2 Aug 2012 01:23:58 +0200	[thread overview]
Message-ID: <20120801232358.30215.qmail@stuge.se> (raw)
In-Reply-To: <5019AF84.7020404@ti.com>

Alexis R. Cortes wrote:
> This patch is intended to work around a known issue on the
> SN65LVPE502CP USB3.0 re-driver that can delay the negotiation
> between a device and the host past the usual handshake timeout,
> and if that happens on the first insertion, the host controller
> port will enter in Compliance Mode as per xHCI Spec, thus causing
> the port to become Unusable. This patch creates a timer which polls
> every 2 seconds the link state of each host controller's port (this
> by reading the PORTSC register) and recovers the port by issuing a
> Warm reset every time Compliance mode is detected. Since the issue
> is being caused by a pice of hardware, the timer will be enabled

Typo, insert an 'e' here ^


> +++ b/drivers/usb/host/xhci.c
..
> @@ -420,6 +477,12 @@ int xhci_init(struct usb_hcd *hcd)
>  	retval = xhci_mem_init(xhci, GFP_KERNEL);
>  	xhci_dbg(xhci, "Finished xhci_init\n");
>  
> +	/* Initializing Compliance Mode Recovery Data If Needed */
> +	if (compliance_mode_recovery_timer_quirk_check()) {
> +		xhci->quirks |= XHCI_COMP_MODE_QUIRK;
> +		compliance_mode_recovery_timer_init(xhci);
> +	}
> +
>  	return retval;
>  }

Maybe add the code just *before* the "Finished" debug message rather
than after.


//Peter

  reply	other threads:[~2012-08-01 23:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 22:36 Alexis R. Cortes
2012-08-01 23:23 ` Peter Stuge [this message]
2012-08-01 23:51 ` Sarah Sharp
  -- strict thread matches above, loose matches on Subject: below --
2012-08-01 19:04 Alexis R. Cortes
2012-08-01 20:01 ` Peter Stuge
2012-08-01 21:18   ` Sarah Sharp
     [not found]     ` <007b01cd702f$1b5e4870$521ad950$@cortes@ti.com>
2012-08-01 23:32       ` Sarah Sharp
2012-07-31 22:48 Alexis R. Cortes
2012-07-31 23:18 ` Greg KH
2012-07-31 21:19 Alexis Cortes
2012-07-31 21:38 ` Greg KH
     [not found]   ` <50186206.0730b60a.069d.6df1SMTPIN_ADDED@mx.google.com>
2012-07-31 23:16     ` 'Greg KH'

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=20120801232358.30215.qmail@stuge.se \
    --to=peter@stuge.se \
    --cc=alexis.cortes@ti.com \
    --cc=brian.quach@ti.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jorge.llamas@ti.com \
    --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

Powered by JetHome