From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: Jaswinder Singh <jaswinder.singh@linaro.org>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, rmk+kernel@arm.linux.org.uk,
linus.walleij@stericsson.com, per.friden@stericsson.com,
wei.zhang@freescale.com, ebony.zhu@freescale.com,
iws@ovro.caltech.edu, s.hauer@pengutronix.de,
maciej.sosnowski@intel.com, saeed@marvell.com,
shawn.guo@freescale.com, yur@emcraft.com, agust@denx.de,
iwamatsu.nobuhiro@renesas.com, per.forlin@stericsson.com,
jonas.aberg@stericsson.com, anemo@mba.ocn.ne.jp
Subject: Re: [PATCHv2] DMAEngine: Let dmac drivers to set chan_id
Date: Wed, 27 Jul 2011 12:59:09 +0300 [thread overview]
Message-ID: <20110727095909.GB16623@intel.com> (raw)
In-Reply-To: <1311757347.1536.103.camel@vkoul-udesk3>
On Wed, Jul 27, 2011 at 02:32:26PM +0530, Koul, Vinod wrote:
> Can you please help me understand why channel number "x" is important
> and strictly needed by some client?
At least in ep93xx we have even channel numbers for TX and odd for RX (or
vice versa, can't rememeber). This is a hardware restriction. So the client
code then filters the channels based on that using ->chan_id.
As the caps are not per channel, that is the only way I was able to make it
work.
next prev parent reply other threads:[~2011-07-27 9:58 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 18:18 [PATCH] DMAEngine: Let dmac drivers set chan_id Jassi Brar
2011-07-21 4:01 ` [PATCHv2] DMAEngine: Let dmac drivers to " Jassi Brar
2011-07-22 15:27 ` Linus Walleij
2011-07-22 17:43 ` Jaswinder Singh
2011-07-22 22:23 ` Williams, Dan J
2011-07-23 3:56 ` Jaswinder Singh
2011-07-25 18:55 ` Williams, Dan J
2011-07-25 19:17 ` Jaswinder Singh
2011-07-25 20:08 ` Williams, Dan J
2011-07-26 14:30 ` Jaswinder Singh
2011-07-26 15:29 ` Williams, Dan J
2011-07-26 18:12 ` Jaswinder Singh
2011-07-27 4:21 ` Koul, Vinod
2011-07-27 7:17 ` Jaswinder Singh
2011-07-27 9:02 ` Koul, Vinod
2011-07-27 9:59 ` Mika Westerberg [this message]
2011-07-27 9:34 ` Koul, Vinod
2011-07-27 10:36 ` Mika Westerberg
2011-07-27 14:50 ` Jaswinder Singh
2011-07-27 16:36 ` Williams, Dan J
2011-07-27 17:14 ` Jaswinder Singh
2011-07-27 20:28 ` Russell King
2011-07-28 10:44 ` Jaswinder Singh
2011-07-28 22:27 ` Linus Walleij
2011-07-28 22:43 ` Russell King
2011-07-29 12:20 ` Linus Walleij
2011-07-29 11:54 ` Koul, Vinod
2011-07-28 22:35 ` Russell King
2011-07-29 14:11 ` Jaswinder Singh
2011-07-27 14:30 ` Jaswinder Singh
2011-07-27 20:37 ` Russell King
2011-07-28 10:56 ` Jaswinder Singh
2011-07-28 13:44 ` Russell King
2011-07-28 17:54 ` Jaswinder Singh
2011-07-28 18:14 ` Williams, Dan J
2011-07-28 18:25 ` Jaswinder Singh
2011-07-28 22:40 ` Russell King
2011-07-30 13:09 ` Jaswinder Singh
2011-07-30 14:22 ` Russell King
2011-07-30 15:00 ` Jaswinder Singh
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=20110727095909.GB16623@intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=agust@denx.de \
--cc=anemo@mba.ocn.ne.jp \
--cc=dan.j.williams@intel.com \
--cc=ebony.zhu@freescale.com \
--cc=iwamatsu.nobuhiro@renesas.com \
--cc=iws@ovro.caltech.edu \
--cc=jaswinder.singh@linaro.org \
--cc=jonas.aberg@stericsson.com \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=per.forlin@stericsson.com \
--cc=per.friden@stericsson.com \
--cc=rmk+kernel@arm.linux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=saeed@marvell.com \
--cc=shawn.guo@freescale.com \
--cc=vinod.koul@intel.com \
--cc=wei.zhang@freescale.com \
--cc=yur@emcraft.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