linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: jwoznack@d-a-s.com
Cc: linux-ide@vger.kernel.org
Subject: Re: Supported chipsets with sata_sil24?
Date: Mon, 06 Nov 2006 23:10:51 +0900	[thread overview]
Message-ID: <454F426B.5000709@gmail.com> (raw)
In-Reply-To: <pv5ttji1w0qr$.1ftk6q36he52r.dlg@40tude.net>

John Woznack wrote:
> On Sun, 05 Nov 2006 08:53:15 +0900, Tejun Heo wrote:
> 
>> John Woznack wrote:
>>> Out of curiosity, which Silicon Image chipsets are supported by the
>>> sata_sil24 driver? (3124/3132 obviously,but what about 3512, 3112, 3531,
>>> and 3726?)
>> sata_sil24	: 3124, 3132, 3131, 3531
>> sata_sil	: 3112, 3114, 3512 and some other variants
>>
>> 3726 and 4726 are port multipliers and supported by pending PMP patchset.
> 
> Thanks Tejun. Just what I was looking for.
> 
> After checking out http://linux-ata.org/driver-status.html, I've got Just a
> few more questions: 
> 
> 1. The sata_sil24 shows it supports NCQ. Out of curiosity, how can I tell
> if it's using NCQ? 

It will say something like the following.

   ata1.00: ATA-7, max UDMA7, 312581808 sectors: LBA48 NCQ (depth 31/32)

If your controller doesn't support NCQ, it will say 0/32.  ATM, libata 
caps max supported commands to 31, so you'll see 31/32 for NCQ capable 
drives.

> 2. The sata_sil24 and sata_sil drivers support suspend. Can you explain
> this in more detail? (Like, is it always on or do I have to enable it? Can
> I set the idle timeout-to-suspend somehow? etc.)

If the power management is turned on, those are turned on automatically.

-- 
tejun

      reply	other threads:[~2006-11-06 14:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-04 14:29 Supported chipsets with sata_sil24? John Woznack
2006-11-04 23:53 ` Tejun Heo
2006-11-06 13:36   ` John Woznack
2006-11-06 14:10     ` Tejun Heo [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=454F426B.5000709@gmail.com \
    --to=htejun@gmail.com \
    --cc=jwoznack@d-a-s.com \
    --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).