From: Jeff Garzik <jeff@garzik.org>
To: Tejun Heo <tj@kernel.org>
Cc: "linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Kyle McMartin <kyle@mcmartin.ca>, stable <stable@kernel.org>
Subject: Re: [PATCH #upstream-fixes] libata: issue DIPM enable commands with LPM state updated
Date: Fri, 24 Dec 2010 13:38:54 -0500 [thread overview]
Message-ID: <4D14E8BE.90405@garzik.org> (raw)
In-Reply-To: <4D00F20B.2080908@kernel.org>
On 12/09/2010 10:13 AM, Tejun Heo wrote:
> Low level drivers may behave differently depending on the current
> link->lpm_policy. During ata_eh_set_lpm(), DIPM enable commands are
> issued after the successful completion of ap->ops->set_lpm(), which
> means that the controller is already in the target state. This causes
> DIPM enable commands to be processed with mismatching controller power
> state and link->lpm_policy value.
>
> In ahci, link->lpm_policy is used to ignore certain PHY events if LPM
> is enabled; however, as DIPM commands are issued with stale
> link->lpm_policy, they sometimes end up triggering these conditions
> and get aborted leading to LPM configuration failure.
>
> Fix it by updating link->lpm_policy before issuing DIPM enable
> commands.
>
> Signed-off-by: Tejun Heo<tj@kernel.org>
> Reported-by: Kyle McMartin<kyle@mcmartin.ca>
> Cc: stable@kernel.org
> ---
> drivers/ata/libata-eh.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
applied
prev parent reply other threads:[~2010-12-24 18:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 15:13 [PATCH #upstream-fixes] libata: issue DIPM enable commands with LPM state updated Tejun Heo
2010-12-24 18:38 ` Jeff Garzik [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=4D14E8BE.90405@garzik.org \
--to=jeff@garzik.org \
--cc=kyle@mcmartin.ca \
--cc=linux-ide@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tj@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 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.