From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: dma-mapping: move consistent_init to early_initcall
Date: Fri, 17 Dec 2010 10:56:57 +0000 [thread overview]
Message-ID: <20101217105657.GB9937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <99eb693af85e07b01d81d45f1bc77f64.squirrel@www.codeaurora.org>
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.
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.
next prev parent reply other threads:[~2010-12-17 10:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-02 22:11 [PATCH] arm: dma-mapping: move consistent_init to early_initcall Jeff Ohlstein
2010-12-02 22:19 ` Russell King - ARM Linux
2010-12-03 20:06 ` Saravana Kannan
2010-12-03 20:36 ` Russell King - ARM Linux
2010-12-03 22:45 ` Jamie Iles
2010-12-07 6:22 ` Saravana Kannan
2010-12-09 9:23 ` skannan at codeaurora.org
2010-12-09 10:38 ` Russell King - ARM Linux
2010-12-10 0:58 ` Saravana Kannan
2010-12-10 10:00 ` Catalin Marinas
2010-12-12 4:58 ` Saravana Kannan
2010-12-13 15:26 ` Catalin Marinas
2010-12-17 2:55 ` Saravana Kannan
2010-12-17 9:48 ` Russell King - ARM Linux
2010-12-17 10:26 ` Saravana Kannan
2010-12-17 10:56 ` Russell King - ARM Linux [this message]
2010-12-17 11:09 ` Saravana Kannan
2010-12-17 11:31 ` Catalin Marinas
2010-12-17 23:14 ` Saravana Kannan
2010-12-20 23:22 ` Saravana Kannan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20101217105657.GB9937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).