Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751973AbbEGTxm (ORCPT ); Thu, 7 May 2015 15:53:42 -0400 Received: from v094114.home.net.pl ([79.96.170.134]:60575 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751415AbbEGTxk (ORCPT ); Thu, 7 May 2015 15:53:40 -0400 From: "Rafael J. Wysocki" To: Arnd Bergmann Cc: linaro-acpi@lists.linaro.org, Suravee Suthikulanit , herbert@gondor.apana.org.au, catalin.marinas@arm.com, will.deacon@arm.com, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, linux-acpi@vger.kernel.org, netdev@vger.kernel.org, Mika Westerberg , davem@davemloft.net, linux-arm-kernel@lists.infradead.org, lenb@kernel.org Subject: Re: [Linaro-acpi] [V2 PATCH 1/5] ACPI / scan: Parse _CCA and setup device coherency Date: Thu, 07 May 2015 22:18:44 +0200 Message-ID: <4260574.bvpyYkBNGq@vostro.rjw.lan> User-Agent: KMail/4.11.5 (Linux/4.0.0+; KDE/4.11.5; x86_64; ; ) In-Reply-To: <2842267.oTDe4myPcU@wuerfel> References: <1430838729-21572-1-git-send-email-Suravee.Suthikulpanit@amd.com> <554A92C3.7060606@amd.com> <2842267.oTDe4myPcU@wuerfel> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1080 Lines: 31 On Thursday, May 07, 2015 11:07:08 AM Arnd Bergmann wrote: > On Wednesday 06 May 2015 17:16:35 Suravee Suthikulanit wrote: > > On 5/6/2015 5:21 PM, Rafael J. Wysocki wrote: > > >>>> > >>+ bool > > >>>> > >>+ > > >>>> > >>+config ACPI_SUPPORT_CCA_ZERO > > >>> > > > > >>> > >I guess this means "we support devices that can DMA, but are not coherent". > > >>> > >right? > > >> > > > >> >Yes, basically when _CCA=0. > > > So what about > > > > > > ARCH_SUPPORT_CACHE_INCOHERENT_DMA > > > > Since this is specific to ACPI _CCA, I just want to be clear with the > > naming. > > How about directly using the architecture names here, this is inherently > architecture specific, and it's more likely that if another architecture > gets added in the future that it will have other requirements. Sounds reasonable to me. Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/