Skip to contentSkip to conversation

Non-coherent memory mapped devices

DISCUSSION Laurent Canet 3 participants 3 messages Mar 18, 2003 – Mar 19, 2003

lore
Share & tools
lore
#0 lore raw

Hi,

On the HPPA architecture, devices (including sound ones) are memory-mapped.
On particular machines, memory access to devices are not consistent,
i.e. data wrote to memory could be cached by the CPU, thus inacessible
to the device.
To avoid inconsistency in memory writes, there are arch-dep functions
that flush write buffers. They are defined in <asm/io.h> as
dma_cache_inv(start,size), dma_cache_wback and dma_cache_wback_inv; and should be called after all DMA memory writes.

On architectures that don't have such cache issues (most ia32, ia64, alpha, mips, ppc, ...), they are just NOP.

I grepped out the whole alsa source tree and didn't find any occurences
of dma_cache_* functions. Who should implement these calls, low level drivers or PCM middle layer ?

Thanks for your answer

-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en

#1 lore raw
Quoted 10 lines · Laurent Canet

Hi,

On the HPPA architecture, devices (including sound ones) are memory-mapped.
On particular machines, memory access to devices are not consistent,
i.e. data wrote to memory could be cached by the CPU, thus inacessible
to the device.
To avoid inconsistency in memory writes, there are arch-dep functions
that flush write buffers. They are defined in <asm/io.h> as
dma_cache_inv(start,size), dma_cache_wback and dma_cache_wback_inv; and should be called after all DMA memory writes.

Quoted 4 lines

On architectures that don't have such cache issues (most ia32, ia64, alpha, mips, ppc, ...), they are just NOP.

I grepped out the whole alsa source tree and didn't find any occurences
of dma_cache_* functions. Who should implement these calls, low level drivers or PCM middle layer ?

This code belongs to both midlevel and lowlevel drivers. See snd_pcm_lib_*_transfer() routines in pcm_lib.c.

Also, we'll probably need to define these functions in our library, because we can access directly to DMA ring buffers there, too.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs

-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en

#2 lore raw
In reply to Laurent Canet

Hi,

At Tue, 18 Mar 2003 20:48:08 +0100,

Quoted 7 lines · Laurent Canet

Hi,

On the HPPA architecture, devices (including sound ones) are memory-mapped. On particular machines, memory access to devices are not consistent, i.e. data wrote to memory could be cached by the CPU, thus inacessible to the device.

doesn't ioremap_nocache() suffice for such a case?

Takashi

-------------------------------------------------------
This SF.net email is sponsored by: Does your code think in ink? You could win a Tablet PC. Get a free Tablet PC hat just for playing. What are you waiting for?
http://ads.sourceforge.net/cgi-bin/redirect.pl?micr5043en