From: Vinod Koul <vinod.koul@linux.intel.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: dan.j.williams@intel.com, grant.likely@secretlab.ca,
rob.herring@calxeda.com, linux-kernel@vger.kernel.org,
devicetree-discuss@lists.ozlabs.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2 1/2] dma: dmaengine: add slave req id in slave_config
Date: Wed, 09 May 2012 14:19:18 +0530 [thread overview]
Message-ID: <1336553358.1540.169.camel@vkoul-udesk3> (raw)
In-Reply-To: <1336030889-32269-2-git-send-email-ldewangan@nvidia.com>
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.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
>
> This change is require to get rid of tegra_dma header to pass the
> slave requestor id.
>
> include/linux/dmaengine.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/dmaengine.h b/include/linux/dmaengine.h
> index 1082698..b0b275f 100644
> --- a/include/linux/dmaengine.h
> +++ b/include/linux/dmaengine.h
> @@ -338,6 +338,9 @@ enum dma_slave_buswidth {
> * @device_fc: Flow Controller Settings. Only valid for slave channels. Fill
> * with 'true' if peripheral should be flow controller. Direction will be
> * selected at Runtime.
> + * @slave_id: Slave requester id. Only valid for slave channels. The dma
> + * slave peripheral will have unique id as dma requester which need to be
> + * pass as slave config.
> *
> * This struct is passed in as configuration data to a DMA engine
> * in order to set up a certain channel for DMA transport at runtime.
> @@ -365,6 +368,7 @@ struct dma_slave_config {
> u32 src_maxburst;
> u32 dst_maxburst;
> bool device_fc;
> + int slave_id;
This wont be negative, so perhaps an unsigned value?
> };
>
> static inline const char *dma_chan_name(struct dma_chan *chan)
--
~Vinod
next prev parent reply other threads:[~2012-05-09 8:56 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 [this message]
2012-05-09 10:27 ` Laxman Dewangan
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=1336553358.1540.169.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.com \
--cc=dan.j.williams@intel.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.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
all inboxes | Powered by JetHome®