linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "Bjorn Helgaas" <helgaas@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Rafael J . Wysocki" <rjw@rjwysocki.net>,
	"Mika Westerberg" <mika.westerberg@linux.intel.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	iain@orangesquash.org.uk,
	"Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
	"open list:PCI SUBSYSTEM" <linux-pci@vger.kernel.org>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v22] PCI: Avoid D3 at suspend for AMD PCIe root ports w/ USB4 controllers
Date: Thu, 5 Oct 2023 20:59:26 +0200	[thread overview]
Message-ID: <20231005185926.GA20935@wunner.de> (raw)
In-Reply-To: <6c02ad76-b205-40a3-9405-dd03e252414b@amd.com>

On Thu, Oct 05, 2023 at 01:52:34PM -0500, Mario Limonciello wrote:
> On 10/5/2023 13:47, Lukas Wunner wrote:
> > One belated thought I have on this is that it might be a better fit in
> > arch/x86/pci/fixups.c rather than drivers/pci/quirks.c.
> > 
> > The latter contains quirks for cards which could appear in any machine,
> > regardless of the arch.  But this seems to be specific to x86 machines.
> > I understand these xhci controllers are built into the SoC.
> > 
> > We've had complaints in the past from developers working with
> > space-constrained Mips routers that the generic quirks in
> > drivers/pci/quirks.c occupy too much memory:
> > 
> > https://lore.kernel.org/all/1482306784-29224-1-git-send-email-john@phrozen.org/
> > 
> > To cater to their needs, we need to keep in mind that arch-specific
> > quirks are kept outside of drivers/pci/quirks.c.
> > 
> > I apologize that this didn't occur to me earlier.
> 
> This seems like a bigger problem than this quirk.
> On a 6.5.y checkout I have on hand:
> 
> $ cat drivers/pci/quirks.c  | grep "VENDOR_ID_INTEL\|VENDOR_ID_AMD" | wc -l
> 412
> 
> Maybe we should move it all as a later follow up?

It's not that simple.  Some of these are for discrete chips which
may appear in any machine of any arch (think GPUs, Ethernet chips,
USB controllers etc, you might see these attached to a Raspberry Pi
and whatnot).

Thanks,

Lukas

  reply	other threads:[~2023-10-05 18:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-04 14:49 [PATCH v22] PCI: Avoid D3 at suspend for AMD PCIe root ports w/ USB4 controllers Mario Limonciello
2023-10-05 18:14 ` Bjorn Helgaas
2023-10-05 18:20   ` Mario Limonciello
2023-10-05 18:47   ` Lukas Wunner
2023-10-05 18:52     ` Mario Limonciello
2023-10-05 18:59       ` Lukas Wunner [this message]
2023-10-05 18:58     ` Bjorn Helgaas

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=20231005185926.GA20935@wunner.de \
    --to=lukas@wunner.de \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=bhelgaas@google.com \
    --cc=hdegoede@redhat.com \
    --cc=helgaas@kernel.org \
    --cc=iain@orangesquash.org.uk \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=mario.limonciello@amd.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rjw@rjwysocki.net \
    /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).