Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753160Ab0LQLJd (ORCPT ); Fri, 17 Dec 2010 06:09:33 -0500 Received: from wolverine02.qualcomm.com ([199.106.114.251]:33348 "EHLO wolverine02.qualcomm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751153Ab0LQLJc (ORCPT ); Fri, 17 Dec 2010 06:09:32 -0500 X-IronPort-AV: E=McAfee;i="5400,1158,6199"; a="67011620" Message-ID: <6149a450170fa5fe32b271d2db0ec81b.squirrel@www.codeaurora.org> In-Reply-To: <20101217105657.GB9937@n2100.arm.linux.org.uk> References: <4CFDD297.4020600@codeaurora.org> <15d23d63900e4545a40555961c49c421.squirrel@codeaurora.org> <20101209103835.GA31465@n2100.arm.linux.org.uk> <4D017B45.4000805@codeaurora.org> <4D045692.4050607@codeaurora.org> <8c67e174d807416f0c6c190cc72d3f5a.squirrel@www.codeaurora.org> <20101217094818.GA9937@n2100.arm.linux.org.uk> <99eb693af85e07b01d81d45f1bc77f64.squirrel@www.codeaurora.org> <20101217105657.GB9937@n2100.arm.linux.org.uk> Date: Fri, 17 Dec 2010 03:09:18 -0800 (PST) Subject: Re: [PATCH] arm: dma-mapping: move consistent_init to early_initcall From: "Saravana Kannan" To: "Russell King - ARM Linux" Cc: "Saravana Kannan" , "Catalin Marinas" , dwalker@codeaurora.org, linux-arm-msm@vger.kernel.org, "Nicolas Pitre" , linux-kernel@vger.kernel.org, "Jeff Ohlstein" , "Tejun Heo" , linux-arm-kernel@lists.infradead.org User-Agent: SquirrelMail/1.4.17 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT X-Priority: 3 (Normal) Importance: Normal Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1395 Lines: 36 > On Fri, Dec 17, 2010 at 02:26:44AM -0800, Saravana Kannan wrote: >> After Catalin's response to clarify, if we still end up not treating >> secure domain as a "DMA device", then what's the alternative? Can we get >> an explicit "cache invalidate API" that's outside of the DMA APIs? Or a >> general uncached pages alloc/free APIs? > > The answer _always_ is that if the existing APIs don't give you want > you need, then either the APIs need extending or a new API needs to > be created. I will wait to hear Catalin's clarification before I proceed further with this point. > > In any case, have you looked at the latest set of SCM patches? They > don't make use of DMA coherent memory anymore, so the problem would > seem to be resolved. > Yes, I saw them and even pointed out a few issues during internal-prelim review. The new patches get around it with what we hope is a temporary solution -- implement cache invalidate in assembly and call it over a kmalloc'ed and page aligned memory. -Saravana -- Sent by an employee of the Qualcomm Innovation Center, Inc. The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum. -- 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/