From: Lorenzo Pieralisi <firstname.lastname@example.org>
To: Thierry Reding <email@example.com>
Cc: Vidya Sagar <firstname.lastname@example.org>,
email@example.com, Bjorn Helgaas <firstname.lastname@example.org>,
"Rafael J. Wysocki" <email@example.com>,
Len Brown <firstname.lastname@example.org>,
Andrew Murray <email@example.com>,
firstname.lastname@example.org, LKML <email@example.com>,
firstname.lastname@example.org, email@example.com, firstname.lastname@example.org
Subject: Re: [PATCH] PCI: Add MCFG quirks for Tegra194 host controllers
Date: Thu, 23 Jan 2020 10:49:41 +0000 [thread overview]
Message-ID: <20200123104941.GA7179@e121166-lin.cambridge.arm.com> (raw)
On Tue, Jan 21, 2020 at 02:44:35PM +0100, Thierry Reding wrote:
> On Mon, Jan 20, 2020 at 03:18:49PM +0000, Lorenzo Pieralisi wrote:
> > On Mon, Jan 20, 2020 at 12:10:42PM +0100, Thierry Reding wrote:
> > [...]
> > > > > Currently the BSP has the kernel booting through Device Tree mechanism
> > > > > and there is a plan to support UEFI based boot as well in the future software
> > > > > releases for which we need this quirky way of handling ECAM.
> > > > > Tegra194 is going to be the only and last chip with this issue and next chip
> > > > > in line in Tegra SoC series will be fully compliant with ECAM.
> > > >
> > > > ACPI on ARM64 works on a standard subset of systems, defined by the
> > > > ARM SBSA:
> > > >
> > > > http://infocenter.arm.com/help/topic/com.arm.doc.den0029c/Server_Base_System_Architecture_v6_0_ARM_DEN_0029C_SBSA_6_0.pdf
> > >
> > > I don't understand what you're saying here. Are you saying that you want
> > > to prevent vendors from upstreaming code that they need to support their
> > > ACPI based platforms? I understand that the lack of support for proper
> > > ECAM means that a platform will not be SBSA compatible, but I wasn't
> > > aware that lack of SBSA compatibility meant that a platform would be
> > > prohibited from implementing ACPI support in an upstream kernel.
> > ACPI on ARM64 requires a set of HW components described in the SBSA.
> > If those HW requirements are not fulfilled you can't bootstrap an ARM64
> > system with ACPI - it is as simple as that.
> That's an odd statement. We do in fact have an ARM64 system that doesn't
> fulfill the ECAM requirement and yet it successfully boots with ACPI.
I know very well (but that's not a reason to break the PCIe
Still, the mistake you are making is thinking that ACPI compliancy
stops at the MCFG quirk. Adding another quirk to the MCFG list will make
PCI enumerates but there is more to that, eg MSI/IOMMU and that's
just an example.
There are platforms in that MCFG list that eg can't do MSI which
basically means they are useless - you look at it as yet another hook
into MCFG, I look at it with history in mind and from an ACPI ARM64
So first thing to do is to post full support for this host controller
inclusive of MSI/INTx (which AFAICS is another piece of HW that is
not SBSA compliant since DWC uses a funnel to trigger MSIs) and
IOMMU, then we will see how to proceed.
Look at this (and again, that's just an example but AFAICS it applies to
this host bridge as well):
> > It is not even appropriate
> > to discuss this on a Linux mailing list anymore since it is HW
> > requirements and it has been public information since ACPI on ARM64 was
> > first enabled.
> Erm... we're discussing Linux patches. Why would it be inappropriate to
> discuss them on a Linux mailing list?
I am not discussing Linux patches at all - I am telling you that the
DWC host controller is not a) PCIe spec compliant b) SBSA compliant
and there is nothing to review from a Linux kernel code perspective.
This is just another quirk to enumerate with ACPI a non-compliant
system, if Bjorn is willing to take it go for it.
> > > > These patches will have to be carried out of tree, the MCFG quirk
> > > > mechanism (merged as Bjorn said more than three years ago) was supposed
> > > > to be a temporary plaster to bootstrap server platforms with teething
> > > > issues, the aim is to remove it eventually not to add more code to it
> > > > indefinitely.
> > >
> > > Now, I fully agree that quirks are suboptimal and we'd all prefer if we
> > > didn't have to deal with them. Unfortunately the reality is that
> > > mistakes happen and hardware doesn't always work the way we want it to.
> > > There's plenty of other quirk mechanisms in the kernel, and frankly this
> > > one isn't really that bad in comparison.
> > Because you don't have to maintain it ;) - I think I said what I had to
> > say about the MCFG mechanism in the past - it has been three years
> > and counting - it is time to remove it rather that adding to it.
> What makes you think you can simply remove this without breaking support
> for all of the devices that currently rely on the quirks?
Don't you think I know ? I said "eventually" for a reason, read what
> > > > So I am afraid but this quirk (and any other coming our way) will not be
> > > > merged in an upstream kernel anymore - for any queries please put Nvidia
> > > > in touch.
> > >
> > > Again, I don't understand what you're trying to achieve here. You seem
> > > to be saying that we categorically can't support this hardware because
> > > it isn't fully SBSA compatible.
> > I am not trying to achieve anything - I am just stating public
> > information - let me repeat it again for interested readers: to
> > bootstrap an ARM64 system with ACPI the platform HW design must follow
> > the SBSA guidelines.
> Can you clarify for me where I can find this public information? What
> I've been able to find suggests that that SBSA-compliant systems would
> typically run ACPI, but I can't find anything about SBSA compliance
> being a prerequisite for booting a system with ACPI.
> I can understand why someone might *wish* for that to always be true,
> but it seems to be a bit far removed from reality.
It is reality and it is not a *wish*, Nvidia will comply - even if
*eventually* we end up merging this code.
> > > Do you have any alternative suggestions on how we can support this in an
> > > upstream kernel?
> > Booting with a device tree ?
> We can already do that, but should that prevent us from making UEFI and
> ACPI an alternative boot mechanism?
Why do you need ACPI support ? What for ?
> > > We realized a while ago that we cannot achieve proper ECAM on Tegra194
> > > because of some issues with the hardware and we've provided this as
> > > feedback to the hardware engineers. As a result, the next generation of
> > > Tegra should no longer suffer from these issues.
> > We will bootstrap next generation Tegra with ACPI then, there are
> > SBSA tests available for compliancy - again, that's a matter for
> > Nvidia and Arm to settle, not a mailing list discussion.
> I don't understand why you keep insisting on this. The mailing lists are
> where kernel patches are discussed, are they not?
> > > As for Tegra194, that chip taped out two years ago and it isn't possible
> > > to make it fully ECAM compliant other than by revising the chip, which,
> > > frankly, isn't going to happen.
> > >
> > > So I see two options here: either we find a way of dealing with this, by
> > > either merging this quirk or finding an alternative solution, or we make
> > > the decision that some hardware just can't be supported.
> > >
> > > The former is fairly common, whereas I've never heard of the latter.
> > What does this mean ? Should I wreck the upstream kernel to make it boot
> > with ACPI on *any* ARM64 platform out there then ?
> Heh... you must have a very low opinion of the upstream kernel if you
> think merging these 100 lines of code is going to wreck it.
I have a very high opinion of the upstream kernel and that's why
as I said above I think in terms of overall ACPI ARM64 maintainership
rather than a platform quirk to get ACPI PCI enumeration going.
> And if you look at the patch, the bulk (95/109 lines) is actually in the
> Tegra194 PCIe driver and only 14/109 lines are added to the MCFG quirks.
> That's hardly the kind of change that's going to wreck the kernel.
See above, show us the rest of the story.
> > My stance is clear above and the ACPI PCI programming model - inclusive
> > of firmware - has been there since ACPI was deployed, if ACPI support
> > is required HW must comply, either that or it is out of tree patches
> > and I can't be blamed for that.
> Looking at the existing quirks table, there's evidently a number of
> people that didn't get the memo. The issue seems to be fairly common,
> yet for some reason you're singling out Tegra194.
The issue is not very common at all. I said it before and I repeat it
again: those MCFG quirks were merged more than three years ago to help
bootstrap ACPI ARM64 ecosystem on early HW and ACPI for ARM64 is meant
for server (SBSA/SBBR compliant) systems, for other platforms DT is the
firmware of choice, ACPI on those does not work well (and *I* will have
to work around it).
I am not singling out anybody, read the mailing lists and you will
realize. You asked for this patch to be reviewed, I told you what
my thoughts are and this patch implications - you want to go ahead,
ask Bjorn to merge it but at least we do it with the broader
consequences in mind.
next prev parent reply other threads:[~2020-01-23 10:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-03 17:49 [PATCH] PCI: Add MCFG quirks for Tegra194 host controllers Vidya Sagar
2020-01-03 18:04 ` Bjorn Helgaas
2020-01-04 3:44 ` Vidya Sagar
2020-01-17 12:17 ` Lorenzo Pieralisi
2020-01-20 11:10 ` Thierry Reding
2020-01-20 15:18 ` Lorenzo Pieralisi
2020-01-21 13:44 ` Thierry Reding
2020-01-23 10:49 ` Lorenzo Pieralisi [this message]
2020-02-06 16:46 ` Thierry Reding
2020-02-07 14:50 ` Bjorn Helgaas
2020-02-07 16:51 ` Thierry Reding
2020-02-07 18:34 ` Bjorn Helgaas
2020-01-04 21:53 ` kbuild test robot
2020-01-06 8:27 ` [PATCH V2] " Vidya Sagar
2020-01-10 19:14 ` [PATCH V3 0/2] " Vidya Sagar
2020-01-10 19:14 ` [PATCH V3 1/2] arm64: tegra: Re-order PCIe aperture mappings to support ACPI boot Vidya Sagar
2020-06-29 13:31 ` Jon Hunter
2020-06-30 10:52 ` Vidya Sagar
2020-01-10 19:15 ` [PATCH V3 2/2] PCI: Add MCFG quirks for Tegra194 host controllers Vidya Sagar
2020-01-17 11:42 ` Thierry Reding
2021-03-05 21:57 ` Bjorn Helgaas
2021-03-05 23:04 ` Krzysztof Wilczyński
2021-04-16 13:45 ` Vidya Sagar
2021-04-16 13:45 ` [PATCH V4] " Vidya Sagar
2021-04-16 19:06 ` Bjorn Helgaas
2021-05-13 9:40 ` [PATCH V3 2/2] " Qu Wenruo
2021-05-13 13:05 ` Vidya Sagar
2020-01-16 17:18 ` [PATCH V3 0/2] " Vidya Sagar
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).