From: vinod.koul@intel.com (Vinod Koul)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: add CSR SiRFprimaII DMAC driver
Date: Wed, 14 Sep 2011 10:24:17 +0530 [thread overview]
Message-ID: <1315976057.26251.461.camel@vkoul-udesk3> (raw)
In-Reply-To: <CACRpkdYkuhhR8yNMK1cENan9WX5Fv7o_0qSN3_c3VJQwrvzgjg@mail.gmail.com>
On Sun, 2011-09-11 at 23:27 +0200, Linus Walleij wrote:
> On Thu, Sep 8, 2011 at 11:38 PM, Vinod Koul <vkoul@infradead.org> wrote:
> >
> > Linus W, any progress on that patches you posted??
>
> I haven't written any, and I felt the whole issue was pretty inflamed
> too so I felt bad about it and avoided to think about it even since
> I have no real problem with this in my current setups.
>
> Currently there is a strong coupling between platforms and filter
> functions and I can live with it in the systems I use since they have
> just one DMAC and need only one filter function per device,
> that is specified in platform data for the device. This would likely
> also work for the SiRFprimaII if it has only a single DMAC.
> The people facing an immediate issue with this are IIRC the
> Samsung S5Ps.
>
> If you think this is in need of solving soon and want me to propose
> patches for channel mapping to devices using the approach used in
> clkdev and regulator APIs to create an attributed mapping table
> using struct device * or its string representations, I can
> try it out of course, but if it gets flamy I will just back off again.
Please try at my request. I really would like this problem to be solved.
What we want is API which solves filter function issues (we should be
able to completely do away after proper mapping). Making a simple to
understand/code/maintain scheme which is platform independent.
--
~Vinod
next prev parent reply other threads:[~2011-09-14 4:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-07 5:41 [PATCH] dmaengine: add CSR SiRFprimaII DMAC driver Barry Song
2011-09-07 16:14 ` Koul, Vinod
2011-09-07 16:46 ` Barry Song
2011-09-07 18:09 ` Koul, Vinod
2011-09-08 2:18 ` Barry Song
[not found] ` <CAGsJ_4yeovNP=6CKTafbxrBTrYQ42B9yvAOM8gM_bYqD6mTnUw@mail.gmail.com>
2011-09-08 3:17 ` Jassi Brar
2011-09-08 5:25 ` Jassi Brar
2011-09-08 6:36 ` Barry Song
2011-09-08 7:49 ` Jassi Brar
2011-09-08 21:51 ` Vinod Koul
2011-09-09 2:35 ` Barry Song
2011-09-09 2:52 ` Barry Song
2011-09-09 16:25 ` Vinod Koul
2011-09-09 23:37 ` Barry Song
2011-09-11 15:59 ` Vinod Koul
2011-09-12 0:13 ` Barry Song
2011-09-08 21:46 ` Vinod Koul
2011-09-09 8:18 ` Barry Song
2011-09-09 16:21 ` Vinod Koul
2011-09-09 23:40 ` Barry Song
2011-09-10 7:33 ` Jassi Brar
2011-09-11 16:02 ` Vinod Koul
2011-09-12 6:33 ` Jassi Brar
2011-09-14 5:07 ` Vinod Koul
2011-09-14 6:46 ` Barry Song
2011-09-14 7:11 ` Jassi Brar
2011-09-14 9:49 ` Barry Song
2011-09-08 6:14 ` Barry Song
2011-09-08 6:37 ` Jassi Brar
2011-09-16 9:06 ` Barry Song
2011-09-07 19:27 ` Linus Walleij
2011-09-08 1:47 ` Barry Song
2011-09-08 14:52 ` Arnd Bergmann
2011-09-08 15:27 ` Barry Song
2011-09-08 16:19 ` Arnd Bergmann
2011-09-08 18:48 ` Linus Walleij
2011-09-08 20:11 ` Arnd Bergmann
2011-09-08 21:38 ` Vinod Koul
2011-09-11 21:27 ` Linus Walleij
2011-09-12 0:01 ` Barry Song
2011-09-14 4:54 ` Vinod Koul [this message]
2011-09-09 16:10 ` 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=1315976057.26251.461.camel@vkoul-udesk3 \
--to=vinod.koul@intel.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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