public inbox for linux-ide@vger.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: Eric <eric.4.debian@grabatoulnz.fr>,
	Salvatore Bonaccorso <carnil@debian.org>,
	Mario Limonciello <mario.limonciello@amd.com>,
	Christoph Hellwig <hch@infradead.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Damien Le Moal <dlemoal@kernel.org>,
	Jian-Hong Pan <jhp@endlessos.org>,
	regressions@lists.linux.dev, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, linux-ide@vger.kernel.org,
	Dieter Mummenschanz <dmummenschanz@web.de>
Subject: Re: Regression from 7627a0edef54 ("ata: ahci: Drop low power policy board type") on reboot (but not cold boot)
Date: Thu, 13 Mar 2025 19:47:11 +0100	[thread overview]
Message-ID: <6d125c69-35b2-45b5-9790-33f3ea06f171@redhat.com> (raw)
In-Reply-To: <Z9L5p6hTp6MATJ80@ryzen>

Hi,

On 13-Mar-25 4:28 PM, Niklas Cassel wrote:
> Hello Hans,
> 
> On Thu, Mar 13, 2025 at 04:13:24PM +0100, Hans de Goede wrote:
>>>
>>> Considering that DIPM seems to work fine on the Maxtor drive, I guess your
>>> initial suggestion of a Samsung only quirk which only disables LPM on ATI
>>> is the best way?
>>
>> I have no objections against going that route, except that I guess this
>> should then be something like ATA_QUIRK_NO_DIPM_ON_ATI to not loose the
>> other LPM modes / savings? AFAIK/IIRC there still is quite some powersaving
>> to be had without DIPM.
> 
> I was thinking like your original suggestion, i.e. setting:
> ATA_QUIRK_NO_LPM_ON_ATI
> 
> for all the Samsung devices that currently have:
> ATA_QUIRK_NO_NCQ_ON_ATI
> 
> Considering that this Samsung device only supports DIPM
> (and not HIPM), I'm guessing the same is true for the other
> Samsung devices as well.

Ah I see ...

> So we might as well just do:
> ATA_QUIRK_NO_LPM_ON_ATI

Yes I agree and that will nicely work as a combination of
ATA_QUIRK_NO_LPM + ATA_QUIRK_NO_NCQ_ON_ATI functionality
so using tested code-paths in a slightly new way.

Regards,

Hans




> to disable both HIPM and DIPM
> (since only DIPM would have been enabled without this quirk anyway).
> 
> 
>> Yes the most severe problems do seem to come from that specific mix,
>> although the long list of other ATI controller quirks also shows those
>> controllers are somewhat finicky.
> 
> Definitely!
> 
> 
> Kind regards,
> Niklas
> 


  reply	other threads:[~2025-03-13 18:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-02 16:03 Regression from 7627a0edef54 ("ata: ahci: Drop low power policy board type") on reboot (but not cold boot) Salvatore Bonaccorso
2025-03-02 16:20 ` Christian Heusel
2025-03-02 19:28 ` Salvatore Bonaccorso
2025-03-02 19:32 ` Niklas Cassel
2025-03-02 20:32   ` Eric
2025-03-03  6:25     ` Niklas Cassel
     [not found]       ` <8b1cbfd4-6877-48ef-b17d-fc10402efbf7@grabatoulnz.fr>
2025-03-03 18:04         ` Eric
2025-03-06 10:37         ` Niklas Cassel
2025-03-06 10:40           ` Niklas Cassel
2025-03-06 12:27             ` Eric
2025-03-07  9:53               ` Niklas Cassel
2025-03-08 10:05                 ` Eric
2025-03-08 18:20                   ` Eric
2025-03-10 16:24                   ` Niklas Cassel
2025-03-17 16:33                     ` Mario Limonciello
2025-03-10  9:34                 ` Hans de Goede
2025-03-10 18:13                   ` Niklas Cassel
2025-03-10 20:12                     ` Hans de Goede
2025-03-11 14:14                       ` Niklas Cassel
2025-03-12 17:11                         ` Eric
2025-03-12 21:39                           ` Eric
2025-03-13 12:21                             ` Niklas Cassel
2025-03-13 10:04                         ` Hans de Goede
2025-03-13 12:48                           ` Niklas Cassel
2025-03-13 15:13                             ` Hans de Goede
2025-03-13 15:28                               ` Niklas Cassel
2025-03-13 18:47                                 ` Hans de Goede [this message]
2025-03-17 17:09                                   ` Niklas Cassel
2025-03-17 19:15                                     ` Eric
2025-03-18  0:04                                       ` Eric
2025-03-18  9:10                                         ` Niklas Cassel
2025-03-22 19:11                                           ` Eric

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=6d125c69-35b2-45b5-9790-33f3ea06f171@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=carnil@debian.org \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=dmummenschanz@web.de \
    --cc=eric.4.debian@grabatoulnz.fr \
    --cc=hch@infradead.org \
    --cc=jhp@endlessos.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=regressions@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox