From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Eduardo Valentin <edubezval@gmail.com>, linux-omap@vger.kernel.org
Subject: Re: FOR COMMENT: void __iomem * and similar casts are Bad News
Date: Wed, 3 Sep 2008 13:50:06 -0700 [thread overview]
Message-ID: <20080903205004.GW23085@atomide.com> (raw)
In-Reply-To: <20080903204524.GI19980@flint.arm.linux.org.uk>
* Russell King - ARM Linux <linux@arm.linux.org.uk> [080903 13:46]:
> On Wed, Sep 03, 2008 at 04:04:11PM -0400, Eduardo Valentin wrote:
> > Hi Russell,
> >
> > On Wed, Sep 3, 2008 at 3:48 PM, Russell King - ARM Linux
> > <linux@arm.linux.org.uk> wrote:
> > > Yes, that will be virtual. But what does it mean to call:
> > >
> > > omap_set_dma_dest_params()
> > >
> > > specifying a virtual address? Can the DMA controller cope with DMAing
> > > to virtual addresses? My hunch is that the DMA controller can't cope
> > > with that, so giving it a virtual address is a bug.
> > >
> > > Let me change the question: does omap_set_dma_dest_params()'s 4th
> > > argument take a virtual or a physical address? If the former, it's
> > > prototype is wrong, and its 4th argument needs to be typed as
> > > 'void __iomem *' rather than 'unsigned long'. If the latter, the code
> > > above is wrong.
> > >
> > > Do you see what I'm getting at now?
> >
> > Ok. I got your point. I took a look at it and it expects a virtual address
> > on its 4th argument.
>
> I'm sorry, but I don't think you have.
>
> > I uses it with dma_write() macro, which uses it with __raw_write()
> > (arch/arm/plat-omap/dma.c).
>
> That's true, but probably not in the way which would require it to be
> a virtual address that you're thinking.
>
> void omap_set_dma_dest_params(int lch, int dest_port, int dest_amode,
> unsigned long dest_start,
> int dst_ei, int dst_fi)
> {
> if (cpu_class_is_omap1()) {
> dma_write(dest_start >> 16, CDSA_U(lch));
> dma_write(dest_start, CDSA_L(lch));
> }
>
> if (cpu_class_is_omap2())
> dma_write(dest_start, CDSA(lch));
> }
>
> 'dest_start' is a value to be written to the hardware registers in
> the DMA controller. So, the question now is: do the CDSA registers
> expect a virtual or a physical address to be written to them?
C[DS][DS]A register need physical addresses for the DMA. The DMA
controller does not know anything about virtual addresses.
> I would look up this CDSA register in the OMAP manuals, if they were
> accessible... Are they not publically available? (Google isn't
> helping, neither is searching on ti.com...)
There is a 3450 public TRM somewhere AFAIK, anybody got a link for that?
At least 5912 TRM is available somewhere.
Tony
next prev parent reply other threads:[~2008-09-03 20:50 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 22:08 FOR COMMENT: void __iomem * and similar casts are Bad News Russell King
2008-08-31 21:47 ` David Brownell
2008-09-02 22:15 ` Tony Lindgren
2008-09-03 7:55 ` Russell King - ARM Linux
2008-09-03 16:40 ` Tony Lindgren
2008-09-03 19:34 ` Russell King - ARM Linux
2008-09-03 19:48 ` Tony Lindgren
2008-09-03 21:09 ` David Brownell
2008-09-03 23:02 ` Russell King - ARM Linux
2008-09-03 19:58 ` Woodruff, Richard
2008-09-03 20:30 ` Russell King - ARM Linux
2008-09-03 21:19 ` Woodruff, Richard
2008-09-03 20:32 ` Tony Lindgren
2008-09-03 21:32 ` Woodruff, Richard
2008-09-03 21:35 ` Tony Lindgren
2008-09-03 21:38 ` Russell King - ARM Linux
2008-09-03 21:46 ` Multi-Boot: Was " Woodruff, Richard
2008-09-03 21:18 ` David Brownell
2008-09-03 21:40 ` Woodruff, Richard
2008-09-03 22:05 ` David Brownell
2008-09-03 22:56 ` Russell King - ARM Linux
2008-09-04 0:28 ` Tony Lindgren
2008-09-04 1:06 ` David Brownell
2008-09-04 7:25 ` Arun KS
2008-09-03 15:07 ` Eduardo Valentin
2008-09-03 18:01 ` Tony Lindgren
2008-09-04 0:16 ` David Brownell
2008-09-03 15:33 ` Eduardo Valentin
2008-09-03 18:48 ` Russell King
2008-09-03 19:33 ` Eduardo Valentin
2008-09-03 19:48 ` Russell King - ARM Linux
2008-09-03 20:04 ` Eduardo Valentin
2008-09-03 20:45 ` Russell King - ARM Linux
2008-09-03 20:50 ` Tony Lindgren [this message]
2008-09-03 20:56 ` Tony Lindgren
2008-09-03 21:07 ` Russell King - ARM Linux
2008-09-03 21:13 ` Tony Lindgren
2008-09-03 21:00 ` Koen Kooi
2008-09-03 20:37 ` Tony Lindgren
2008-09-03 21:04 ` Russell King - ARM Linux
2008-09-03 21:26 ` Eduardo Valentin
2008-09-03 21:48 ` Tony Lindgren
2008-09-03 21:35 ` David Brownell
2008-09-03 23:16 ` Russell King - ARM Linux
2008-09-04 9:46 ` Russell King - ARM Linux
2008-09-04 16:10 ` Tony Lindgren
2008-09-04 16:12 ` Russell King - ARM Linux
2008-09-04 16:29 ` Tony Lindgren
2008-09-04 17:07 ` Russell King - ARM Linux
2008-09-04 17:58 ` Tony Lindgren
2008-09-04 21:01 ` Russell King - ARM Linux
2008-09-04 21:20 ` Tony Lindgren
2008-09-05 1:07 ` Tony Lindgren
2008-09-05 5:17 ` Paul Walmsley
2008-09-05 5:58 ` Paul Walmsley
2008-09-29 5:16 ` Arun KS
2008-09-29 7:44 ` Jarkko Nikula
2008-09-29 9:24 ` Arun KS
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=20080903205004.GW23085@atomide.com \
--to=tony@atomide.com \
--cc=edubezval@gmail.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.