public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Hans de Goede <j.w.r.degoede@hhs.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: USB autosuspend and turning of usb pendrive leds
Date: Fri, 28 Sep 2007 16:48:29 -0400	[thread overview]
Message-ID: <46FD689D.7040103@tmr.com> (raw)
In-Reply-To: <46F3C704.5000203@hhs.nl>

Hans de Goede wrote:
> Hi All,
> 
> Please keep me CC-ed as I'm not subscribed.
> 
> Some time ago a mail about turning of the leds on usb pendrives once 
> unmounted by hal was send to the fedora-devel list:
> https://www.redhat.com/archives/fedora-devel-list/2007-August/msg01807.html
> 
> This mail talked about echo 2 > power/state for usb devices.
> 
> I tested the method described in the mail to turn of the drive light and 
> it worked well.
> 
> As I think that turning of the drive led (as windows does) would be good 
> visual feedback to the end user that its safe to remove the device I've 
> written a patch for hal which does the power state change automatically 
> when the last partition of a usb massstorage device gets unmounted.
> 
> However when testing the patch I found out that my now newer kernel no 
> longer has power/state for usb devices, it only has power/level. I can 
> send suspend to power/level, but then remounting the device won't work 
> and me syslog fills itself with:
> sd 2:0:0:0: [sdc] READ CAPACITY failed
> sd 2:0:0:0: [sdc] Result: hostbyte=DID_ERROR 
> driverbyte=DRIVER_OK,SUGGEST_OK
> sd 2:0:0:0: [sdc] Sense not available.
> sd 2:0:0:0: [sdc] Write Protect is off
> sd 2:0:0:0: [sdc] Mode Sense: 00 00 00 00
> sd 2:0:0:0: [sdc] Assuming drive cache: write through
> 
> Because hal keeps polling the device.

What did power/state do, and can that capability be easily recovered? 
Being able to turn off the lights is desirable, but it may be that 
standby is the only way to do that, with all the issue already discussed 
in this thread. But if there's another way, it would be useful.

-- 
Bill Davidsen <davidsen@tmr.com>
   "We have more to fear from the bungling of the incompetent than from
the machinations of the wicked."  - from Slashdot

      parent reply	other threads:[~2007-09-28 20:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 13:28 USB autosuspend and turning of usb pendrive leds Hans de Goede
2007-09-21 14:18 ` Jiri Kosina
2007-09-21 14:20   ` Hans de Goede
2007-09-21 15:15     ` Jiri Kosina
2007-09-24 10:36       ` Oliver Neukum
2007-09-24 11:38         ` Hans de Goede
2007-09-24 13:25           ` Oliver Neukum
2007-09-21 19:47     ` [linux-usb-devel] " Oliver Neukum
2007-09-21 14:39   ` Alan Stern
2007-09-22 14:00     ` Hans de Goede
2007-09-22 14:29       ` Alan Stern
2007-09-22 17:08         ` Hans de Goede
2007-09-22 20:12           ` Alan Stern
2007-09-28 20:48 ` Bill Davidsen [this message]

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=46FD689D.7040103@tmr.com \
    --to=davidsen@tmr.com \
    --cc=j.w.r.degoede@hhs.nl \
    --cc=linux-kernel@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