From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] ARM: dma_map|unmap_sg plus iommu
Date: Mon, 8 Aug 2011 16:29:52 +0100 [thread overview]
Message-ID: <20110808152952.GA19367@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAB-zwWj-VCWQ6h8wjv7owG7n7p59Ep4qXiQY3LruT64sikuSKg@mail.gmail.com>
On Mon, Aug 08, 2011 at 10:21:46AM -0500, Ramirez Luna, Omar wrote:
> Hi,
>
> On Sun, Jul 31, 2011 at 7:57 PM, KyongHo Cho <pullip.cho@samsung.com> wrote:
> > On Fri, Jul 29, 2011 at 11:24 PM, Marek Szyprowski
> ...
> >> Right now I have no idea how to handle this better. Perhaps with should be
> >> possible
> >> to specify somehow the target dma_address when doing memory allocation, but I'm
> >> not
> >> really convinced yet if this is really required.
> >>
> > What about using 'dma_handle' argument of alloc_coherent callback of
> > dma_map_ops?
> > Although it is an output argument, I think we can convey a hint or
> > start address to map
> > to the IO memory manager that resides behind dma API.
>
> I also thought on this one, even dma_map_single receives a void *ptr
> which could be casted into a struct with both physical and virtual
> addresses to be mapped, but IMHO, this starts to add twists into the
> dma map parameters which might create confusion.
No - don't even consider that. That's highly non-standard usage and
it'll break all existing drivers to do so.
next prev parent reply other threads:[~2011-08-08 15:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-28 21:09 [RFC] ARM: dma_map|unmap_sg plus iommu Ramirez Luna, Omar
2011-07-29 7:50 ` Marek Szyprowski
2011-07-29 9:35 ` 'Joerg Roedel'
2011-07-29 10:14 ` Marek Szyprowski
2011-07-29 10:54 ` 'Joerg Roedel'
2011-07-29 14:24 ` Marek Szyprowski
2011-08-01 0:57 ` KyongHo Cho
2011-08-08 15:21 ` Ramirez Luna, Omar
2011-08-08 15:29 ` Russell King - ARM Linux [this message]
2011-08-09 7:04 ` Marek Szyprowski
2011-08-08 15:04 ` Ramirez Luna, Omar
2011-08-09 6:51 ` Marek Szyprowski
2011-08-13 14:39 ` Ramirez Luna, Omar
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=20110808152952.GA19367@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).