From: Vinod Koul <vinod.koul@linux.intel.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Paul Mundt <lethal@linux-sh.org>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org,
Dan Williams <dan.j.williams@intel.com>,
Magnus Damm <damm@opensource.se>
Subject: Re: [PATCH] serial: sh-sci: don't filter on DMA device, use only channel ID
Date: Tue, 30 Aug 2011 15:32:02 +0530 [thread overview]
Message-ID: <1314698522.1606.164.camel@vkoul-udesk3> (raw)
In-Reply-To: <Pine.LNX.4.64.1108300931220.19151@axis700.grange>
On Tue, 2011-08-30 at 09:54 +0200, Guennadi Liakhovetski wrote:
> On Mon, 29 Aug 2011, Vinod Koul wrote:
> > > >> You should not assign chan->private.
> > > >> Please move this to dma_slave_control API
> > > >
> > > > I haven't seen any reply to this comment and this patch seems to still be
> > > > outstanding, is there an updated version of this patch that I've missed?
> > I don't recall seeing any updated version fixing this
>
> As a matter of fact, when you say "use dma_slave_control API," you
> actually mean the dma_slave_config, right? Then, how is one supposed to
> use it in this case? Shall we be issuing a DMA_SLAVE_CONFIG call inside of
> the filter and check the return code? The problem is, that not all DMA
> controllers on sh-mobile SoCs can service the same slave devices. So, if
> we don't check in the filter we might well get an unsuitable DMA channel.
Here you are assigning to chan->private your specific values, which
should be moved to the dma_slave_config.
But here you are removing the checks, and accepting the first channel
you got, so how do you find channel is suitable or not.
--
~Vinod
next prev parent reply other threads:[~2011-08-30 10:03 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 11:56 Guennadi Liakhovetski
2011-06-24 11:47 ` Koul, Vinod
2011-08-29 8:00 ` Paul Mundt
2011-08-29 8:16 ` Magnus Damm
2011-08-29 11:55 ` Vinod Koul
2011-08-30 7:54 ` Guennadi Liakhovetski
2011-08-30 10:02 ` Vinod Koul [this message]
2011-08-30 11:20 ` Guennadi Liakhovetski
2011-08-30 11:23 ` Vinod Koul
2011-08-30 11:40 ` Guennadi Liakhovetski
2011-09-05 8:04 ` Guennadi Liakhovetski
2011-09-05 13:13 ` Vinod Koul
2011-09-05 13:48 ` Guennadi Liakhovetski
2011-09-05 14:43 ` Vinod Koul
2011-09-05 15:01 ` Guennadi Liakhovetski
2011-09-05 15:08 ` Vinod Koul
2011-09-05 15:21 ` Guennadi Liakhovetski
2011-09-07 18:42 ` Koul, Vinod
2011-09-07 20:01 ` Guennadi Liakhovetski
2011-09-07 21:37 ` Koul, Vinod
2011-09-08 1:21 ` Paul Mundt
2011-09-08 19:31 ` Vinod Koul
2011-09-14 5:16 ` Vinod Koul
2011-09-14 18:52 ` Alan Cox
2011-09-19 3:13 ` Vinod Koul
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=1314698522.1606.164.camel@vkoul-udesk3 \
--to=vinod.koul@linux.intel.com \
--cc=damm@opensource.se \
--cc=dan.j.williams@intel.com \
--cc=g.liakhovetski@gmx.de \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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®