From: Douglas Gilbert <dougg@torque.net>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: sdparm cannot start or stop SATA disks
Date: Sat, 30 Jul 2005 13:06:08 +1000 [thread overview]
Message-ID: <42EAEEA0.5010106@torque.net> (raw)
In-Reply-To: <42EA553A.1070304@pobox.com>
Jeff Garzik wrote:
> Douglas Gilbert wrote:
>
>> sdparm uses the START STOP UNIT SCSI command to start
>> and stop (spin up and spin down) SCSI devices.
>> Currently libata does not implement that SCSI command.
>> [Hopefully Jeff contradicts me.]
>
>
> Correct.
>
> Someone should submit a libata patch for this!
Jeff,
I could have a go at the SCSI half of it. According to
SAT, START STOP UNIT should only be allowed for non-packet
ATA devices. I assume your SATAPI code will the bypass
libata-scsi.c SAT layer.
SAT suggests libata should issue a ATA STANDBY (sector=0)
to "stop" the device. I can't see the STANDBY command (0xE2)
defined anywhere in libata or the ide subsystem (or their
headers).
The action to start the SATA device depends on the power
mode of the SATA device:
- SLEEP: send a hardware or software reset: that should
get it to ACTIVE or STANDBY mode
- STANDBY or IDLE: send a (READ) VERIFY (sector=0) ATA
to the command
- ACTIVE: I assume this would be a nop
The START STOP UNIT SCSI command also has an "IMMED"iate
bit. That could just be ignored initially.
Is half a patch any use?
Doug Gilbert
next prev parent reply other threads:[~2005-07-30 3:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-29 10:47 sdparm cannot start or stop SATA disks Douglas Gilbert
2005-07-29 16:02 ` Mogens Valentin
2005-07-29 16:11 ` Jeff Garzik
2005-07-30 3:06 ` Douglas Gilbert [this message]
2005-07-30 3:56 ` Jeff Garzik
2005-07-30 3:25 ` Douglas Gilbert
2005-07-30 3:54 ` Jeff Garzik
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=42EAEEA0.5010106@torque.net \
--to=dougg@torque.net \
--cc=jgarzik@pobox.com \
--cc=linux-scsi@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