All of lore.kernel.org
 help / color / mirror / Atom feed
From: Niklas Cassel <cassel@kernel.org>
To: Andy Yang <andyybtc79@gmail.com>
Cc: Hans de Goede <hansg@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
	dlemoal@kernel.org
Subject: Re: [PATCH v2] ata: ahci: Use correct DMI identifier for ASUSPRO-D840SA LPM quirk
Date: Wed, 25 Jun 2025 10:52:04 +0200	[thread overview]
Message-ID: <aFu4tO4Wk1CyeJ9h@ryzen> (raw)
In-Reply-To: <CAGEiHrCWnC9BDi3DFDiAnoJxB_pFJpv-vcRU9jTmwb3Pxsg_Hw@mail.gmail.com>

On Wed, Jun 25, 2025 at 06:29:58AM +0000, Andy Yang wrote:
> On Tuesday, June 24, 2025, Damien Le Moal <dlemoal@kernel.org> wrote:
> > On 6/24/25 4:40 PM, Niklas Cassel wrote:
> >> ASUS store the board name in DMI_PRODUCT_NAME rather than
> >> DMI_PRODUCT_VERSION. (Apparently it is only Lenovo that stores the
> >> model-name in DMI_PRODUCT_VERSION.)
> >>
> >> Use the correct DMI identifier, DMI_PRODUCT_NAME, to match the
> >> ASUSPRO-D840SA board, such that the quirk actually gets applied.
> >>
> >> Cc: stable@vger.kernel.org
> >> Reported-by: Andy Yang <andyybtc79@gmail.com>
> >> Closes: https://lore.kernel.org/linux-ide/aFb3wXAwJSSJUB7o@ryzen/
> >> Fixes: b5acc3628898 ("ata: ahci: Disallow LPM for ASUSPRO-D840SA
> motherboard")
> >> Reviewed-by: Hans de Goede <hansg@kernel.org>
> >> Signed-off-by: Niklas Cassel <cassel@kernel.org>
> >
> > Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> >
> >
> > --
> > Damien Le Moal
> > Western Digital Research
> >
> 
> LGTM. This patch is tested work correctly.

Thank you, I will add your Tested-by tag.


> 
> Again, not sure if its model specific or motherboard specific, if its
> consider motherboard specific we should use (DMI_BOARD_NAME, D840MB)
> instead to match the board.

I don't know if it is model specific or motherboard specific.

Considering how bad this bug is (causing artifacts on the iGPU),
I guess we should hope that it is only the BIOS for your system,
and not for all D840MB boards.

So personally, I would go with the narrowest possible match (which
this patch currently does).

But, I would not be surprised if they actually managed to mess this
up for all boards. But until someone else reports the same problem,
I guess we should give them the benefit of the doubt.


Kind regards,
Niklas

  parent reply	other threads:[~2025-06-25  8:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-24  7:40 [PATCH v2] ata: ahci: Use correct DMI identifier for ASUSPRO-D840SA LPM quirk Niklas Cassel
2025-06-24  7:58 ` Damien Le Moal
     [not found]   ` <CAGEiHrCWnC9BDi3DFDiAnoJxB_pFJpv-vcRU9jTmwb3Pxsg_Hw@mail.gmail.com>
2025-06-25  8:52     ` Niklas Cassel [this message]
2025-06-25 13:20 ` Niklas Cassel
     [not found]   ` <CAGEiHrDtfwKGN+veFjgODf_0W4yJfDP0f6kqp-dF9xsypoH_0A@mail.gmail.com>
2025-06-26  8:24     ` 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=aFu4tO4Wk1CyeJ9h@ryzen \
    --to=cassel@kernel.org \
    --cc=andyybtc79@gmail.com \
    --cc=dlemoal@kernel.org \
    --cc=hansg@kernel.org \
    --cc=linux-ide@vger.kernel.org \
    --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.