[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240808050129.GH1532424@black.fi.intel.com>
Date: Thu, 8 Aug 2024 08:01:29 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Esther Shimanovich <eshimanovich@...omium.org>
Cc: Bjorn Helgaas <bhelgaas@...gle.com>, Rajat Jain <rajatja@...gle.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
Lukas Wunner <lukas@...ner.de>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, iommu@...ts.linux.dev,
Mario Limonciello <mario.limonciello@....com>
Subject: Re: [PATCH] PCI: Detect and trust built-in TBT chips
On Wed, Aug 07, 2024 at 05:15:36PM -0400, Esther Shimanovich wrote:
> On Wed, Aug 7, 2024 at 3:17 AM Mika Westerberg
> <mika.westerberg@...ux.intel.com> wrote:
> >
> > I suggest opening the heuristic here a bit more.
>
> Could you clarify what you mean by "opening the heuristic"?
> What details should I remove?
I mean not to remove anything but open up how we "detect" the built-in
controlllers.
> And add the links to
> > the Microsoft firmware document somewhere. These:
> >
> > https://learn.microsoft.com/en-us/windows-hardware/drivers/pci/dsd-for-pcie-root-ports#mapping-native-protocols-pcie-displayport-tunneled-through-usb4-to-usb4-host-routers
> > https://learn.microsoft.com/en-us/windows-hardware/drivers/pci/dsd-for-pcie-root-ports#identifying-externally-exposed-pcie-root-ports
>
> Is it good enough to have them in the commit message? Or should they
> be linked in probe.c?
IMHO they can be in the commit message.
Powered by blists - more mailing lists