From: Niklas Cassel <Niklas.Cassel@wdc.com>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>
Cc: "Limonciello, Mario" <Mario.Limonciello@amd.com>,
Paul Menzel <pmenzel@molgen.mpg.de>,
Hans de Goede <hdegoede@redhat.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH v2 3/3] ata: ahci: Skip 200 ms debounce delay for AMD 300 Series Chipset SATA Controller
Date: Wed, 21 Sep 2022 19:18:58 +0000 [thread overview]
Message-ID: <YytjoUsiXAH9cMPf@x1-carbon> (raw)
In-Reply-To: <cf2d8276-ee36-9923-1444-1dd7d489b172@opensource.wdc.com>
On Wed, Sep 21, 2022 at 02:01:24PM +0900, Damien Le Moal wrote:
> On 9/14/22 00:28, Limonciello, Mario wrote:
> >
> > I think what happened here is there was related patches from another party
> > that got tangled up with this.
>
> Niklas and I are investigating this again now because Niklas discovered that
> one AMD AHCI adapter leads to drive resets when the drive goes to low power
> mode. The adapter is:
>
> SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA
> Controller [AHCI mode] [1022:7901] (rev 51)
>
> If we switch to performance mode (no LPM), the reset disapears. But if LPM
> is enabled, any command sent after the disk goes to low power mode (device
> initiated), there is a link reset...
FTR, I sent out a patch for this issue:
https://lore.kernel.org/linux-ide/20220921155753.231770-1-niklas.cassel@wdc.com/T/#u
Kind regards,
Niklas
prev parent reply other threads:[~2022-09-21 19:19 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 21:24 [PATCH v2 1/3] ata: ahci: Add new board low_power_no_debounce_delay Paul Menzel
2022-03-21 21:24 ` [PATCH v2 2/3] ata: ahci: Skip 200 ms debounce delay for AMD FCH SATA Controller Paul Menzel
2022-03-21 21:24 ` [PATCH v2 3/3] ata: ahci: Skip 200 ms debounce delay for AMD 300 Series Chipset " Paul Menzel
2022-03-21 21:51 ` Limonciello, Mario
2022-03-23 5:01 ` Damien Le Moal
2022-03-23 6:55 ` Paul Menzel
2022-03-23 8:24 ` Damien Le Moal
2022-03-23 8:36 ` Paul Menzel
2022-03-31 14:42 ` Paul Menzel
2022-03-31 23:04 ` Damien Le Moal
2022-04-01 5:18 ` Paul Menzel
2022-04-01 7:23 ` Damien Le Moal
2022-05-31 16:18 ` Paul Menzel
2022-05-31 16:21 ` Paul Menzel
2022-05-31 16:24 ` Paul Menzel
2022-06-01 8:58 ` Damien Le Moal
2022-08-30 9:05 ` Paul Menzel
2022-08-31 22:13 ` Damien Le Moal
2022-09-13 15:23 ` Paul Menzel
2022-09-13 15:28 ` Limonciello, Mario
2022-09-14 8:26 ` Damien Le Moal
2022-09-21 5:01 ` Damien Le Moal
2022-09-21 19:18 ` Niklas Cassel [this message]
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=YytjoUsiXAH9cMPf@x1-carbon \
--to=niklas.cassel@wdc.com \
--cc=Mario.Limonciello@amd.com \
--cc=damien.lemoal@opensource.wdc.com \
--cc=hdegoede@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=pmenzel@molgen.mpg.de \
/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.