From: Niklas Cassel <cassel@kernel.org>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH 09/10] ata: libata-core: Reduce the number of messages signaling broken LPM
Date: Mon, 30 Jun 2025 17:08:16 +0200 [thread overview]
Message-ID: <aGKoYG4cI05iFkpx@ryzen> (raw)
In-Reply-To: <20250630062637.258329-10-dlemoal@kernel.org>
On Mon, Jun 30, 2025 at 03:26:36PM +0900, Damien Le Moal wrote:
> ata_dev_config_lpm() prints the message "LPM support broken, forcing
> max_power" for devices that have the ATA_QUIRK_NOLPM quirk flag set.
> This messages is repeated for every device revalidation, which is not
> necessary, but also erroneously printed for devices without a broken LPM
> support when connected to a port that does not support LPM (e.g. because
> the port is an external one with hotplug capability).
>
> Since in all cases the device port target_lpm_policy is set to
> ATA_LPM_MAX_POWER, avoid the "LPM broken" message repetition and
> erroneous output by generating it only if the port target_lpm_policy is
> not already set to ATA_LPM_MAX_POWER.
>
> This change will suppress the "LPM broken" message for genuine cases of
> a device having broken LPM if the initial LPM policy is set to
> ATA_LPM_MAX_POWER through CONFIG_SATA_MOBILE_LPM_POLICY. This is not a
> problem as the ATA_LPM_MAX_POWER policy implies that LPM is disabled and
> unused, which is safe for devices with broken LPM.
>
> Signed-off-by: Damien Le Moal <dlemoal@kernel.org>
Reviewed-by: Niklas Cassel <cassel@kernel.org>
next prev parent reply other threads:[~2025-06-30 15:08 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 6:26 [PATCH 00/10] Improve link power management Damien Le Moal
2025-06-30 6:26 ` [PATCH 01/10] ata: libata-core: Introduce ata_dev_config_lpm() Damien Le Moal
2025-06-30 14:46 ` Niklas Cassel
2025-07-01 6:09 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 02/10] ata: libata-core: Move device LPM quirk settings to ata_dev_config_lpm() Damien Le Moal
2025-06-30 14:47 ` Niklas Cassel
2025-07-01 6:13 ` Hannes Reinecke
2025-07-01 6:43 ` Damien Le Moal
2025-07-01 7:19 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 03/10] ata: libata-core: Advertize device support for DIPM and HIPM features Damien Le Moal
2025-06-30 14:47 ` Niklas Cassel
2025-07-01 6:14 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 04/10] ata: libata-eh: Avoid unnecessary resets when revalidating devices Damien Le Moal
2025-06-30 14:47 ` Niklas Cassel
2025-07-01 6:23 ` Hannes Reinecke
2025-07-01 6:48 ` Damien Le Moal
2025-07-01 7:21 ` Hannes Reinecke
2025-07-01 9:24 ` Niklas Cassel
2025-07-01 9:25 ` Damien Le Moal
2025-06-30 6:26 ` [PATCH 05/10] ata: libata-sata: Disallow changing LPM state if not supported Damien Le Moal
2025-06-30 14:49 ` Niklas Cassel
2025-07-01 6:23 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 06/10] ata: ahci: Disable DIPM if host lacks support Damien Le Moal
2025-06-30 14:50 ` Niklas Cassel
2025-07-01 6:23 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 07/10] ata: ahci: Disallow LPM policy control for external ports Damien Le Moal
2025-06-30 14:50 ` Niklas Cassel
2025-07-01 6:24 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 08/10] ata: ahci: Disallow LPM policy control if not supported Damien Le Moal
2025-06-30 8:30 ` Sergey Shtylyov
2025-06-30 15:07 ` Niklas Cassel
2025-07-01 6:25 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 09/10] ata: libata-core: Reduce the number of messages signaling broken LPM Damien Le Moal
2025-06-30 15:08 ` Niklas Cassel [this message]
2025-07-01 6:26 ` Hannes Reinecke
2025-06-30 6:26 ` [PATCH 10/10] ata: libata_eh: Add debug messages to ata_eh_link_set_lpm() Damien Le Moal
2025-06-30 15:11 ` Niklas Cassel
2025-06-30 15:25 ` Sergey Shtylyov
2025-07-01 6:27 ` 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=aGKoYG4cI05iFkpx@ryzen \
--to=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--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).