[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2842267.oTDe4myPcU@wuerfel>
Date: Thu, 07 May 2015 11:07:08 +0200
From: Arnd Bergmann <arnd@...db.de>
To: linaro-acpi@...ts.linaro.org
Cc: Suravee Suthikulanit <suravee.suthikulpanit@....com>,
"Rafael J. Wysocki" <rjw@...ysocki.net>,
herbert@...dor.apana.org.au, catalin.marinas@....com,
will.deacon@....com, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org, linux-acpi@...r.kernel.org,
netdev@...r.kernel.org,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
davem@...emloft.net, linux-arm-kernel@...ts.infradead.org,
lenb@...nel.org
Subject: Re: [Linaro-acpi] [V2 PATCH 1/5] ACPI / scan: Parse _CCA and setup device coherency
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.
Arnd
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists