public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Suravee Suthikulanit <suravee.suthikulpanit@amd•com>
To: Catalin Marinas <catalin.marinas@arm•com>
Cc: <rjw@rjwysocki•net>, <lenb@kernel•org>, <will.deacon@arm•com>,
	<bhelgaas@google•com>, <thomas.lendacky@amd•com>,
	<herbert@gondor•apana.org.au>, <davem@davemloft•net>,
	<arnd@arndb•de>, <al.stone@linaro•org>,
	<linaro-acpi@lists•linaro.org>, <netdev@vger•kernel.org>,
	<linux-kernel@vger•kernel.org>, <linux-acpi@vger•kernel.org>,
	<leo.duran@amd•com>, <hanjun.guo@linaro•org>,
	<msalter@redhat•com>, <grant.likely@linaro•org>,
	<linux-arm-kernel@lists•infradead.org>,
	<linux-crypto@vger•kernel.org>
Subject: Re: [V4 PATCH 2/6] arm64 : Introduce support for ACPI _CCA object
Date: Wed, 20 May 2015 06:51:34 -0500	[thread overview]
Message-ID: <555C7546.4040601@amd.com> (raw)
In-Reply-To: <20150520100304.GE25313@e104818-lin.cambridge.arm.com>

On 5/20/2015 5:03 AM, Catalin Marinas wrote:
> On Fri, May 15, 2015 at 04:23:10PM -0500, Suravee Suthikulpanit wrote:
>>  From http://www.uefi.org/sites/default/files/resources/ACPI_6.0.pdf,
>> section 6.2.17 _CCA states that ARM platforms require ACPI _CCA
>> object to be specified for DMA-cabpable devices. This patch introduces
>> ACPI_MUST_HAVE_CCA in arm64 Kconfig to specify such requirement.
>>
>> In case _CCA is missing, arm64 would assign dummy_dma_ops
>> to disable DMA capability of the device.
>>
>> Signed-off-by: Mark Salter <msalter@redhat•com>
>> Signed-off-by: Suravee Suthikulpanit <Suravee.Suthikulpanit@amd•com>
>> CC: Catalin Marinas <catalin.marinas@arm•com>
>> CC: Will Deacon <will.deacon@arm•com>
>> CC: Arnd Bergmann <arnd@arndb•de>
>
> Acked-by: Catalin Marinas <catalin.marinas@arm•com>
>

Thanks,

Suravee


  reply	other threads:[~2015-05-20 11:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-15 21:23 [V4 PATCH 0/6] ACPI: Introduce support for _CCA object Suravee Suthikulpanit
2015-05-15 21:23 ` [V4 PATCH 1/6] ACPI / scan: Parse _CCA and setup device coherency Suravee Suthikulpanit
2015-05-15 23:53   ` Rafael J. Wysocki
2015-05-18 22:38     ` Suravee Suthikulanit
2015-05-19  0:28       ` Rafael J. Wysocki
2015-05-20 10:01   ` Catalin Marinas
2015-05-20 11:52     ` Suravee Suthikulanit
2015-05-20 12:04       ` [Linaro-acpi] " Arnd Bergmann
2015-05-21 13:01         ` Catalin Marinas
2015-05-21 13:24           ` Arnd Bergmann
2015-05-15 21:23 ` [V4 PATCH 2/6] arm64 : Introduce support for ACPI _CCA object Suravee Suthikulpanit
2015-05-16 11:48   ` Paul Bolle
2015-05-16 16:50     ` Suravee Suthikulpanit
2015-05-20 10:03   ` Catalin Marinas
2015-05-20 11:51     ` Suravee Suthikulanit [this message]
2015-05-15 21:23 ` [V4 PATCH 3/6] pci: Generic function for setting up PCI device DMA coherency Suravee Suthikulpanit
2015-05-15 23:59   ` Rafael J. Wysocki
2015-05-16 15:12     ` Suthikulpanit, Suravee
2015-05-20  9:24     ` Catalin Marinas
2015-05-20  9:27       ` Arnd Bergmann
2015-05-20  9:34         ` Catalin Marinas
2015-05-20 12:00           ` Suravee Suthikulanit
2015-05-20 12:02             ` [Linaro-acpi] " Arnd Bergmann
2015-05-20 20:46             ` Russell King - ARM Linux
2015-05-20  9:31       ` Catalin Marinas
2015-05-16 12:41   ` Bjorn Helgaas
2015-05-16 15:14     ` Suthikulpanit, Suravee
2015-05-15 21:23 ` [V4 PATCH 4/6] device property: Introduces device_dma_is_coherent() Suravee Suthikulpanit
2015-05-20 10:28   ` Will Deacon
2015-05-20 21:32     ` Suravee Suthikulanit
2015-05-15 21:23 ` [V4 PATCH 5/6] crypto: ccp - Unify coherency checking logic with device_dma_is_coherent() Suravee Suthikulpanit
2015-05-15 21:23 ` [V4 PATCH 6/6] amd-xgbe: " 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=555C7546.4040601@amd.com \
    --to=suravee.suthikulpanit@amd$(echo .)com \
    --cc=al.stone@linaro$(echo .)org \
    --cc=arnd@arndb$(echo .)de \
    --cc=bhelgaas@google$(echo .)com \
    --cc=catalin.marinas@arm$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=grant.likely@linaro$(echo .)org \
    --cc=hanjun.guo@linaro$(echo .)org \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=lenb@kernel$(echo .)org \
    --cc=leo.duran@amd$(echo .)com \
    --cc=linaro-acpi@lists$(echo .)linaro.org \
    --cc=linux-acpi@vger$(echo .)kernel.org \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    --cc=linux-crypto@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=msalter@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rjw@rjwysocki$(echo .)net \
    --cc=thomas.lendacky@amd$(echo .)com \
    --cc=will.deacon@arm$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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