[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A2508D5.2040809@petalogix.com>
Date: Tue, 02 Jun 2009 13:11:17 +0200
From: Michal Simek <michal.simek@...alogix.com>
To: Arnd Bergmann <arnd@...db.de>
CC: FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
lethal@...ux-sh.org, chris@...kel.net,
John Williams <john.williams@...alogix.com>
Subject: Re: [PATCH] asm-generic: add dma-mapping-linear.h
Arnd Bergmann wrote:
> On Monday 01 June 2009, Michal Simek wrote:
>
>
>> Microblaze have it but it is not cleared(checked) and not in mainline -
>> I want to look at it when mmu is in mainline.
>> As I wrote before you can use Microblaze as tested arch.
>>
>
> Ok. It should become really easy once the asm-generic version is there.
> Do you know if all DMA capable devices on microblaze are coherent
> (or if all of them are noncoherent)?
>
We don't have cache coherency modul.
> If it is indeed coherent, the below code should be enough, otherwise
> you need to add some cache flushes in the functions below.
>
I'll send you special email about to find out proper solution for
Microblaze.
Michal
> Arnd <><
>
> ---
> #ifndef _ASM_MICROBLAZE_DMA_MAPPING_H
> #define _ASM_MICROBLAZE_DMA_MAPPING_H
>
> static inline int
> __dma_coherent_dev(struct device *dev)
> {
> return 1;
> }
>
> static inline void
> dma_cache_sync(struct device *dev, void *cpu_addr, size_t size,
> enum dma_data_direction direction)
> {
> }
>
> static inline int dma_get_cache_alignment(void)
> {
> return 1 << L1_CACHE_SHIFT;
> }
>
> #include <asm-generic/dma-mapping-linear.h>
>
> #endif _ASM_MICROBLAZE_DMA_MAPPING_H
>
--
Michal Simek, Ing. (M.Eng)
PetaLogix - Linux Solutions for a Reconfigurable World
w: www.petalogix.com p: +61-7-30090663,+42-0-721842854 f: +61-7-30090663
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists