qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Graeme Gregory <graeme.gregory@linaro.org>
To: qemu-devel@nongnu.org
Cc: Graeme Gregory <graeme.gregory@linaro.org>,
	shannon.zhao@linaro.org, tomasz.nowicki@linaro.org
Subject: [Qemu-devel] [PATCH] hw/arm/virt-acpi-build: _CCA attribute is compulsary
Date: Mon,  2 Nov 2015 10:39:46 +0000	[thread overview]
Message-ID: <1446460786-13663-1-git-send-email-graeme.gregory@linaro.org> (raw)

According to ACPI specification 6.2.17 _CCA (Cache Coherency Attribute)
this attribute is compulsary on ARM systems. Add this attribute to
the PCI host bridges as required.

Without this the kernel will produce the error
[Firmware Bug]: PCI device 0000:00:00.0 fail to setup DMA.

Signed-off-by: Graeme Gregory <graeme.gregory@linaro.org>
---
 hw/arm/virt-acpi-build.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/hw/arm/virt-acpi-build.c b/hw/arm/virt-acpi-build.c
index 1aaff1f..1430125 100644
--- a/hw/arm/virt-acpi-build.c
+++ b/hw/arm/virt-acpi-build.c
@@ -180,6 +180,7 @@ static void acpi_dsdt_add_pci(Aml *scope, const MemMapEntry *memmap, int irq,
     aml_append(dev, aml_name_decl("_ADR", aml_int(0)));
     aml_append(dev, aml_name_decl("_UID", aml_string("PCI0")));
     aml_append(dev, aml_name_decl("_STR", aml_unicode("PCIe 0 Device")));
+    aml_append(dev, aml_name_decl("_CCA", aml_int(1)));
 
     /* Declare the PCI Routing Table. */
     Aml *rt_pkg = aml_package(nr_pcie_buses * PCI_NUM_PINS);
-- 
2.4.3

             reply	other threads:[~2015-11-02 10:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-02 10:39 Graeme Gregory [this message]
2015-11-03  2:25 ` [Qemu-devel] [PATCH] hw/arm/virt-acpi-build: _CCA attribute is compulsary Shannon Zhao
2015-11-03  8:31   ` Graeme Gregory
2015-11-03  9:08     ` Shannon Zhao
2015-11-03 13:26       ` Peter Maydell

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=1446460786-13663-1-git-send-email-graeme.gregory@linaro.org \
    --to=graeme.gregory@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=shannon.zhao@linaro.org \
    --cc=tomasz.nowicki@linaro.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).