Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423415AbbD2OsP (ORCPT ); Wed, 29 Apr 2015 10:48:15 -0400 Received: from mout.kundenserver.de ([212.227.126.130]:61819 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1031731AbbD2OsL (ORCPT ); Wed, 29 Apr 2015 10:48:11 -0400 From: Arnd Bergmann To: linaro-acpi@lists.linaro.org Cc: Suravee Suthikulpanit , linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com, rjw@rjwysocki.net, linux-kernel@vger.kernel.org, will.deacon@arm.com, linux-acpi@vger.kernel.org, lenb@kernel.org Subject: Re: [Linaro-acpi] [PATCH 2/2] ACPI / scan: Parse _CCA and setup device coherency Date: Wed, 29 Apr 2015 16:47:51 +0200 Message-ID: <3246744.xVj4sLRlWl@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <5540EE97.70202@amd.com> References: <1430315049-4663-1-git-send-email-Suravee.Suthikulpanit@amd.com> <5542288.z0SSOZ4xV7@wuerfel> <5540EE97.70202@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:Hpo0qGYVJzoGUbcVk0/BQNlM8Mrj5atPFriVv4tuC63ynnJNkEp ueJnlEcOxfPWCw6L6/Ys7RkYIHrpdum0IKPexhNVcqy7Jcm2ME06C5DDPjaormIyCz1pCvf pJ4kkch2GBHsEmiSTRX72heq6nhzl9vXbQu8o9xBcXUue6/obWcGO4RjI+/yholWgDbmfK2 vZ1fbMbEvy29ZvdTay1JA== X-UI-Out-Filterresults: notjunk:1; Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1977 Lines: 46 On Wednesday 29 April 2015 09:45:43 Suravee Suthikulpanit wrote: > On 04/29/2015 09:03 AM, Arnd Bergmann wrote: > > On Wednesday 29 April 2015 08:44:09 Suravee Suthikulpanit wrote: > >> + device->flags.cca_seen = 1; > >> + } else if (IS_ENABLED(CONFIG_ACPI_MUST_HAVE_CCA)) { > >> + /* > >> + * Architecture has specified that if the device > >> + * can do DMA, it must have ACPI _CCA object. > >> + * Here, there could be two cases: > >> + * 1. Not DMA-able device. > >> + * 2. DMA-able device, but missing _CCA object. > >> + * > >> + * In both cases, we will default to dma non-coherent. > >> + */ > >> + cca = 0; > >> + } else { > >> + /* > >> + * If architecture does not specify that device must > >> + * specify ACPI _CCA (e.g. x86), we default to use > >> + * dma coherent. > >> + */ > >> + cca = 1; > >> + } > >> > > > > What does it mean here if a device does DMA but is not coherent? Do you > > have an example of a server that needs this? > > > > Can we please make the default for ARM64 cca=1 as well? > > > > Arnd > > > > Actually, I am trying to implement the logic for when missing _CCA to be > consistent with the behavior when the devicetree entry does not specify > "dma-coherent" property. IIUC, in such case, Linux will default to using > non-coherent DMA. Why? Arnd -- 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/