From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 6/6] ARM: mxc: clean up imx-dma device registration
Date: Wed, 22 Jun 2011 00:57:58 +0200 [thread overview]
Message-ID: <20110621225758.GG6069@pengutronix.de> (raw)
In-Reply-To: <20110620145054.GA24184@S2100-06.ap.freescale.net>
On Mon, Jun 20, 2011 at 10:50:55PM +0800, Shawn Guo wrote:
> Hi Sascha,
>
> Any comment on this one?
>
Please respin this series on the for-next branch. Fabio has
added i.MX53 support in the meantime and this does not apply anymore.
Sascha
> Regards,
> Shawn
>
> On Mon, Jun 13, 2011 at 03:37:25PM +0800, Shawn Guo wrote:
> > The patch follows the implementation of gpio-mxc device registration
> > to break the concentrated imx-dma device registration into soc
> > specific setup function. Then we can avoid the churn of "#ifdef"
> > and the cpu_is_mx checking on such a long list, which makes no sense,
> > considering more soc supports need to be added and we need to support
> > single image for multiple socs in the long run.
> >
> > Signed-off-by: Shawn Guo <shawn.guo@linaro.org>
> > ---
> > arch/arm/mach-imx/mm-imx21.c | 3 +
> > arch/arm/mach-imx/mm-imx25.c | 26 +++
> > arch/arm/mach-imx/mm-imx27.c | 3 +
> > arch/arm/mach-imx/mm-imx31.c | 24 +++
> > arch/arm/mach-imx/mm-imx35.c | 44 +++++
> > arch/arm/mach-mx5/mm.c | 23 +++
> > arch/arm/plat-mxc/devices.c | 16 ++-
> > arch/arm/plat-mxc/devices/platform-imx-dma.c | 202 ++---------------------
> > arch/arm/plat-mxc/include/mach/devices-common.h | 6 +
> > 9 files changed, 157 insertions(+), 190 deletions(-)
> >
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2011-06-21 22:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 7:37 [PATCH 0/6] Some fixes and cleanup on imx-dma device registration Shawn Guo
2011-06-13 7:37 ` [PATCH 1/6] ARM: mxc: imx-sdma device gets 16K iosize than 4K Shawn Guo
2011-06-13 7:37 ` [PATCH 2/6] ARM: mxc: sdma on imx25 is a V2 block Shawn Guo
2011-06-13 7:37 ` [PATCH 3/6] ARM: mxc: change imx-dma default to_version to 1 Shawn Guo
2011-06-13 7:37 ` [PATCH 4/6] ARM: mxc: imx-dma on imx25 has no other TO version but TO1 Shawn Guo
2011-06-13 7:37 ` [PATCH 5/6] ARM: mxc: all three imx51 TOs use TO1 version of sdma script Shawn Guo
2011-06-13 12:36 ` Fabio Estevam
2011-06-13 13:05 ` Shawn Guo
2011-06-14 6:20 ` [PATCH v2 " Shawn Guo
2011-06-14 20:38 ` Sascha Hauer
2011-06-15 4:29 ` Shawn Guo
2011-06-16 7:30 ` Sascha Hauer
2011-06-16 11:51 ` Shawn Guo
2011-06-17 1:59 ` Fabio Estevam
2011-06-17 2:27 ` Shawn Guo
2011-06-20 7:20 ` Sascha Hauer
2011-06-13 7:37 ` [PATCH 6/6] ARM: mxc: clean up imx-dma device registration Shawn Guo
2011-06-20 14:50 ` Shawn Guo
2011-06-21 14:41 ` Shawn Guo
2011-06-21 15:13 ` Wolfram Sang
2011-06-22 2:43 ` Shawn Guo
2011-06-22 6:33 ` Wolfram Sang
2011-06-21 22:57 ` Sascha Hauer [this message]
2011-06-22 2:53 ` Shawn Guo
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=20110621225758.GG6069@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).