All of lore.kernel.org
 help / color / mirror / Atom feed
From: Runa Guo-oc <RunaGuo-oc@zhaoxin.com>
To: <damien.lemoal@opensource.wdc.com>, <linux-ide@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: [PATCH 0/2] ahci: Add some controls on actual LPM capability
Date: Thu, 21 Apr 2022 17:43:35 +0800	[thread overview]
Message-ID: <1650534217-14052-1-git-send-email-RunaGuo-oc@zhaoxin.com> (raw)

On some platform, when OS enables LPM by default (eg, min_power),
then, PhyRdy Change cannot be detected if ahci supports no LPM;
DIPM Slumber request cannot be disallowed if ahci's CAP.PSC is
set to '1' and CAP.SSC is cleared to '0', which may cause ahci
to be an uncertain state (same for Partial).

In ahci spec, PhyRdy Change cannot coexist with LPM;
when CAP.PSC/SSC is cleared to '0', the PxSCTL.IPM
field must be programmed to disallow device initiated
Partial/Slumber request.

Adds suports to control these cases on actual LPM capability.

Runa Guo-oc (2):
  ahci: Add PhyRdy Change control on actual LPM capability
  ahci: Add PxSCTL.IPM control on actual LPM capability

 drivers/ata/ahci.c        |  9 +++++++++
 drivers/ata/libata-eh.c   |  4 ++++
 drivers/ata/libata-sata.c | 12 +++++++++++-
 include/linux/libata.h    |  4 ++++
 4 files changed, 28 insertions(+), 1 deletion(-)

-- 
2.7.4


             reply	other threads:[~2022-04-21  9:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-21  9:43 Runa Guo-oc [this message]
2022-04-21  9:43 ` [PATCH 1/2] ahci: Add PhyRdy Change control on actual LPM capability Runa Guo-oc
2022-04-21 10:39   ` Damien Le Moal
2022-04-22  9:57     ` RunaGuo-oc
2022-04-22 22:37       ` Damien Le Moal
2022-04-27 10:18         ` Runa Guo-oc
2022-05-02 13:05           ` Damien Le Moal
2022-05-07  7:36             ` Runa Guo-oc
2022-05-11  8:14               ` Damien Le Moal
2022-05-18 21:31                 ` Limonciello, Mario
2022-04-21  9:43 ` [PATCH 2/2] ahci: Add PxSCTL.IPM " Runa Guo-oc
2022-04-21 10:53   ` Damien Le Moal
2022-04-22  9:58     ` RunaGuo-oc

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=1650534217-14052-1-git-send-email-RunaGuo-oc@zhaoxin.com \
    --to=runaguo-oc@zhaoxin.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@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 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.