Linux PCI subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jose Ignacio Tornos Martinez" <jtornosm@redhat.com>
Cc: linux-pci@vger.kernel.org
Subject: Re: [PATCH v2] PCI: Disable broken FLR on MediaTek MT7925
Date: Fri, 08 May 2026 21:22:07 +0000	[thread overview]
Message-ID: <20260508212208.2544FC2BCB0@smtp.kernel.org> (raw)
In-Reply-To: <20260508145153.717641-1-jtornosm@redhat.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete implementation: Missing MediaTek MT7925 device ID `0x0717` in the FLR quirk list.
--

commit 2cb7494208e4978bb4c09df85e374c7eac96b74d
Author: Jose Ignacio Tornos Martinez <jtornosm@redhat.com>

PCI: Disable broken FLR on MediaTek MT7925

The MediaTek MT7925 WiFi device advertises FLR capability but its
implementation is broken, causing reset to fail and leaving the device in
an undefined state. This commit disables FLR for the device so the PCI core
can fall back to working reset methods like PM reset or bus reset.

> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
> index caaed1a01dc02..e49136ac5dbfb 100644
> --- a/drivers/pci/quirks.c
> +++ b/drivers/pci/quirks.c
[ ... ]
> @@ -5619,6 +5620,7 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x17f0, quirk_no_flr);
>  DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);
>  DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_no_flr);
>  DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_MEDIATEK, 0x0616, quirk_no_flr);
> +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_MEDIATEK, 0x7925, quirk_no_flr);

Should this quirk also include the 0x0717 device ID?

The MT7925 driver in drivers/net/wireless/mediatek/mt76/mt7925/pci.c
registers and supports two MediaTek device IDs: 0x7925 and 0x0717. Both IDs
share the same initialization logic, MAC behavior, and firmware.

Since 0x0717 belongs to the same MT7925 family and shares the same
underlying hardware IP, is it likely to have the same broken FLR
implementation?

If so, users with the 0x0717 variant might still experience the VFIO
passthrough undefined state issue if the device is omitted from this quirk
list.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260508145153.717641-1-jtornosm@redhat.com?part=1

      parent reply	other threads:[~2026-05-08 21:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-08 14:51 [PATCH v2] PCI: Disable broken FLR on MediaTek MT7925 Jose Ignacio Tornos Martinez
2026-05-08 14:51 ` [PATCH v2] PCI: Force PM reset for Qualcomm devices with NoSoftRst+ Jose Ignacio Tornos Martinez
2026-05-08 17:16   ` Alex Williamson
2026-05-08 21:21   ` sashiko-bot
2026-05-08 21:22 ` sashiko-bot [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=20260508212208.2544FC2BCB0@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=jtornosm@redhat.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=sashiko@lists.linux.dev \
    /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