From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [regression] in linux-next: sh_mobile_ceu_camera broken by "ARM: Prohibit ioremap() on kernel managed RAM"
Date: Wed, 18 Aug 2010 22:44:40 +0100 [thread overview]
Message-ID: <20100818214440.GA22254@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.1008182218150.17895@axis700.grange>
On Wed, Aug 18, 2010 at 10:31:10PM +0200, Guennadi Liakhovetski wrote:
> On Wed, 18 Aug 2010, Russell King - ARM Linux wrote:
> > Sounds like a sane approach to fixing this to me.
>
> I assume, you mean adding a new flag to skip ioremap(). But then we have
> to pass the virtual address to the function. Its prototype is
>
> int dma_declare_coherent_memory(struct device *dev, dma_addr_t bus_addr,
> dma_addr_t device_addr, size_t size, int flags);
>
> bus_addr is unused in this case, but I don't think abusing it to pass a
> "void *" would be an acceptable solution - apart from all the ugly
> type-casting, if we ever get 64-bit virtual addresses on ARM with 32-bit
> DMA addresses, we've got a problem. Or is this never going to happen? Or
> whould I rather add a new function?
A new function sounds saner.
next prev parent reply other threads:[~2010-08-18 21:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-08 15:45 [regression] in linux-next: sh_mobile_ceu_camera broken by "ARM: Prohibit ioremap() on kernel managed RAM" Arnd Hannemann
2010-08-08 22:00 ` Russell King - ARM Linux
2010-08-10 14:07 ` Stuart Menefy
2010-08-10 16:36 ` Russell King - ARM Linux
2010-08-10 8:45 ` Philippe Rétornaz
2010-08-10 9:27 ` Russell King - ARM Linux
2010-08-10 19:55 ` Guennadi Liakhovetski
2010-08-10 21:26 ` Russell King - ARM Linux
2010-08-13 10:52 ` hisao munakata
2010-08-18 19:23 ` Guennadi Liakhovetski
2010-08-18 19:41 ` Russell King - ARM Linux
2010-08-18 20:31 ` Guennadi Liakhovetski
2010-08-18 21:44 ` Russell King - ARM Linux [this message]
2010-08-18 21:47 ` Russell King - ARM Linux
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=20100818214440.GA22254@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).