From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Ian Campbell <Ian.Campbell@eu.citrix.com>
Cc: Becky Bruce <beckyb@kernel.crashing.org>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 2/3] powerpc: Add support for swiotlb on 32-bit
Date: Fri, 22 May 2009 16:55:30 -0700 [thread overview]
Message-ID: <4A173B72.5000201@goop.org> (raw)
In-Reply-To: <1242990702.22654.253.camel@zakaz.uk.xensource.com>
Ian Campbell wrote:
> On Thu, 2009-05-21 at 14:27 -0400, Becky Bruce wrote:
>
>> I can work with that, but it's going to be a bit inefficient, as I
>> actually need the dma_addr_t, not the phys_addr_t, so I'll have to
>> convert. In every case, this is a conversion I've already done and
>> that I need in the calling code as well.
>>
>
> Does
>
> dma_addr_t dma_map_range(struct device *hwdev, phys_addr_t addr,
> size_t size);
>
> work for you?
>
> If the range does not need mapping then it returns the dma address, if
> you needed to calculate the dma address anyway to figure out if mapping
> is required then this is fine. If the range does need mapping then it
> returns NULL.
>
My only concern is whether dma_addr_t == 0 is actually equivalent to
NULL. That is, can we be sure that address 0 will never be used?
Taking dma_alloc_coherent as a model, we could have something like:
int dma_map_range(struct device *hwdev, phys_addr_t addr, size_t size, dma_addr_t *dma_addrp);
where *dma_addrp is set if the function returns success (bool return
type might be clearer).
J
next prev parent reply other threads:[~2009-05-22 23:55 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1242340949-16369-1-git-send-email-beckyb@kernel.crashing.org>
[not found] ` <1242340949-16369-2-git-send-email-beckyb@kernel.crashing.org>
2009-05-19 5:27 ` [PATCH V2 2/3] powerpc: Add support for swiotlb on 32-bit FUJITA Tomonori
2009-05-19 20:57 ` Becky Bruce
2009-05-21 17:43 ` Jeremy Fitzhardinge
2009-05-21 18:27 ` Becky Bruce
2009-05-21 19:01 ` Ian Campbell
2009-05-22 10:51 ` FUJITA Tomonori
2009-05-21 20:18 ` Jeremy Fitzhardinge
2009-05-21 22:08 ` Ian Campbell
2009-05-22 10:51 ` FUJITA Tomonori
2009-05-27 19:05 ` Becky Bruce
2009-05-22 11:11 ` Ian Campbell
2009-05-22 23:55 ` Jeremy Fitzhardinge [this message]
2009-05-23 22:59 ` Leon Woestenberg
2009-05-26 12:51 ` Ian Campbell
2009-05-27 19:11 ` Becky Bruce
2009-05-27 19:05 ` Becky Bruce
2009-05-27 20:29 ` Ian Campbell
2009-05-27 22:11 ` Becky Bruce
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=4A173B72.5000201@goop.org \
--to=jeremy@goop.org \
--cc=Ian.Campbell@eu.citrix.com \
--cc=beckyb@kernel.crashing.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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