All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Shane Huang <shane.huang@amd.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: check SATA_SETTINGS log with HW Feature Ctrl
Date: Mon, 03 Dec 2012 04:58:50 -0500	[thread overview]
Message-ID: <50BC77DA.1060401@pobox.com> (raw)
In-Reply-To: <1353185081-11349-1-git-send-email-shane.huang@amd.com>

On 11/17/2012 03:44 PM, Shane Huang wrote:
> NCQ capability was used to check availability of SATA Settings page
> from Identify Device Data Log, which contains DevSlp timing variables.
> It does not work on some HDDs and leads to error messages.
> IDENTIFY word 78 bit 5(Hardware Feature Control) should be used.
>
> Quoting SATA spec 3.1:
> If Hardware Feature Control is supported, then:
> a) IDENTIFY DEVICE data word 78 bit 5 (see 13.2.1.18) shall be
> set to one;
> b) the SET FEATURES Select Hardware Feature Control subcommand
> shall be supported (see 13.3.8);
> c) page 08h of the Identify Device Data log (see 13.7.7) shall
> be supported;
>
> This patch is not tested on SATA HDD with DevSlp supported.
>
> Reported-by: Borislav Petkov <bp@amd64.org>
> Signed-off-by: Shane Huang <shane.huang@amd.com>
> ---
>   drivers/ata/libata-core.c |    3 +--
>   include/linux/ata.h       |    1 +
>   2 files changed, 2 insertions(+), 2 deletions(-)

applied




  reply	other threads:[~2012-12-03  9:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-17 20:44 [PATCH] libata: check SATA_SETTINGS log with HW Feature Ctrl Shane Huang
2012-12-03  9:58 ` Jeff Garzik [this message]
2012-12-11  9:25   ` Huang, Shane
2012-12-14 14:37     ` 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=50BC77DA.1060401@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=shane.huang@amd.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.