linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Claus H. Stovgaard" <cst@phaseone.com>
To: <linux-usb@vger.kernel.org>
Cc: Felipe Balbi <balbi@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	<linux-kernel@vger.kernel.org>,
	"Anurag Kumar Vulisha" <anurag.kumar.vulisha@xilinx.com>
Subject: Re: [PATCH] usb: gadget: configfs: Add lpm_Ux_disable
Date: Tue, 7 May 2019 11:37:10 +0200	[thread overview]
Message-ID: <1557221830.114189.8.camel@phaseone.com> (raw)
In-Reply-To: <1557220655-123090-1-git-send-email-cst@phaseone.com>

On Tue, 2019-05-07 at 11:09 +0200, Claus H. Stovgaard wrote:
> When combining dwc3 with an redriver for a USB Type-C device
> solution, it
> sometimes have problems with leaving U1/U2 for certain hosts,
> resulting in
> link training errors and reconnects. This create an interface via
> configfs for disabling U1/U2, enabling a workaround for devices based
> on
> dwc3.
> 

Sorry messed up a bit with a missing cover letter.
This feature relates to Anurag patch [1] and a thread [2] from earlier 

Where Anurags patch focus on setting U1/U2 latency in the BOS
descriptor from the devicetree, this patch focuses on having a configfs
interface for forcing the UDC (here the dwc3) to not enable U1/U2 and
reject the SET_SEL(U1/U2).

Looking forward to input.

[1] https://www.spinics.net/lists/linux-usb/msg179732.html
[2] https://www.spinics.net/lists/linux-usb/msg179393.html


  reply	other threads:[~2019-05-07  9:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07  9:09 [PATCH] usb: gadget: configfs: Add lpm_Ux_disable Claus H. Stovgaard
2019-05-07  9:37 ` Claus H. Stovgaard [this message]
2019-05-07 18:53   ` Thinh Nguyen
2019-05-07 21:28     ` Claus H. Stovgaard
2019-05-08  8:10       ` Anurag Kumar Vulisha

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=1557221830.114189.8.camel@phaseone.com \
    --to=cst@phaseone.com \
    --cc=anurag.kumar.vulisha@xilinx.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.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;
as well as URLs for NNTP newsgroup(s).