From: lauraa@codeaurora.org (Laura Abbott)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFc] Map CMA pages as cached
Date: Fri, 13 Jul 2012 11:01:45 -0700 [thread overview]
Message-ID: <1342202506-12449-1-git-send-email-lauraa@codeaurora.org> (raw)
Current APIs only support allocating CMA pages as either coherent or
writecombine. This seems to miss support for cached pages completely.
The following patch seems to be the first obvious solution.
More generally though, what should be the strategy for remapping with
other memory types? Add a new function call each time?
Thanks,
Laura
next reply other threads:[~2012-07-13 18:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 18:01 Laura Abbott [this message]
2012-07-13 18:01 ` [PATCH][RFC] arm: dma-mapping: Add support for allocating/mapping cached buffers Laura Abbott
2012-07-14 13:53 ` [Linaro-mm-sig] " Clark, Rob
2012-07-17 1:06 ` Laura Abbott
2012-07-17 5:58 ` Marek Szyprowski
2012-07-20 20:30 ` Laura Abbott
2012-07-23 7:22 ` Marek Szyprowski
2012-07-23 8:46 ` Arnd Bergmann
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=1342202506-12449-1-git-send-email-lauraa@codeaurora.org \
--to=lauraa@codeaurora.org \
--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).