linux-kernel - Re: [PATCH V5 2/2] dma: tegra: add dmaengine based dma driver

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]

Date:	Wed, 6 Jun 2012 23:22:27 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	"vinod.koul@...el.com" <vinod.koul@...el.com>,
	"dan.j.williams@...el.com" <dan.j.williams@...el.com>,
	"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"olof@...om.net" <olof@...om.net>,
	"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V5 2/2] dma: tegra: add dmaengine based dma driver

On Wednesday 06 June 2012 11:17 PM, Stephen Warren wrote:
> On 06/05/2012 11:25 PM, Laxman Dewangan wrote:
>> Add dmaengine based NVIDIA's Tegra APB DMA driver.
>> This driver support the slave mode of data transfer from
>> peripheral to memory and vice versa.
>> The driver supports for the cyclic and non-cyclic mode
>> of data transfer.
> Acked-by: Stephen Warren<swarren@...dotorg.org>
>
> Laxman, what are you plans for enabling this and replacing the existing
> non-dmaengine APB DMA driver? We will need to convert:
>
> * The fuse WAR stuff in arch/arm/mach-tegra
> * The ASoC driver in sound/soc/tegra
>
> This will require some thought and dependency management between the
> various subsystems.
Currently following drive using the non-dmanegine apb dma driver:
fuse
SPI
ASoc.

I want to first have this dma driver in the tree and then I will have 
the series of patches to use this dmaengine dma driver and delete the 
old apb dma driver.

So just waiting for this driver to be in.


> Vinod,
>
> It may be best to apply this series along in a topic branch that you
> merge into the dmaengine branch, and I can pull into Tegra if/when I
> need. Or, if you ack it, I can take it all through the Tegra tree if you
> want. That wouldn't allow patch 1 to be use by others though.
>

I like this series to be taken by Vinod. And then pull the change in to 
Tegra tree for further dependency change.
Reason is:
- If there is any dmaengine driver change/enhancement, then tegra dma 
driver will also be inline.
- Taking on tegra tree help to implement the clock framework which is 
going on.
- Also fuse related changes will be in tegra tree.
- Asoc and SPI can be also taken in the tegra tree or may be their 
corresponding tree based on how much other changes are there,
-Deletion of old driver is in Tegra tree.

> Thanks.

--
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/