mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zhuang Jin Can <jin.can.zhuang@intel.com>
Cc: rafael.j.wysocki@intel.com, stern@rowland.harvard.edu,
	dan.j.williams@intel.com, pmladek@suse.cz,
	peter.chen@freescale.com, jwerner@chromium.org,
	linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: core: add usb3 lpm sysfs
Date: Tue, 28 Apr 2015 12:42:24 +0200	[thread overview]
Message-ID: <20150428104224.GB540@kroah.com> (raw)
In-Reply-To: <20150419034612.GA31576@intel.com>

On Sun, Apr 19, 2015 at 11:46:12AM +0800, Zhuang Jin Can wrote:
> Some usb3 devices may not support usb3 lpm well.
> The patch adds a sysfs to enable/disable u1 or u2 of the port.The
> settings apply to both before and after device enumeration.
> Supported values are "0" - u1 and u2 are disabled, "u1" - only u1 is
> enabled, "u2" - only u2 is enabled, "u1_u2" - u1 and u2 are enabled.
> 
> The interface is useful for testing some USB3 devices during
> development, and provides a way to disable usb3 lpm if the issues can
> not be fixed in final products.

How is a user supposed to "know" to make this setting for a device?  Why
can't the kernel automatically set this value properly?  Why does it
need to be a kernel issue at all?

And when you are doing development of broken devices, the kernel doesn't
have to support you, you can run with debugging patches of your own
until you fix your firmware :)

thanks,

greg k-h

  parent reply	other threads:[~2015-04-28 10:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-19  3:46 Zhuang Jin Can
2015-04-22  9:21 ` Zhuang Jin Can
2015-04-28 10:42 ` Greg KH [this message]
2015-04-28 16:51   ` Zhuang Jin Can
2015-04-28 21:11     ` Greg KH
2015-04-29  7:20       ` Zhuang Jin Can
2015-04-29  9:01         ` Greg KH
2015-04-29 10:57           ` Zhuang Jin Can
2015-04-29 11:06             ` Greg KH
2015-04-29 16:21               ` Zhuang Jin Can
2015-04-29 19:57                 ` Greg KH
2015-04-30  8:49                   ` Zhuang Jin Can

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=20150428104224.GB540@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jin.can.zhuang@intel.com \
    --cc=jwerner@chromium.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=peter.chen@freescale.com \
    --cc=pmladek@suse.cz \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stern@rowland.harvard.edu \
    /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