From: Bjorn Helgaas <helgaas@kernel.org>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Duc Dang <dhdang@apm.com>,
linux-kernel@vger.kernel.org, linaro-acpi@lists.linaro.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: Re: [PATCH v2] PCI: Add information about describing PCI in ACPI
Date: Thu, 1 Dec 2016 16:36:04 -0600 [thread overview]
Message-ID: <20161201223604.GC15867@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Tue, Nov 29, 2016 at 03:39:48PM -0600, Bjorn Helgaas wrote:
> 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
It's very late in the cycle, but I'm considering trying to squeeze
this into v4.9 on the grounds that:
- It's only a documentation change and can't break anything, and
- Distributing it more widely may help the arm64 firmware ecosystem
But I don't want to disseminate misleading or incorrect information,
so if it needs clarification or wordsmithing, or even just maturation,
I'll wait until v4.10.
The Consumer/Producer stuff, in particular, doesn't seem 100% settled
yet. Your thoughts, and especially your improvements, are welcome!
Bjorn
WARNING: multiple messages have this Message-ID (diff)
From: helgaas@kernel.org (Bjorn Helgaas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] PCI: Add information about describing PCI in ACPI
Date: Thu, 1 Dec 2016 16:36:04 -0600 [thread overview]
Message-ID: <20161201223604.GC15867@bhelgaas-glaptop.roam.corp.google.com> (raw)
In-Reply-To: <20161129212816.15663.28100.stgit@bhelgaas-glaptop.roam.corp.google.com>
On Tue, Nov 29, 2016 at 03:39:48PM -0600, Bjorn Helgaas wrote:
> 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
It's very late in the cycle, but I'm considering trying to squeeze
this into v4.9 on the grounds that:
- It's only a documentation change and can't break anything, and
- Distributing it more widely may help the arm64 firmware ecosystem
But I don't want to disseminate misleading or incorrect information,
so if it needs clarification or wordsmithing, or even just maturation,
I'll wait until v4.10.
The Consumer/Producer stuff, in particular, doesn't seem 100% settled
yet. Your thoughts, and especially your improvements, are welcome!
Bjorn
next prev parent reply other threads:[~2016-12-01 22:36 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 21:39 [PATCH v2] PCI: Add information about describing PCI in ACPI Bjorn Helgaas
2016-11-29 21:39 ` Bjorn Helgaas
2016-11-29 21:39 ` Bjorn Helgaas
2016-11-29 21:39 ` Bjorn Helgaas
2016-11-29 21:39 ` Bjorn Helgaas
2016-11-29 21:39 ` Bjorn Helgaas
2016-12-13 9:09 ` Jon Masters
2016-12-13 9:09 ` Jon Masters
2016-12-13 9:09 ` Jon Masters
2017-02-01 16:50 ` Bjorn Helgaas
2017-02-01 16:50 ` Bjorn Helgaas
2017-02-01 16:50 ` Bjorn Helgaas
2016-11-29 23:39 ` Linus Torvalds
2016-11-29 23:39 ` Linus Torvalds
2016-11-29 23:39 ` Linus Torvalds
2016-11-30 16:17 ` Bjorn Helgaas
2016-11-30 16:17 ` Bjorn Helgaas
2016-11-30 16:17 ` Bjorn Helgaas
2016-11-30 16:17 ` Bjorn Helgaas
2016-12-01 22:36 ` Bjorn Helgaas [this message]
2016-12-01 22:36 ` Bjorn Helgaas
2016-12-01 22:37 ` Rafael J. Wysocki
2016-12-01 22:37 ` Rafael J. Wysocki
2016-12-01 23:27 ` Bjorn Helgaas
2016-12-01 23:27 ` Bjorn Helgaas
2016-12-01 23:27 ` Bjorn Helgaas
2016-12-02 0:28 ` Rafael J. Wysocki
2016-12-02 0:28 ` Rafael J. Wysocki
2016-12-02 0:28 ` Rafael J. Wysocki
2016-12-02 2:18 ` Bjorn Helgaas
2016-12-02 2:18 ` Bjorn Helgaas
2016-12-02 2:18 ` Bjorn Helgaas
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=20161201223604.GC15867@bhelgaas-glaptop.roam.corp.google.com \
--to=helgaas@kernel.org \
--cc=ard.biesheuvel@linaro.org \
--cc=bhelgaas@google.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.