[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f2cc62e2-276b-e6a9-3b2c-48a61061be25@gmail.com>
Date: Sun, 22 Aug 2021 10:52:25 +0200
From: Florian Fainelli <f.fainelli@...il.com>
To: Jeremy Linton <jeremy.linton@....com>, linux-pci@...r.kernel.org
Cc: lorenzo.pieralisi@....com, nsaenz@...nel.org, bhelgaas@...gle.com,
rjw@...ysocki.net, lenb@...nel.org, robh@...nel.org, kw@...ux.com,
sdonthineni@...dia.com, stefan.wahren@...e.com,
bcm-kernel-feedback-list@...adcom.com, linux-acpi@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 2/4] PCI: brcmstb: Add ACPI config space quirk
On 8/19/2021 11:56 PM, Jeremy Linton wrote:
> The PFTF CM4 is an ACPI platform that isn't ECAM compliant. Its config
> space is in two parts. One part is for the root port registers and a
> second moveable window pointing at a device's 4K config space. Thus it
> doesn't have an MCFG, and any MCFG provided would be nonsense
> anyway. Instead, a Linux specific host bridge _DSD selects a custom
> ECAM ops and cfgres. The cfg op picks between those two regions while
> disallowing problematic accesses.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@....com>
Once you address Bjorn's feedback, feel free to add:
Acked-by: Florian Fainelli <f.fainelli@...il.com>
I do wonder if squashing patches 2 and 3 would make more sense,
otherwise we have a bcm2711_pcie_ops that is unused in patch 2.
--
Florian
Powered by blists - more mailing lists