From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Ray Jui <ray.jui@broadcom.com>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
linux-pci@vger.kernel.org, Tomasz Nowicki <tn@semihalf.com>,
Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [RFC] ARM64, PCIe, annd ACPI
Date: Thu, 9 Aug 2018 16:41:51 +0100 [thread overview]
Message-ID: <20180809154151.GB20329@red-moon> (raw)
In-Reply-To: <9b5b5918-1492-df65-5b63-678b4a35ecb9@broadcom.com>
On Thu, Aug 09, 2018 at 07:57:52AM -0700, Ray Jui wrote:
[...]
> >As I said ARM64 ACPI PCI kernel support is in the mainline today and I
> >am not willing to merge any more MCFG quirks at driver level - the
> >information is out there, it is public and must be followed, either
> >designers do that or no ACPI PCI support on your platform, sorry.
> >
> >Lorenzo
> >
>
> I just want to make sure I interpret this properly. This means if
> the PCIe controller hardware does not support ECAM, there's pretty
> much no way around it with SW based workaround going forward with
> mainline kernel?
Yes.
> What about for the PCIe controller that was designed a few years back?
It will bootstrap with DT :)
Thanks,
Lorenzo
next prev parent reply other threads:[~2018-08-09 18:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 0:10 [RFC] ARM64, PCIe, annd ACPI Ray Jui
2018-08-08 2:10 ` Bjorn Helgaas
2018-08-08 18:46 ` Ray Jui
2018-08-08 9:38 ` Lorenzo Pieralisi
2018-08-08 18:49 ` Ray Jui
2018-08-09 8:59 ` Lorenzo Pieralisi
2018-08-09 14:57 ` Ray Jui
2018-08-09 15:41 ` Lorenzo Pieralisi [this message]
2018-08-09 15:44 ` Ray Jui
2018-08-09 16:00 ` Lorenzo Pieralisi
2018-08-09 16:04 ` Ray Jui
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=20180809154151.GB20329@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=bhelgaas@google.com \
--cc=linux-pci@vger.kernel.org \
--cc=ray.jui@broadcom.com \
--cc=tn@semihalf.com \
--cc=vladimir.olovyannikov@broadcom.com \
/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