From: Jayachandran C <jchandra@broadcom.com>
To: <linux-pci@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>
Cc: Jayachandran C <jchandra@broadcom.com>
Subject: [RFC PATCH 0/3] ACPI PCI support for arm64
Date: Thu, 3 Dec 2015 03:54:43 +0530 [thread overview]
Message-ID: <1449095086-5138-1-git-send-email-jchandra@broadcom.com> (raw)
This is a very simple and generic implementation of a PCI host controller
based on ACPI. This approach does not pull in the MMCONFIG and ECAM code
from x86.
It is important for us to have a working ACPI based PCI host controller
implementation for arm64, so I thought I would post this as a simple
and less disruptive alternative.
This is tested with arm64 QEMU and OVMF. Comments are very welcome.
Thanks,
JC.
Jayachandran C (3):
arm64: pci: Add ACPI support
pci: Handle NULL parent in pci_bus_assign_domain_nr
pci/host : Add a generic ACPI based host controller
arch/arm64/kernel/pci.c | 47 ++++++++-
drivers/pci/host/Kconfig | 7 ++
drivers/pci/host/Makefile | 1 +
drivers/pci/host/pci-host-acpi.c | 211 +++++++++++++++++++++++++++++++++++++++
drivers/pci/pci.c | 7 +-
5 files changed, 270 insertions(+), 3 deletions(-)
create mode 100644 drivers/pci/host/pci-host-acpi.c
--
1.9.1
next reply other threads:[~2015-12-02 22:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-02 22:24 Jayachandran C [this message]
2015-12-02 22:24 ` [PATCH 1/3] arm64: pci: Add ACPI support Jayachandran C
2015-12-02 22:24 ` [PATCH 2/3] pci: Handle NULL parent in pci_bus_assign_domain_nr Jayachandran C
2015-12-02 22:24 ` [PATCH 3/3] pci/host : Add a generic ACPI based host controller Jayachandran C
[not found] ` <20151203105628.GD2110@red-moon>
2015-12-03 11:02 ` [RFC PATCH 0/3] ACPI PCI support for arm64 Lorenzo Pieralisi
[not found] ` <20151203184128.GA5890@jayachandranc.netlogicmicro.com>
2015-12-04 12:43 ` Lorenzo Pieralisi
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=1449095086-5138-1-git-send-email-jchandra@broadcom.com \
--to=jchandra@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
/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).