All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Mario Limonciello <mario.limonciello@amd.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jian-Hong Pan <jhp@endlessos.org>,
	stable@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: [PATCH v2] ata: ahci: Do not enable LPM if no LPM states are supported by the HBA
Date: Wed, 19 Jun 2024 12:13:03 +0200	[thread overview]
Message-ID: <ZnKvLy4_a3U6835Q@ryzen.lan> (raw)
In-Reply-To: <4522f403-8419-4c59-b28b-9d460780c389@kernel.org>

On Wed, Jun 19, 2024 at 12:45:51PM +0900, Damien Le Moal wrote:
> On 6/19/24 00:28, Niklas Cassel wrote:
> > LPM consists of HIPM (host initiated power management) and DIPM
> > (device initiated power management).
> > 
> > ata_eh_set_lpm() will only enable HIPM if both the HBA and the device
> > supports it.
> > 
> > However, DIPM will be enabled as long as the device supports it.
> > The HBA will later reject the device's request to enter a power state
> > that it does not support (Slumber/Partial/DevSleep) (DevSleep is never
> > initiated by the device).
> > 
> > For a HBA that doesn't support any LPM states, simply don't set a LPM
> > policy such that all the HIPM/DIPM probing/enabling will be skipped.
> > 
> > Not enabling HIPM or DIPM in the first place is safer than relying on
> > the device following the AHCI specification and respecting the NAK.
> > (There are comments in the code that some devices misbehave when
> > receiving a NAK.)
> > 
> > Performing this check in ahci_update_initial_lpm_policy() also has the
> > advantage that a HBA that doesn't support any LPM states will take the
> > exact same code paths as a port that is external/hot plug capable.
> > 
> > Side note: the port in ata_port_dbg() has not been given a unique id yet,
> > but this is not overly important as the debug print is disabled unless
> > explicitly enabled using dynamic debug. A follow-up series will make sure
> > that the unique id assignment will be done earlier. For now, the important
> > thing is that the function returns before setting the LPM policy.
> > 
> > Fixes: 7627a0edef54 ("ata: ahci: Drop low power policy board type")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Niklas Cassel <cassel@kernel.org>
> > ---
> > Changes since v1: Add debug print as suggested by Mika.
> > 
> >  drivers/ata/ahci.c | 8 ++++++++
> >  1 file changed, 8 insertions(+)
> > 
> > diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
> > index 07d66d2c5f0d..5eb38fbbbecd 100644
> > --- a/drivers/ata/ahci.c
> > +++ b/drivers/ata/ahci.c
> > @@ -1735,6 +1735,14 @@ static void ahci_update_initial_lpm_policy(struct ata_port *ap)
> >  	if (ap->pflags & ATA_PFLAG_EXTERNAL)
> >  		return;
> >  
> > +	/* If no LPM states are supported by the HBA, do not bother with LPM */
> > +	if ((ap->host->flags & ATA_HOST_NO_PART) &&
> > +	    (ap->host->flags & ATA_HOST_NO_SSC) &&
> > +	    (ap->host->flags & ATA_HOST_NO_DEVSLP)) {
> 
> Nit: Maybe:
> 
> #define ATA_HOST_NO_LPM		\
> 	(ATA_HOST_NO_PART | ATA_HOST_NO_SSC | ATA_HOST_NO_DEVSLP)
> 
> and then the if becomes:
> 
> 	if ((ap->host->flags & ATA_HOST_NO_LPM) == ATA_HOST_NO_LPM) {
> 
> But no strong feelings about it. So:
> 
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>

Thank you for the R-b and your suggestion.

Personally, I do not think that your suggestion is significantly easier to
read than what is already there (especially with the comment to give
context).

My brain always has to read a:
if ((foo & bar) == bar)
twice anyway.

I guess a:
if (!ata_host_has_lpm(ap->host))
would be clearer, but considering that we wouldn't be able to use this
helper function anywhere else in the libata subsystem, I'm not sure if
it is worth it, so I will just apply this patch as is.


Kind regards,
Niklas

  reply	other threads:[~2024-06-19 10:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-18 15:28 [PATCH v2] ata: ahci: Do not enable LPM if no LPM states are supported by the HBA Niklas Cassel
2024-06-18 15:49 ` Mario Limonciello
2024-06-18 15:54 ` Mika Westerberg
2024-06-19  3:45 ` Damien Le Moal
2024-06-19 10:13   ` Niklas Cassel [this message]
2024-06-19 11:36 ` Niklas Cassel

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=ZnKvLy4_a3U6835Q@ryzen.lan \
    --to=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=jhp@endlessos.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=stable@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.