[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F91686A.1030000@nvidia.com>
Date: Fri, 20 Apr 2012 19:15:14 +0530
From: Laxman Dewangan <ldewangan@...dia.com>
To: Vinod Koul <vinod.koul@...ux.intel.com>
CC: "dan.j.williams@...el.com" <dan.j.williams@...el.com>,
"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
Stephen Warren <swarren@...dia.com>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH V1] dmaengine: tegra: add dma driver
Hi Vinod,
On Friday 20 April 2012 05:46 PM, Laxman Dewangan wrote:
> Thanks Vinod for quick review.
>
>>> + * @dma_dev: required DMA master client device.
>>> + * @dm_req_id: Peripheral dma requestor ID.
>>> + */
>>> +struct tegra_dma_slave {
>>> + struct device *client_dev;
>>> + enum tegra_dma_requestor dma_req_id;
>>> + enum tegra_dma_burst_size burst_size;
>> pls remove
> if above is OK then I can remove this.
>
If I add one more member as slave_id for slave requester in struct
dma_slave_config then I will not need the tegra_dma header at all and I
can get rid of this file.
Let me know if this is OK so that I can take care of this in my next patch.
Thanks,
Laxman
--
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