Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: rjw@rjwysocki.net (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] PCI: Add information about describing PCI in ACPI
Date: Thu, 01 Dec 2016 23:37:39 +0100	[thread overview]
Message-ID: <47776378.8X3TnsHd3Q@aspire.rjw.lan> (raw)
In-Reply-To: <20161201223604.GC15867@bhelgaas-glaptop.roam.corp.google.com>

On Thursday, December 01, 2016 04:36:04 PM Bjorn Helgaas wrote:
> 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!

Well, what's the drawback if it doesn't go into 4.9?

Thanks,
Rafael

  reply	other threads:[~2016-12-01 22:37 UTC|newest]

Thread overview: 11+ 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-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 [this message]
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=47776378.8X3TnsHd3Q@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=linux-arm-kernel@lists.infradead.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