From: Guillermo Marcus <marcus@ti.uni-mannheim.de>
To: rmk+lkml@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmaping a kernel buffer to user space
Date: Thu, 02 Nov 2006 12:31:46 +0100 [thread overview]
Message-ID: <4549D722.5090007@ti.uni-mannheim.de> (raw)
In-Reply-To: <20061102083109.GB1377@flint.arm.linux.org.uk>
Russell King wrote:
> On Wed, Nov 01, 2006 at 01:58:17PM +0100, Guillermo Marcus Martinez wrote:
>> My suggestion would be to add two functions: pci_map_consistent() and
>> dma_map_coherent() to address this issue, and their corresponding
>> unmap's. That will make sure all that is needed is done, is a clean and
>> consistent with the pci_ and dma_ APIs, and fills a mmap requirement not
>> covered by the other functions.
>
> You might want to look through include/asm-arm/dma-mapping.h to see if
> an architecture already has considered that and the interface they
> implemented.
>
Nice! Thanks. I think the issue of mapping a coherent area to user space
is fairly general. Should not this be promoted to be part of the general
dma-api? (that is, not a platform specific function)
prev parent reply other threads:[~2006-11-02 11:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 9:19 mmaping a kernel buffer to user space Guillermo Marcus
2006-10-31 16:00 ` Jiri Slaby
2006-10-31 16:25 ` Guillermo Marcus
2006-10-31 16:49 ` Jiri Slaby
2006-10-31 17:08 ` Franck Bui-Huu
2006-10-31 19:44 ` Miguel Ojeda
2006-10-31 19:22 ` Russell King
2006-10-31 19:36 ` Jiri Slaby
2006-10-31 16:10 ` Rolf Offermanns
2006-10-31 16:33 ` Guillermo Marcus
2006-11-01 11:11 ` Rolf Offermanns
2006-11-01 12:58 ` Guillermo Marcus Martinez
2006-11-01 14:00 ` yogeshwar sonawane
2006-11-01 15:06 ` Guillermo Marcus Martinez
2006-11-02 8:31 ` Russell King
2006-11-02 11:31 ` Guillermo Marcus [this message]
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=4549D722.5090007@ti.uni-mannheim.de \
--to=marcus@ti.uni-mannheim.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
/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