From: Laxman Dewangan <ldewangan@nvidia.com>
To: Vinod Koul <vinod.koul@linux.intel.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>
Subject: Re: [PATCH V2 1/2] dma: dmaengine: add slave req id in slave_config
Date: Wed, 9 May 2012 15:57:50 +0530 [thread overview]
Message-ID: <4FAA46A6.4090003@nvidia.com> (raw)
In-Reply-To: <1336553358.1540.169.camel@vkoul-udesk3>
Thanks for review.
On Wednesday 09 May 2012 02:19 PM, Vinod Koul wrote:
> On Thu, 2012-05-03 at 13:11 +0530, Laxman Dewangan wrote:
>> The dma controller like Nvidia's Tegra Dma controller
>> supports the different slave requestor id from different slave.
>> This need to be configure in dma controller to handle the request
>> properly.
>>
>> Adding the slave-id in the slave configuration so that information
>> can be passed from client when configuring for slave.
>>
>> u32 dst_maxburst;
>> bool device_fc;
>> + int slave_id;
> This wont be negative, so perhaps an unsigned value?
Fine, I will make it unsigned int in my next patch.
next prev parent reply other threads:[~2012-05-09 10:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 7:41 [PATCH V2 0/2] dmaengine: tegra: add dma driver Laxman Dewangan
2012-05-03 7:41 ` [PATCH V2 1/2] dma: dmaengine: add slave req id in slave_config Laxman Dewangan
2012-05-09 8:49 ` Vinod Koul
2012-05-09 10:27 ` Laxman Dewangan [this message]
2012-05-03 7:41 ` [PATCH V2 2/2] dmaengine: tegra: add dma driver Laxman Dewangan
2012-05-09 10:14 ` Vinod Koul
2012-05-09 11:01 ` Laxman Dewangan
2012-05-10 3:34 ` Vinod Koul
2012-05-10 5:05 ` Laxman Dewangan
2012-05-11 8:41 ` Vinod Koul
2012-05-11 10:58 ` Laxman Dewangan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FAA46A6.4090003@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=vinod.koul@linux.intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox