public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: linux-ide@vger.kernel.org,
	Linux ACPI <linux-acpi@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ATA: ACPI: Do not check ACPI_FADT_LOW_POWER_S0
Date: Wed, 24 Aug 2022 18:55:50 -0500	[thread overview]
Message-ID: <0b70fc12-6217-147f-c663-a1035738cf7d@amd.com> (raw)
In-Reply-To: <9c479bb6-bb57-9b5a-2fa5-7b4d1b840245@opensource.wdc.com>

On 8/24/22 18:54, Damien Le Moal wrote:
> On 2022/08/24 10:29, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> 
> The patch title should be "ata: ahci: ..."
> 
>>
>> The ACPI_FADT_LOW_POWER_S0 flag merely means that it is better to
>> use low-power S0 idle on the given platform than S3 (provided that
>> the latter is supported) and it doesn't preclude using either of
>> them (which of them will be used depends on the choices made by user
>> space).
>>
>> For this reason, there is no benefit from checking that flag in
>> ahci_update_initial_lpm_policy().
>>
>> First off, it cannot be a bug to do S3 with policy set to either
>> ATA_LPM_MIN_POWER_WITH_PARTIAL or ATA_LPM_MIN_POWER, because S3 can be
>> used on systems with ACPI_FADT_LOW_POWER_S0 set and it must work if
>> really supported, so the ACPI_FADT_LOW_POWER_S0 check is not needed to
>> protect the S3-capable systems from failing.
>>
>> Second, suspend-to-idle can be carried out on a system with
>> ACPI_FADT_LOW_POWER_S0 unset and it is expected to work, so if setting
>> policy to either ATA_LPM_MIN_POWER_WITH_PARTIAL or ATA_LPM_MIN_POWER is
>> needed to handle that case correctly, it should be done regardless of
>> the ACPI_FADT_LOW_POWER_S0 value.
>>
>> Accordingly, drop the ACPI_FADT_LOW_POWER_S0 check from
>> ahci_update_initial_lpm_policy().
>>
>> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>> ---
>>   drivers/ata/ahci.c |    3 +--
>>   1 file changed, 1 insertion(+), 2 deletions(-)
>>
>> Index: linux-pm/drivers/ata/ahci.c
>> ===================================================================
>> --- linux-pm.orig/drivers/ata/ahci.c
>> +++ linux-pm/drivers/ata/ahci.c
>> @@ -1610,8 +1610,7 @@ static void ahci_update_initial_lpm_poli
>>   	}
>>   
>>   #ifdef CONFIG_ACPI
>> -	if (policy > ATA_LPM_MED_POWER &&
>> -	    (acpi_gbl_FADT.flags & ACPI_FADT_LOW_POWER_S0)) {
>> +	if (policy > ATA_LPM_MED_POWER) {

If making this change, perhaps the #ifdef CONFIG_ACPI can drop too.

>>   		if (hpriv->cap & HOST_CAP_PART)
>>   			policy = ATA_LPM_MIN_POWER_WITH_PARTIAL;
>>   		else if (hpriv->cap & HOST_CAP_SSC)
>>
>>
>>
> 
> 


  reply	other threads:[~2022-08-24 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 17:29 [PATCH] ATA: ACPI: Do not check ACPI_FADT_LOW_POWER_S0 Rafael J. Wysocki
2022-08-24 23:54 ` Damien Le Moal
2022-08-24 23:55   ` Mario Limonciello [this message]
2022-08-25  0:13     ` 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=0b70fc12-6217-147f-c663-a1035738cf7d@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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