linux-kernel - Re: [PATCHv4] DMAEngine: Define interleaved transfer request api

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAJe_ZhfyTBgH7wqB1HWtkjDNusecTOTZrqyYKF=Lwb9xQAXA3w@mail.gmail.com>
Date:	Fri, 30 Sep 2011 21:31:28 +0530
From:	Jassi Brar <jaswinder.singh@...aro.org>
To:	Barry Song <21cnbao@...il.com>
Cc:	Vinod Koul <vinod.koul@...el.com>, linux-kernel@...r.kernel.org,
	dan.j.williams@...el.com, rmk@....linux.org.uk,
	DL-SHA-WorkGroupLinux <workgroup.linux@....com>
Subject: Re: [PATCHv4] DMAEngine: Define interleaved transfer request api

On 30 September 2011 12:13, Barry Song <21cnbao@...il.com> wrote:
>
> i support we can update dma_data_direction to:   MEM_TO_MEM,
> MEM_TO_DEV,  DEV_TO_MEM, DEV_TO_DEV.
>
So basically you are suggesting to replace 'enum dma_data_direction'
with 'enum xfer_direction'
I am not sure about that. I think they represent different things and
hence should be separate.
dma_data_direction tells the mapping of a buffer while the other
tells if the src and dst are memory or a device's FIFO.
--
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/