From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: dma-mapping: support for DMA_ATTR_NON_CONSISTENT DMA attribute
Date: Mon, 29 Jun 2015 11:08:04 +0100 [thread overview]
Message-ID: <20150629100804.GA7557@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAF6-1L584tp5o8U7S-w4-_XSjH4uXdMJSY89grLyFuwrJF3UyA@mail.gmail.com>
On Mon, Jun 29, 2015 at 12:05:09PM +0200, Sylvain Munaut wrote:
> Well that can't be since the dma_sync_* are part of streaming API and
> the dma_alloc_attrs is part of the "coherent" API (even though you
> have the NON_COHERENT flag in it ... that's a bit weird).
>
> But I don't see the alternative, unless the doc is suggesting I
> basically do all the cache invalidation myself manually and doing arch
> specific stuff directly in the driver ?
Maybe someone with this problem should work on a solution - augmenting
the coherent API with a set of functions to do what you want?
Please, if you find something lacking like this, make a proposal and
send a patch - but bear in mind that such an extension is not a matter
for just ARM, but every other architecture that the kernel supports,
so merely sending it to ARM mailing lists isn't going to get you very
far.
--
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2015-06-29 10:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-28 20:32 dma-mapping: support for DMA_ATTR_NON_CONSISTENT DMA attribute Sylvain Munaut
2015-06-28 22:45 ` Russell King - ARM Linux
2015-06-29 5:24 ` Sylvain Munaut
2015-06-29 6:44 ` Mike Looijmans
2015-06-29 9:45 ` Russell King - ARM Linux
2015-06-29 13:08 ` Mike Looijmans
2015-06-29 10:05 ` Sylvain Munaut
2015-06-29 10:08 ` Russell King - ARM Linux [this message]
2015-06-29 13:22 ` Sylvain Munaut
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=20150629100804.GA7557@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).