linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Damien Le Moal <dlemoal@kernel.org>
To: Hannes Reinecke <hare@suse.de>,
	linux-ide@vger.kernel.org, Niklas Cassel <cassel@kernel.org>
Subject: Re: [PATCH 3/6] ata: Fix SATA_MOBILE_LPM_POLICY description in Kconfig
Date: Fri, 27 Jun 2025 16:35:38 +0900	[thread overview]
Message-ID: <5b3d302b-c4e5-4061-959c-e60b1ec1bc6a@kernel.org> (raw)
In-Reply-To: <347157db-8a01-47ae-9dba-c46c77bae824@suse.de>

On 6/27/25 15:03, Hannes Reinecke wrote:
> On 6/27/25 03:11, Damien Le Moal wrote:
>> Improve the description of the possible default SATA link power
>> management policies and add the missing description for policy 5.
>> No functional changes.
>>
>> Fixes: a5ec5a7bfd1f ("ata: ahci: Support state with min power but Partial low power state")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
>> ---
>>   drivers/ata/Kconfig | 36 ++++++++++++++++++++++++++----------
>>   1 file changed, 26 insertions(+), 10 deletions(-)
>>
>> diff --git a/drivers/ata/Kconfig b/drivers/ata/Kconfig
>> index e00536b49552..1d53d7b568bd 100644
>> --- a/drivers/ata/Kconfig
>> +++ b/drivers/ata/Kconfig
>> @@ -117,23 +117,39 @@ config SATA_AHCI
>>   
>>   config SATA_MOBILE_LPM_POLICY
>>   	int "Default SATA Link Power Management policy"
>> -	range 0 4
>> +	range 0 5
>>   	default 3
>>   	depends on SATA_AHCI
>>   	help
>>   	  Select the Default SATA Link Power Management (LPM) policy to use
>>   	  for chipsets / "South Bridges" supporting low-power modes. Such
>>   	  chipsets are ubiquitous across laptops, desktops and servers.
>> -
>> -	  The value set has the following meanings:
>> +	  Each policy combines power saving states and features:
>> +	   - Partial: The Phy logic is powered but is in a reduced power
>> +                      state. The exit latency from this state is no longer than
>> +                      10us).
>> +	   - Slumber: The Phy logic is powered but is in an even lower power
>> +                      state. The exit latency from this state is potentially
>> +		      longer, but no longer than 10ms.
>> +	   - DevSleep: The Phy logic may be powered down. The exit latency from
>> +	               this state is no longer than 20 ms, unless otherwise
>> +		       specified by DETO in the device Identify Device Data log.
>> +	   - HIPM: Host Initiated Power Management (host automatic transisitons
>> +		   to partial and slumber).
>> +	   - DIPM: Device Initiated Power Management (device automatic
>> +		   transitions to partial and slumber).
>> +
>> +	  The possible values for the default SATA link power management
>> +	  policies are:
>>   		0 => Keep firmware settings
>> -		1 => Maximum performance
>> -		2 => Medium power
>> -		3 => Medium power with Device Initiated PM enabled
>> -		4 => Minimum power
>> -
>> -	  Note "Minimum power" is known to cause issues, including disk
>> -	  corruption, with some disks and should not be used.
>> +		1 => No power savings (maximum performance)
>> +		2 => HIPM (Partial)
>> +		3 => HIPM (Partial) and DIPM (Partial and Slumber)
>> +		4 => HIPM (Partial and DevSleep) and DIPM (Partial and Slumber)
>> +		5 => HIPM (Slumber and DevSleep) and DIPM (Partial and Slumber)
>> +
>> +	  Excluding the value 0, higher values represent policies with higher
>> +	  power savings.
>>   
>>   config SATA_AHCI_PLATFORM
>>   	tristate "Platform AHCI SATA support"
> 
> Hmm. Isn't it worth creating an official documentation somewhere in
> Documentation/* to have this available without having to look at the
> source code?

Yes, I am considering this.
I did not write it in the cover letter, but these patches are the first part of
a much bigger patch series that addresses a lot of LPM issues that we recently
discovered doing completely unrelated tests. Once that is out, documenting
everything will be a good thing to do.

> 
> Otherwise:
> Reviewed-by: Hannes Reinecke <hare@suse.de>
> 
> Cheers,
> 
> Hannes


-- 
Damien Le Moal
Western Digital Research

  reply	other threads:[~2025-06-27  7:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  1:11 [PATCH 0/6] Various cleanups Damien Le Moal
2025-06-27  1:11 ` [PATCH 1/6] ata: libata: Remove ATA_DFLAG_ZAC device flag Damien Le Moal
2025-06-27  6:01   ` Hannes Reinecke
2025-06-27  1:11 ` [PATCH 2/6] ata: libata-scsi: Cleanup ata_scsi_offline_dev() Damien Le Moal
2025-06-27  6:01   ` Hannes Reinecke
2025-06-27  1:11 ` [PATCH 3/6] ata: Fix SATA_MOBILE_LPM_POLICY description in Kconfig Damien Le Moal
2025-06-27  6:03   ` Hannes Reinecke
2025-06-27  7:35     ` Damien Le Moal [this message]
2025-06-27  1:11 ` [PATCH 4/6] ata: libata: Improve LPM policies description Damien Le Moal
2025-06-27  6:04   ` Hannes Reinecke
2025-06-27  7:38     ` Damien Le Moal
2025-06-27  1:11 ` [PATCH 5/6] ata: ahci: Clarify mobile_lpm_policy description Damien Le Moal
2025-06-27  6:05   ` Hannes Reinecke
2025-06-27  1:11 ` [PATCH 6/6] ata: libata-eh: Move and rename ata_eh_set_lpm() Damien Le Moal
2025-06-27  6:05   ` Hannes Reinecke

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=5b3d302b-c4e5-4061-959c-e60b1ec1bc6a@kernel.org \
    --to=dlemoal@kernel.org \
    --cc=cassel@kernel.org \
    --cc=hare@suse.de \
    --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).