From: Russell King <rmk@arm.linux.org.uk>
To: Jaswinder Singh <jaswinder.singh@linaro.org>
Cc: "Koul, Vinod" <vinod.koul@intel.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-kernel@vger.kernel.org, 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 21:37:11 +0100 [thread overview]
Message-ID: <20110727203710.GB5028@flint.arm.linux.org.uk> (raw)
In-Reply-To: <CAJe_Zhd+Z4-=xDzFrd3ARuKZkUAo6n_miQgdSADY9Uk6uhkqhw@mail.gmail.com>
On Wed, Jul 27, 2011 at 08:00:23PM +0530, Jaswinder Singh wrote:
> On 27 July 2011 14:32, Koul, Vinod <vinod.koul@intel.com> wrote:
> > You can have two different DMACs in same system. At least I have two
> > from current intel_mid_dma which are used. Both give their channel id
> > starting from 0, 1....
> > Further as we integrate video, audio, spi, emmc dmacs possibility of
> > having multiple dmacs will increase in a system
>
> Most of Samsung's S5P series have 3 DMACs - 2 for peripherals and 1 for
> mem->mem But that is not the point.
>
> This patch in no way affects what values currently a dmac driver
> assigns to chan_id
Then *explain* how the chan_id is used to match the channel which the
peripheral requires when you have three DMA controllers, each with
channels numbered 0 to 7.
> > Sorry I didn't get you.
> > As I understand you are trying to simplify the filter function by
> > assigning unique ids to all channels,
>
> No dear. Let me put it precisely.
>
> Even if we make no further change to the dmaengine, this patch is the right
> thing to do today.
You sound like a politician. "the right thing to do" is a cop-out. That
says "believe me, I know I'm right, but I can't say why I'm right, I just
am." Basically, it means that the person saying it has no clue on the
subject they're talking about.
If you do have a clue, then don't say that infuriating phrase, but give an
actual reason.
> On a serious note, my proposal, and the reply, shows the possibility
> of having :-
> a) Client drivers that are truly platform agnostic -- no platform_data
> poking for
> channel selection
I really doubt that's even possible. Take this setup:
MMCI ---> DMAC
where the DMAC has 32 request signals, and 8 channels. The MMCI is
connected to two of them. The DMAC can supply any of its physical
channels for MMCI.
Board 1 has the MMCI connected to request signals #1 and #3. Board 2
has the MMCI connected to request signals #8 and #22. Board 3 has
the MMCI connected through an external FPGA mux, which can route the
MMCI requests to DMA request signals #1, #2 or #3.
Now, explain how a channel is selected for each of those two boards, and
the DMA controller is provided with the relevant request signal is found
without platform data involved, using _only_ your 'capabilities' bitfield
and the channel ID number.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2011-07-27 20:37 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-20 18:18 [PATCH] DMAEngine: Let dmac drivers " 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
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 [this message]
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=20110727203710.GB5028@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--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=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
all inboxes | Powered by JetHome®