Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S966298AbbD2ODf (ORCPT ); Wed, 29 Apr 2015 10:03:35 -0400 Received: from mout.kundenserver.de ([212.227.126.131]:58739 "EHLO mout.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S966189AbbD2ODd (ORCPT ); Wed, 29 Apr 2015 10:03:33 -0400 From: Arnd Bergmann To: linux-arm-kernel@lists.infradead.org Cc: Suravee Suthikulpanit , rjw@rjwysocki.net, lenb@kernel.org, catalin.marinas@arm.com, will.deacon@arm.com, al.stone@linaro.org, linaro-acpi@lists.linaro.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 Subject: Re: [PATCH 2/2] ACPI / scan: Parse _CCA and setup device coherency Date: Wed, 29 Apr 2015 16:03:19 +0200 Message-ID: <5542288.z0SSOZ4xV7@wuerfel> User-Agent: KMail/4.11.5 (Linux/3.16.0-10-generic; KDE/4.11.5; x86_64; ; ) In-Reply-To: <1430315049-4663-3-git-send-email-Suravee.Suthikulpanit@amd.com> References: <1430315049-4663-1-git-send-email-Suravee.Suthikulpanit@amd.com> <1430315049-4663-3-git-send-email-Suravee.Suthikulpanit@amd.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Provags-ID: V03:K0:ATHrJxzds1jyuIiRY2/NTV15/joisuAS5iyrzd34I8Vy6jyIXuv wiJYTfckJ4D8arl4tbdUaS5Y17UKywd98bG99NPn5UkzSbXuyANlHZoDsO4RG8hMmeWvOko luwijoUaYeWem2ojKHJ8byBNkkN2AkLzGew6VAm83SfOueLPoZyjUlp+RIHtcv2WfIvqvM+ bU2+e7Z5mpW119SQ6CHsQ== 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: 1502 Lines: 34 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 -- 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/