From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.3 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 85A80C3A59E for ; Sat, 24 Aug 2019 22:36:56 +0000 (UTC) Received: from lists.ozlabs.org (lists.ozlabs.org [203.11.71.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id D6BA42133F for ; Sat, 24 Aug 2019 22:36:55 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org D6BA42133F Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=lst.de Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Received: from bilbo.ozlabs.org (lists.ozlabs.org [IPv6:2401:3900:2:1::3]) by lists.ozlabs.org (Postfix) with ESMTP id 46GCn13g9QzDrT0 for ; Sun, 25 Aug 2019 08:36:53 +1000 (AEST) Authentication-Results: lists.ozlabs.org; spf=none (mailfrom) smtp.mailfrom=lst.de (client-ip=213.95.11.211; helo=verein.lst.de; envelope-from=hch@lst.de; receiver=) Authentication-Results: lists.ozlabs.org; dmarc=none (p=none dis=none) header.from=lst.de Received: from verein.lst.de (verein.lst.de [213.95.11.211]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 46GCks1dRyzDrQh for ; Sun, 25 Aug 2019 08:34:58 +1000 (AEST) Received: by verein.lst.de (Postfix, from userid 2407) id 3E93268AEF; Sun, 25 Aug 2019 00:34:50 +0200 (CEST) Date: Sun, 25 Aug 2019 00:34:49 +0200 From: Christoph Hellwig To: Paul Burton Subject: Re: cleanup the dma_pgprot handling Message-ID: <20190824223449.GC21729@lst.de> References: <20190816070754.15653-1-hch@lst.de> <20190823215759.zprrwotlbva46y33@pburton-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190823215759.zprrwotlbva46y33@pburton-laptop> User-Agent: Mutt/1.5.17 (2007-11-01) X-BeenThere: linuxppc-dev@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Shawn Anastasio , Will Deacon , "linux-m68k@lists.linux-m68k.org" , Catalin Marinas , "linuxppc-dev@lists.ozlabs.org" , "linux-kernel@vger.kernel.org" , Russell King , "linux-mips@vger.kernel.org" , "iommu@lists.linux-foundation.org" , Geert Uytterhoeven , James Hogan , Guan Xuetao , Christoph Hellwig , "linux-arm-kernel@lists.infradead.org" , Robin Murphy Errors-To: linuxppc-dev-bounces+linuxppc-dev=archiver.kernel.org@lists.ozlabs.org Sender: "Linuxppc-dev" On Fri, Aug 23, 2019 at 09:58:04PM +0000, Paul Burton wrote: > So I believe uncached & uncached accelerated are another case like that > described above - they're 2 different CCAs but the same "access type", > namely uncached. > > Section 4.9 then goes on to forbid mixing access types, but not CCAs. > > It would be nice if the precise mapping from CCA to access type was > provided, but I don't see that anywhere. I can check with the > architecture team to be sure, but to my knowledge we're fine to mix > access via kseg1 (ie. uncached) & mappings with CCA=7 (uncached > accelerated). Ok. Looks like we can keep it then and I'll add a comment to the code with the above reference.