From: Bjorn Helgaas <bhelgaas@google.com>
To: linux-pci@vger.kernel.org
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Duc Dang <dhdang@apm.com>,
linaro-acpi@lists.linaro.org, linux-kernel@vger.kernel.org,
linux-acpi@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Lv Zheng <lv.zheng@intel.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] PCI: Add information about describing PCI in ACPI
Date: Tue, 29 Nov 2016 15:39:48 -0600 [thread overview]
Message-ID: <20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com> (raw)
Here's another stab at this writeup. I'd appreciate any comments!
Changes from v1 to v2:
- Consumer/Producer is defined for Extended Address Space descriptors;
should be ignored for QWord/DWord/Word Address Space descriptors
- New arches may use Extended Address Space descriptors in PNP0A03 for
bridge registers, including ECAM (if the arch adds support for this)
- Add more details about MCFG and _CBA (Lv's suggestion)
- Incorporate Rafael's suggestions
---
Bjorn Helgaas (1):
PCI: Add information about describing PCI in ACPI
Documentation/PCI/00-INDEX | 2
Documentation/PCI/acpi-info.txt | 180 +++++++++++++++++++++++++++++++++++++++
2 files changed, 182 insertions(+)
create mode 100644 Documentation/PCI/acpi-info.txt
next reply other threads:[~2016-11-29 21:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 21:39 Bjorn Helgaas [this message]
2016-11-29 21:39 ` Bjorn Helgaas
2016-12-13 9:09 ` Jon Masters
2017-02-01 16:50 ` Bjorn Helgaas
2016-11-29 23:39 ` Linus Torvalds
2016-11-30 16:17 ` Bjorn Helgaas
2016-12-01 22:36 ` Bjorn Helgaas
2016-12-01 22:37 ` Rafael J. Wysocki
2016-12-01 23:27 ` Bjorn Helgaas
2016-12-02 0:28 ` Rafael J. Wysocki
2016-12-02 2:18 ` Bjorn Helgaas
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=20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com \
--to=bhelgaas@google.com \
--cc=ard.biesheuvel@linaro.org \
--cc=dhdang@apm.com \
--cc=gabriele.paoloni@huawei.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lv.zheng@intel.com \
--cc=rafael@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
all inboxes | Powered by JetHome®