From: kmpark@infradead.org (Kyungmin Park)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM:SAMSUNG: Move S3C DMA driver to drivers/dma
Date: Tue, 7 Jun 2011 17:35:42 +0900 [thread overview]
Message-ID: <BANLkTinDBebMiK9Ezu=QDpC2+rChApd64Q@mail.gmail.com> (raw)
In-Reply-To: <20110607081527.GB20929@n2100.arm.linux.org.uk>
On Tue, Jun 7, 2011 at 5:15 PM, Russell King - ARM Linux
<linux@arm.linux.org.uk> wrote:
> On Tue, Jun 07, 2011 at 01:39:43PM +0530, Jassi Brar wrote:
>> Unfortunately, no. There are some features of Samsung's DMA API that
>> the drivers have come to rely upon.
>> Besides, I am not particularly a fan of the generic API. And IIRC,
>> neither is Ben Dooks, the designer of the
>> Samsung's DMA API.
>
> We are now at the point where this is non-optional. ?If the generic API
> doesn't fit what Samsung needs, then that needs to be discussed and
> whatever problems there are need to be resolved.
>
> Continuing the platform specific DMA APIs is not sustainable.
>
> I'm getting rather fed up with Samsung needing custom this and that, and
> refusing to use the generic infrastructure such as clkdev. ?This attitude
> needs to change NOW.
>
> Fix your platform specific crap and start using the generic services.
>
I think Jassi is the right person to handle this one even though you
don't like the generic DMA APIs
1) since you become a member of linaro. it's role of linaro.
2) know the how to use the s3c-pl330 at sound (most user of DMA is
sound, SPI and MMC)
3) now you're the Samsung Sound maintainer
If we move the generic DMA APIs, it's also need to modify the its
consumer, sound and SPI.
Thank you,
Kyungmin Park
next prev parent reply other threads:[~2011-06-07 8:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 7:48 [PATCH] ARM:SAMSUNG: Move S3C DMA driver to drivers/dma root
2011-06-07 8:00 ` Kyungmin Park
2011-06-07 8:09 ` Jassi Brar
2011-06-07 8:15 ` Russell King - ARM Linux
2011-06-07 8:35 ` Kyungmin Park [this message]
2011-06-07 10:15 ` Jassi Brar
2011-06-07 18:29 ` Russell King - ARM Linux
2011-06-07 18:43 ` Mark Brown
2011-06-07 19:01 ` Jassi Brar
2011-06-07 21:41 ` Mark Brown
2011-06-08 2:51 ` Jassi Brar
2011-06-08 8:55 ` Mark Brown
2011-06-07 22:28 ` Russell King - ARM Linux
2011-06-08 4:05 ` Jassi Brar
2011-06-08 7:44 ` Russell King - ARM Linux
2011-06-07 19:46 ` Jassi Brar
2011-06-07 22:36 ` Russell King - ARM Linux
2011-06-09 18:24 ` Kukjin Kim
2011-06-16 12:56 ` Kyungmin Park
2011-06-23 6:47 ` Kukjin Kim
2011-06-07 10:15 ` Linus Walleij
2011-06-07 10:05 ` Koul, Vinod
2011-06-07 8:01 ` Jassi Brar
2011-06-07 15:42 ` Tushar Behera
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='BANLkTinDBebMiK9Ezu=QDpC2+rChApd64Q@mail.gmail.com' \
--to=kmpark@infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).