Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Ray Jui <ray.jui@broadcom.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.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 09:04:52 -0700	[thread overview]
Message-ID: <a73ff84c-0fe1-4c13-e021-b41945f8e46a@broadcom.com> (raw)
In-Reply-To: <20180809160035.GC20329@red-moon>

Hi Lorenzo,

On 8/9/2018 9:00 AM, Lorenzo Pieralisi wrote:
> On Thu, Aug 09, 2018 at 08:44:34AM -0700, Ray Jui wrote:
>> Hi Lorenzo,
>>
>> On 8/9/2018 8:41 AM, Lorenzo Pieralisi wrote:
>>> 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 :)
>>
>> Okay, one more quick question, what about for distributions that
>> will eventually disable DT and force ACPI?
> 
> ACPI PCI support revolves around a FW model that requires, among other
> things, ECAM and its firmware description, MCFG table, to work.
> 
> If the host controller is not ECAM compliant it is not PCI firmware
> compliant, so it is not ACPI compliant, you can't run ACPI only
> distributions on it.
> 
> It is a model that has been run for decades in basically all
> ACPI based systems out there and there is not a reason to
> deviate from it, I understand the frustration but that's the
> way it is, sorry.
> 
> Thanks,
> Lorenzo
> 

Okay that draws the line. Thanks for confirming.

Ray

      reply	other threads:[~2018-08-09 18:30 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
2018-08-09 15:44           ` Ray Jui
2018-08-09 16:00             ` Lorenzo Pieralisi
2018-08-09 16:04               ` Ray Jui [this message]

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=a73ff84c-0fe1-4c13-e021-b41945f8e46a@broadcom.com \
    --to=ray.jui@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=bhelgaas@google.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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