linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ray Jui <ray.jui@broadcom.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	linux-pci@vger.kernel.org, Tomasz Nowicki <tn@semihalf.com>
Cc: Vladimir Olovyannikov <vladimir.olovyannikov@broadcom.com>,
	BCM Kernel Feedback <bcm-kernel-feedback-list@broadcom.com>
Subject: [RFC] ARM64, PCIe, annd ACPI
Date: Tue, 7 Aug 2018 17:10:15 -0700	[thread overview]
Message-ID: <89484aa0-08c4-0cff-500d-407d21e2f5fd@broadcom.com> (raw)

Hi Lorenzo/Bjorn,

I have a question on PCIe controller APCI support on ARM64 based systems.

If my understanding of the implementation of "pci_acpi_scan_root" under 
"arch/arm64/kernel/pci.c" is correct, it appears 
"pci_acpi_setup_ecam_mapping" is called within "pci_acpi_scan_root".

Does that mean for a PCIe host controller on ARM64 to support ACPI, it 
needs to support ECAM and MMIO based access to the configuration space 
registers?

If the above statement is true, does it imply that any PCIe controller 
on ARM64 that does not support MMIO based access to the config space 
register cannot have ACPI support?

I might be missing something here so I'd like to send out this email and 
get your opinion on this. Your feedback is highly appreciated.

Regards,

Ray

             reply	other threads:[~2018-08-08  2:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-08  0:10 Ray Jui [this message]
2018-08-08  2:10 ` [RFC] ARM64, PCIe, annd ACPI 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

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=89484aa0-08c4-0cff-500d-407d21e2f5fd@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;
as well as URLs for NNTP newsgroup(s).