From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: PLEA: Please fix mach/gpio.h includes (was: Re: [RFC PATCH 2/2] GPIO: add gpiolib and irqchip for CSR SiRFprimaII GPIO controller)
Date: Thu, 11 Aug 2011 09:30:33 +0100 [thread overview]
Message-ID: <20110811083033.GC4775@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAGsJ_4ysq4RruD5oP=B6ZvNCa0baFPxtLdbgpsC8wZQsT1r1yQ@mail.gmail.com>
On Thu, Aug 11, 2011 at 10:25:58AM +0800, Barry Song wrote:
> now every SoCs have different DMA APIs due to different DMA controller:
We already have a solution to this. It's called dmaengine. See
drivers/dma, include/linux/dmaengine.h and Documentation/dmaengine.txt
There is work going on at present to convert the OMAP and Samsung SoC
specific DMA support to dmaengine.
next prev parent reply other threads:[~2011-08-11 8:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 8:13 [RFC PATCH 0/2] add pinmux and gpio for CSR SiRFprimaII Barry Song
2011-07-26 8:13 ` [RFC PATCH 1/2] ARM: CSR: Add pinmux support for SiRFprimaII Barry Song
2011-07-26 8:13 ` [RFC PATCH 2/2] GPIO: add gpiolib and irqchip for CSR SiRFprimaII GPIO controller Barry Song
2011-07-26 10:09 ` Russell King - ARM Linux
2011-07-26 10:46 ` PLEA: Please fix mach/gpio.h includes (was: Re: [RFC PATCH 2/2] GPIO: add gpiolib and irqchip for CSR SiRFprimaII GPIO controller) Russell King - ARM Linux
2011-07-26 18:32 ` Colin Cross
2011-07-26 18:39 ` Russell King - ARM Linux
2011-07-26 19:10 ` Nicolas Pitre
2011-07-27 2:08 ` Barry Song
2011-07-27 2:51 ` Nicolas Pitre
2011-07-29 15:58 ` Linus Walleij
2011-08-09 7:22 ` Barry Song
2011-08-09 13:15 ` Arnd Bergmann
2011-08-11 2:25 ` Barry Song
2011-08-11 8:30 ` Russell King - ARM Linux [this message]
2011-09-19 9:10 ` Linus Walleij
2011-09-19 15:53 ` Arnd Bergmann
2011-08-08 9:09 ` [RFC PATCH 2/2] GPIO: add gpiolib and irqchip for CSR SiRFprimaII GPIO controller Barry Song
2011-08-08 9:32 ` Linus Walleij
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=20110811083033.GC4775@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).