From: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
To: <bhelgaas@google.com>, <rjw@rjwysocki.net>, <lenb@kernel.org>,
<catalin.marinas@arm.com>, <will.deacon@arm.com>
Cc: <hanjun.guo@linaro.org>, <linux-acpi@vger.kernel.org>,
<linux-pci@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
Suravee Suthikulpanit <Suravee.Suthikulpanit@amd.com>
Subject: [PATCH V2 0/4] PCI: ACPI: Setting up DMA coherency for PCI device from _CCA attribute
Date: Wed, 26 Aug 2015 00:33:25 +0700 [thread overview]
Message-ID: <1440524009-5359-1-git-send-email-Suravee.Suthikulpanit@amd.com> (raw)
This patch adds support to setup DMA coherency for PCI device using
the ACPI _CCA attribute. According to the ACPI spec, the _CCA attribute
is required for ARM64. Therefore, this patch is a pre-req for ACPI PCI
support for ARM64 which is currently in development.
Also, this should not affect other architectures that does not define
CONFIG_ACPI_CCA_REQUIRED, since the default value is coherent.
In the V2 of this patch series, I have pulled in the following patch from Jeremy
before cleaning up the acpi_check_dma() function (in patch 2).
http://www.spinics.net/lists/linux-usb/msg128582.html)
Changes from V1: (https://lkml.org/lkml/2015/8/13/182)
* Include patch 1 from Jeremy to enable support for _CCA=0
* Clean up acpi_check_dma() per Bjorn suggestions
* Split the original V1 patch into two patches (patch 3 and 4)
Jeremy Linton (1):
Honor ACPI _CCA attribute setting
Suravee Suthikulpanit (3):
ACPI/scan: Clean up acpi_check_dma
PCI: OF: Move of_pci_dma_configure() to pci_dma_configure()
PCI: ACPI: Add support for PCI device DMA coherency
drivers/acpi/acpi_platform.c | 7 ++++++-
drivers/acpi/glue.c | 5 +++--
drivers/acpi/scan.c | 39 +++++++++++++++++++++++++++++++++++++++
drivers/base/property.c | 8 ++++++--
drivers/of/of_pci.c | 20 --------------------
drivers/pci/probe.c | 32 ++++++++++++++++++++++++++++++--
include/acpi/acpi_bus.h | 35 ++---------------------------------
include/linux/acpi.h | 4 ++--
include/linux/of_pci.h | 3 ---
9 files changed, 88 insertions(+), 65 deletions(-)
--
2.1.0
next reply other threads:[~2015-08-25 17:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 17:33 Suravee Suthikulpanit [this message]
2015-08-25 17:33 ` [PATCH V2 1/4] Honor ACPI _CCA attribute setting Suravee Suthikulpanit
2015-08-25 17:33 ` [PATCH V2 2/4] ACPI/scan: Clean up acpi_check_dma Suravee Suthikulpanit
2015-08-25 23:48 ` Rafael J. Wysocki
2015-08-26 2:00 ` Suravee Suthikulpanit
2015-08-26 2:44 ` Rafael J. Wysocki
2015-08-25 17:33 ` [PATCH V2 3/4] PCI: OF: Move of_pci_dma_configure() to pci_dma_configure() Suravee Suthikulpanit
2015-08-25 19:27 ` Rob Herring
2015-08-25 17:33 ` [PATCH V2 4/4] PCI: ACPI: Add support for PCI device DMA coherency Suravee Suthikulpanit
2015-08-25 23:48 ` Rafael J. Wysocki
2015-08-26 2:01 ` Suravee Suthikulpanit
2015-08-25 18:48 ` [PATCH V2 0/4] PCI: ACPI: Setting up DMA coherency for PCI device from _CCA attribute Arnd Bergmann
2015-08-26 2:36 ` Suravee Suthikulpanit
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=1440524009-5359-1-git-send-email-Suravee.Suthikulpanit@amd.com \
--to=suravee.suthikulpanit@amd.com \
--cc=bhelgaas@google.com \
--cc=catalin.marinas@arm.com \
--cc=hanjun.guo@linaro.org \
--cc=lenb@kernel.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=rjw@rjwysocki.net \
--cc=will.deacon@arm.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).