From: Yan Li <elliot.li.tech@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@suse.de, linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Enable CONFIG_USB_SUSPEND by default or some mobile HD can't be unplugged safely
Date: Fri, 2 Jan 2009 21:23:56 +0800 [thread overview]
Message-ID: <20090102132355.GA4833@thyme.bj.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0901011225400.32126-100000@netrider.rowland.org>
On Thu, Jan 01, 2009 at 12:29:51PM -0500, Alan Stern wrote:
> On Fri, 2 Jan 2009, Yan Li wrote:
> > On it's manual read "you should unplug and remove the device only when
> > the light is off."
>
> It's not clear whether you should believe this. The manual may have
> overstated things. Still, better to be safe.
Yeah, that maybe true. Better to be safe. And we can't tell users just
to ignore the warnings on the manual.
> > On Windows and Mac OS, `safely remove this device' function effectly
> > turns it into `suspend' mode, and it's light off.
>
> Yes -- but they don't suspend the device; instead they disable its
> upstream port. As far as the device is concerned, there's no
> difference. However the Linux API doesn't include any way to disable a
> USB port. Maybe we should add one...
Definitely.
> > I did a
> > quick search in LKML and haven't found specific oppose to enable USB
> > suspend by default, and Debian has started shipping a kernel with
> > it turned on since 2.6.26.
> >
> > Perhaps we should consider turning it on by default? Thanks!
>
> That is indeed the next step to take.
Hope to see this happen soon.
--
Li, Yan
next prev parent reply other threads:[~2009-01-02 13:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 16:03 Enable CONFIG_USB_SUSPEND by default or some mobile HD can't be unplugged safely Yan Li
2009-01-01 16:07 ` [PATCH] enable CONFIG_USB_SUSPEND by default Yan Li
2009-01-01 17:29 ` Enable CONFIG_USB_SUSPEND by default or some mobile HD can't be unplugged safely Alan Stern
2009-01-02 13:23 ` Yan Li [this message]
2009-01-01 17:32 ` Alexander E. Patrakov
2009-01-01 17:45 ` Alan Stern
2009-01-02 13:37 ` Yan Li
2009-01-02 13:46 ` Alexander E. Patrakov
2009-01-01 19:09 ` Robert Hancock
2009-01-02 9:56 ` Tino Keitel
2009-01-02 14:00 ` Yan Li
2009-01-02 14:08 ` Tino Keitel
2009-01-02 14:28 ` Yan Li
2009-01-02 16:04 ` Alan Stern
2009-01-03 2:33 ` Yan Li
2009-01-02 15:50 ` Mark Lord
2009-01-02 15:51 ` Mark Lord
2009-01-02 18:15 ` Tino Keitel
2009-01-03 2:24 ` Yan Li
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=20090102132355.GA4833@thyme.bj.intel.com \
--to=elliot.li.tech@gmail.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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