From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Niklas Cassel <nks@flawful.org>,
Runa Guo-oc <RunaGuo-oc@zhaoxin.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ata: libata: disallow dev-initiated LPM transitions to unsupported states
Date: Tue, 5 Sep 2023 08:26:46 +0000 [thread overview]
Message-ID: <ZPbmQiQR8yU6L5Nx@x1-carbon> (raw)
In-Reply-To: <f83f8d45-b506-118f-d038-507bc87eeeef@kernel.org>
On Tue, Sep 05, 2023 at 11:29:13AM +0900, Damien Le Moal wrote:
> On 9/5/23 05:42, Niklas Cassel wrote:
> > From: Niklas Cassel <niklas.cassel@wdc.com>
> >
> > In AHCI 1.3.1, the register description for CAP.SSC:
> > "When cleared to ‘0’, software must not allow the HBA to initiate
> > transitions to the Slumber state via agressive link power management nor
> > the PxCMD.ICC field in each port, and the PxSCTL.IPM field in each port
> > must be programmed to disallow device initiated Slumber requests."
> >
> > In AHCI 1.3.1, the register description for CAP.PSC:
> > "When cleared to ‘0’, software must not allow the HBA to initiate
> > transitions to the Partial state via agressive link power management nor
> > the PxCMD.ICC field in each port, and the PxSCTL.IPM field in each port
> > must be programmed to disallow device initiated Partial requests."
> >
> > Ensure that we always set the corresponding bits in PxSCTL.IPM, such that
> > a device is not allowed to initiate transitions to power states which are
> > unsupported by the HBA.
> >
> > DevSleep is always initiated by the HBA, however, for completeness, set the
> > corresponding bit in PxSCTL.IPM such that agressive link power management
> > cannot transition to DevSleep if DevSleep is not supported.
> >
> > sata_link_scr_lpm() is used by libahci, ata_piix and libata-pmp.
> > However, only libahci has the ability to read the CAP/CAP2 register to see
> > if these features are supported. Therefore, in order to not introduce any
> > regressions on ata_piix or libata-pmp, create flags that indicate that the
> > respective feature is NOT supported. This way, the behavior for ata_piix
> > and libata-pmp should remain unchanged.
> >
> > This change is based on a patch originally submitted by Runa Guo-oc.
> >
> > Signed-off-by: Niklas Cassel <niklas.cassel@wdc.com>
>
> Looks good, but don't we need a Fixes tag for this ?
Sure
Fixes: 1152b2617a6e ("libata: implement sata_link_scr_lpm() and make ata_dev_set_feature() global")
Can you add when applying, or do you want me to resend?
Kind regards,
Niklas
next prev parent reply other threads:[~2023-09-05 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 20:42 [PATCH] ata: libata: disallow dev-initiated LPM transitions to unsupported states Niklas Cassel
2023-09-05 2:29 ` Damien Le Moal
2023-09-05 8:26 ` Niklas Cassel [this message]
2023-09-05 8:33 ` Damien Le Moal
2023-09-11 6:12 ` Damien Le Moal
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=ZPbmQiQR8yU6L5Nx@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=RunaGuo-oc@zhaoxin.com \
--cc=dlemoal@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=nks@flawful.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