From: Suravee.Suthikulpanit@amd.com (Suravee Suthikulpanit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] Honor ACPI _CCA attribute setting
Date: Fri, 14 Aug 2015 08:45:22 +0700 [thread overview]
Message-ID: <55CD4832.7070301@amd.com> (raw)
In-Reply-To: <1439416290-21228-2-git-send-email-jeremy.linton@arm.com>
Hi Jeremy,
On 8/13/15 04:51, Jeremy Linton wrote:
> ACPI configurations can now mark devices as noncoherent,
> support that choice.
>
> Signed-off-by: Jeremy Linton <jeremy.linton@arm.com>
> ---
> include/acpi/acpi_bus.h | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/include/acpi/acpi_bus.h b/include/acpi/acpi_bus.h
> index 83061ca..7ecb8e4 100644
> --- a/include/acpi/acpi_bus.h
> +++ b/include/acpi/acpi_bus.h
> @@ -399,7 +399,7 @@ static inline bool acpi_check_dma(struct acpi_device *adev, bool *coherent)
> * case 1. Do not support and disable DMA.
> * case 2. Support but rely on arch-specific cache maintenance for
> * non-coherence DMA operations.
> - * Currently, we implement case 1 above.
> + * Currently, we implement case 2 above.
> *
> * For the case when _CCA is missing (i.e. cca_seen=0) and
> * platform specifies ACPI_CCA_REQUIRED, we do not support DMA,
> @@ -407,7 +407,8 @@ static inline bool acpi_check_dma(struct acpi_device *adev, bool *coherent)
> *
> * See acpi_init_coherency() for more info.
> */
> - if (adev->flags.coherent_dma) {
> + if (adev->flags.coherent_dma ||
> + (adev->flags.cca_seen && IS_ENABLED(CONFIG_ARM64))) {
> ret = true;
> if (coherent)
> *coherent = adev->flags.coherent_dma;
>
This change was in my earlier revisions for the original patch series to
add ACPI CCA support. At the time, this was pushed back since we were
not sure whether this would be a useful case, and whether such hardware
exists.
Would it be useful to document somewhere (may be in the GIT commit
message) about which hardware might need this?
Arnd/Catalin, any feedback on this?
Thanks,
Suravee
next prev parent reply other threads:[~2015-08-14 1:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 21:51 [PATCH 0/3] Enable EHCI-platform driver for use with ACPI Jeremy Linton
2015-08-12 21:51 ` [PATCH 1/3] Honor ACPI _CCA attribute setting Jeremy Linton
2015-08-14 1:45 ` Suravee Suthikulpanit [this message]
2015-08-14 13:14 ` Catalin Marinas
2015-08-14 14:12 ` Jeremy Linton
2015-08-18 3:36 ` Huang Shijie
2015-08-12 21:51 ` [PATCH 2/3] Display a DMA error message Jeremy Linton
2015-08-13 11:02 ` Hanjun Guo
2015-08-13 14:52 ` Alan Stern
2015-08-14 21:19 ` Arnd Bergmann
2015-08-14 21:44 ` Jeremy Linton
2015-08-14 21:56 ` Arnd Bergmann
2015-08-12 21:51 ` [PATCH 3/3] Add ACPI bindings for the EHCI platform driver Jeremy Linton
2015-08-13 11:50 ` Hanjun Guo
2015-08-13 14:45 ` Jeremy Linton
2015-08-13 14:53 ` Alan Stern
2015-08-13 15:13 ` Jeremy Linton
2015-08-18 3:35 ` Huang Shijie
2015-08-13 9:44 ` [PATCH 0/3] Enable EHCI-platform driver for use with ACPI Graeme Gregory
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=55CD4832.7070301@amd.com \
--to=suravee.suthikulpanit@amd.com \
--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;
as well as URLs for NNTP newsgroup(s).