linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: <balbi@kernel.org>, <mathias.nyman@intel.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] usb: xhci: Add broken port disable quirk
Date: Tue, 3 Jan 2017 14:37:41 +0200	[thread overview]
Message-ID: <e9cd4eff-5cbf-e297-08d2-e2fb317dbc3a@ti.com> (raw)
In-Reply-To: <1479394881-13863-1-git-send-email-rogerq@ti.com>

Mathias & Felipe,

On 17/11/16 17:01, Roger Quadros wrote:
> Hi,
> 
> Some XHCI controllers e.g. dwc3 based have a broken Port disable [1].
> 
> If the attached high-speed device is misbehaving, the USB stack typically
> disables the port using the PED bit in PORTSC. For the controllers that
> have broken port disable, the port fails to detect further attach/detach
> events and so high-speed devices can no longer be enumerated on the
> port. The workaround is to prevent port disable using PED on such
> controllers.
> 
> We add a new BROKEN_PED quirk flag and 'quirk-broken-port-ped' device
> property and prevent port disable using PED if we encounter the quirk flag.
> 
> [1] - AM572x Silicon Errata http://www.ti.com/lit/er/sprz429j/sprz429j.pdf
>     Section i896— USB xHCI Port Disable Feature Does Not Work

Any comments on this series?
patch 1 is at v3. Rest 2 are original.

cheers,
-roger

> 
> cheers,
> -roger
> 
> Felipe Balbi (3):
>   usb: xhci: add quirk flag for broken PED bits
>   usb: host: xhci-plat: enable BROKEN_PED quirk if platform requested
>   usb: dwc3: host: pass quirk-broken-port-ped property for known broken
>     revisions
> 
>  Documentation/devicetree/bindings/usb/usb-xhci.txt |  1 +
>  drivers/usb/dwc3/host.c                            | 21 ++++++++++++++++++---
>  drivers/usb/host/xhci-hub.c                        |  6 ++++++
>  drivers/usb/host/xhci-plat.c                       |  3 +++
>  drivers/usb/host/xhci.h                            |  3 +++
>  5 files changed, 31 insertions(+), 3 deletions(-)
> 

  parent reply	other threads:[~2017-01-03 12:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17 15:01 [PATCH 0/3] usb: xhci: Add broken port disable quirk Roger Quadros
2016-11-17 15:01 ` [PATCH 1/3] usb: xhci: add quirk flag for broken PED bits Roger Quadros
2016-11-18 10:49   ` Sergei Shtylyov
2016-11-21 11:51     ` Roger Quadros
2016-11-21 11:51   ` [PATCH v2 " Roger Quadros
2016-11-21 11:56     ` Felipe Balbi
2016-11-21 13:05       ` Roger Quadros
2016-11-21 13:09     ` [PATCH v3 " Roger Quadros
2016-11-17 15:01 ` [PATCH 2/3] usb: host: xhci-plat: enable BROKEN_PED quirk if platform requested Roger Quadros
2016-11-17 15:01 ` [PATCH 3/3] usb: dwc3: host: pass quirk-broken-port-ped property for known broken revisions Roger Quadros
2017-01-03 12:37 ` Roger Quadros [this message]
2017-01-03 12:53   ` [PATCH 0/3] usb: xhci: Add broken port disable quirk Felipe Balbi
2017-01-03 16:32     ` Mathias Nyman
2017-01-24 14:59     ` Roger Quadros
2017-01-26  9:19       ` Felipe Balbi

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=e9cd4eff-5cbf-e297-08d2-e2fb317dbc3a@ti.com \
    --to=rogerq@ti.com \
    --cc=balbi@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@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;
as well as URLs for NNTP newsgroup(s).