From: Arnd Bergmann <arnd@arndb.de>
To: Roland Stigge <stigge@antcom.de>
Cc: srinivas.bakki@nxp.com, linux@arm.linux.org.uk,
artem.bityutskiy@linux.intel.com, linux-kernel@vger.kernel.org,
kevin.wells@nxp.com, linux-mtd@lists.infradead.org,
aletes.xgr@gmail.com, dwmw2@infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: LPC32xx: Provide DMA filter callbacks via platform data
Date: Thu, 16 Aug 2012 13:59:21 +0000 [thread overview]
Message-ID: <201208161359.21276.arnd@arndb.de> (raw)
In-Reply-To: <1345122935-22115-1-git-send-email-stigge@antcom.de>
On Thursday 16 August 2012, Roland Stigge wrote:
> The SLC and MLC NAND drivers now need their dma_filter callbacks via platform
> data to make them independent of single DMA engine drivers.
>
> (This also helps fixing build errors of the SLC and MLC drivers when building
> as modules because direct access to AMBA dma filter functions isn't available
> via export.)
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
Yes, this looks right.
Acked-by: Arnd Bergmann <arnd@arndb.de>
Once we have proper DT bindings for the DMA channels, we can hopefully
get rid of the auxdata again.
Arnd
next prev parent reply other threads:[~2012-08-16 13:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-16 13:15 [PATCH] ARM: LPC32xx: Provide DMA filter callbacks via platform data Roland Stigge
2012-08-16 13:15 ` [PATCH] mtd: lpc32xx_slc: Make driver independent of AMBA DMA engine driver Roland Stigge
2012-08-16 13:15 ` [PATCH] mtd: lpc32xx_mlc: " Roland Stigge
2012-08-16 13:59 ` Arnd Bergmann [this message]
2012-08-17 10:09 ` [PATCH] ARM: LPC32xx: Provide DMA filter callbacks via platform data Artem Bityutskiy
2012-08-17 10:52 ` Roland Stigge
2012-08-17 11:01 ` Artem Bityutskiy
2012-08-17 11:10 ` Artem Bityutskiy
2012-08-17 11:40 ` Arnd Bergmann
2012-08-17 11:45 ` Roland Stigge
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=201208161359.21276.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=aletes.xgr@gmail.com \
--cc=artem.bityutskiy@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=kevin.wells@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=srinivas.bakki@nxp.com \
--cc=stigge@antcom.de \
/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