From: Niklas Cassel <cassel@kernel.org>
To: Andy Yang <andyybtc79@gmail.com>
Cc: Damien Le Moal <dlemoal@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: Issue in the patch "ata: ahci: Disallow LPM for ASUSPRO-D840SA motherboard"
Date: Sat, 21 Jun 2025 20:19:45 +0200 [thread overview]
Message-ID: <aFb3wXAwJSSJUB7o@ryzen> (raw)
In-Reply-To: <CAGEiHrCs_V8w3cTCY44rgQ0nZrhAo7=0jAn0=79HZxMJ5wEp8g@mail.gmail.com>
+linux-ide
Hello Andy,
On Sat, Jun 21, 2025 at 06:06:10PM +0000, Andy Yang wrote:
> Hi Damien & Niklas,
>
> This patch isn't working. I've mentioned this in several previous emails as
> replies, from the time it was applied to the libata work tree to its being
> merged into stable. This is my third email addressing this issue.
This is the first email that I see about this issue.
I also don't find any other report about this on the mailing list,
perhaps you were sending your email using HTML instead of plain text?
>
> The DMI_PRODUCT_VERSION field is incorrect, we should consider using
> DMI_MATCH(DMI_PRODUCT_NAME,
> "ASUSPRO D840MB_M840SA") or DMI_MATCH(DMI_BOARD_NAME, "D840MB") instead. If
> you require additional DMI information about this model, I included it in a
> previous reply to the patch mailing list.
Does this patch solve your problem:
diff --git a/drivers/ata/ahci.c b/drivers/ata/ahci.c
index e5e5c2e81d09..aa93b0ecbbc6 100644
--- a/drivers/ata/ahci.c
+++ b/drivers/ata/ahci.c
@@ -1450,7 +1450,7 @@ static bool ahci_broken_lpm(struct pci_dev *pdev)
{
.matches = {
DMI_MATCH(DMI_SYS_VENDOR, "ASUSTeK COMPUTER INC."),
- DMI_MATCH(DMI_PRODUCT_VERSION, "ASUSPRO D840MB_M840SA"),
+ DMI_MATCH(DMI_PRODUCT_NAME, "ASUSPRO D840MB_M840SA"),
},
/* 320 is broken, there is no known good version. */
},
Kind regards,
Niklas
parent reply other threads:[~2025-06-21 18:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGEiHrCs_V8w3cTCY44rgQ0nZrhAo7=0jAn0=79HZxMJ5wEp8g@mail.gmail.com>]
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=aFb3wXAwJSSJUB7o@ryzen \
--to=cassel@kernel.org \
--cc=andyybtc79@gmail.com \
--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).