From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Al Stone <ahs@redhat.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Arnd Bergmann <arnd@arndb.de>,
Christopher Covington <cov@codeaurora.org>,
Don Dutile <ddutile@redhat.com>,
Dongdong Liu <liudongdong3@huawei.com>, Duc Dang <dhdang@apm.com>,
Gabriele Paoloni <gabriele.paoloni@huawei.com>,
Graeme Gregory <graeme.gregory@linaro.org>,
Jon Masters <jcm@redhat.com>, Mark Salter <msalter@redhat.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Robert Richter <rrichter@cavium.com>,
Sinan Kaya <okaya@codeaurora.org>,
Tomasz Nowicki <tn@semihalf.com>,
linux-arm-kernel@lists.infradead.org,
linaro-acpi@lists.linaro.org
Subject: Re: ACPI namespace details for ARM64
Date: Fri, 11 Nov 2016 11:28:29 +0000 [thread overview]
Message-ID: <20161111112829.GB13333@red-moon> (raw)
In-Reply-To: <20161109220506.GN14322@bhelgaas-glaptop.roam.corp.google.com>
On Wed, Nov 09, 2016 at 04:05:06PM -0600, Bjorn Helgaas wrote:
[...]
> ACPI defined a Producer/Consumer bit that was intended to distinguish
> the bridge apertures from the bridge registers [4, 5]. However, BIOSes
> didn't use that bit correctly, and the result is that OSes have to
> assume that everything in a PCI host bridge _CRS is a window. That
> leaves no way to describe the bridge registers in the PNP0A03/PNP0A08
> device itself.
ACPI 6.1 states that in the revision changes 4.0a Apr.2010 (xiii)
"Consumer/Producer bit is ignored (Restored 2.0C change that had
been lost)" and still that bit is marked as valid. If it is not
reliable it should be set as "ignored" in the specs (as it was
on ACPI 2.0C, BTW), as it is it is just a source of confusion.
Thanks again !
Lorenzo
next prev parent reply other threads:[~2016-11-11 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 22:05 ACPI namespace details for ARM64 Bjorn Helgaas
2016-11-10 23:18 ` [Linaro-acpi] " Al Stone
2016-11-11 3:33 ` Don Dutile
2016-11-11 9:32 ` Lorenzo Pieralisi
2016-11-11 14:44 ` Hanjun Guo
2016-11-11 14:24 ` Sinan Kaya
2016-12-02 5:13 ` Jon Masters
2016-11-11 11:28 ` Lorenzo Pieralisi [this message]
2016-12-02 4:52 ` Jon Masters
2016-12-02 16:21 ` 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=20161111112829.GB13333@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=ahs@redhat.com \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=cov@codeaurora.org \
--cc=ddutile@redhat.com \
--cc=dhdang@apm.com \
--cc=gabriele.paoloni@huawei.com \
--cc=graeme.gregory@linaro.org \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--cc=linaro-acpi@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=msalter@redhat.com \
--cc=okaya@codeaurora.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rrichter@cavium.com \
--cc=tn@semihalf.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).