From: Jeff Garzik <jeff@garzik.org>
To: Robert Hancock <hancockrwd@gmail.com>
Cc: Mark Lord <liml@rtr.ca>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Tejun Heo <htejun@gmail.com>
Subject: Re: hdparm-9.17 released, with experimental trim/wiper scripts for SSDs
Date: Thu, 30 Jul 2009 04:24:06 -0400 [thread overview]
Message-ID: <4A7158A6.1090407@garzik.org> (raw)
In-Reply-To: <4A7149C6.4030508@gmail.com>
Robert Hancock wrote:
> Yeah, according to the datasheet "The SiI3124 will decode the 8-bit ATA
> command at PRB offset 0x0a and automatically execute the default
> protocol for the command. In certain cases it might be desirable to
> specify a non-default protocol to be used, such as with vendor specific
> device commands." The DSM command seems to be DMA data-out and the chip
> likely doesn't know that command. I have to wonder why they decided to
> use that design instead of just making the driver indicate the protocol
> explicitly. In any case, it looks like the driver needs code to override
> the protocol setting for this command. (Maybe we should just set the
> protocol override for what we know the command is supposed to be in all
> cases?)
>
> Sil311x will have the same problem. The solution there seems to be to
> execute a vendor-specific command to tell the controller what protocol
> that command code uses. Some other controllers may have similar issues
> if they are parsing the ATA command codes.. it's possible that some of
> them might not support DSM/TRIM commands properly.
Yes, this is a common problem for many SATA controllers, for any new
opcode -- and for SATA<->PATA bridges too, which also snoop the opcode
to determine certain behaviors.
Jeff
next prev parent reply other threads:[~2009-07-30 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-29 23:35 hdparm-9.17 released, with experimental trim/wiper scripts for SSDs Mark Lord
2009-07-29 23:39 ` Mark Lord
2009-07-30 7:20 ` Robert Hancock
2009-07-30 8:24 ` Jeff Garzik [this message]
2009-07-30 12:54 ` Mark Lord
2009-07-30 18:27 ` Robert Hancock
2009-07-30 18:43 ` Mark Lord
2009-07-30 19:15 ` Mark Lord
2009-07-30 19:30 ` Mark Lord
2009-07-30 19:57 ` Robert Hancock
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=4A7158A6.1090407@garzik.org \
--to=jeff@garzik.org \
--cc=hancockrwd@gmail.com \
--cc=htejun@gmail.com \
--cc=liml@rtr.ca \
--cc=linux-ide@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).