From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/5] dma i.MX: remove individual SOC dependency
Date: Tue, 8 Nov 2011 16:22:39 +0100 [thread overview]
Message-ID: <20111108152239.GA9641@pengutronix.de> (raw)
In-Reply-To: <1314168072-13822-3-git-send-email-s.hauer@pengutronix.de>
Vinod,
Ping. Can you please queue this one?
Thanks
Sascha
On Wed, Aug 24, 2011 at 08:41:09AM +0200, Sascha Hauer wrote:
> The individual SoC dependency in Kconfig hardly scales anymore.
> Instead of having such a fine grained dependency just depend
> on ARCH_MXC and risk that the uninformed user has to look in
> the help text to figure out which driver is the correct one.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> Cc: Vinod Koul <vinod.koul@intel.com>
> ---
> drivers/dma/Kconfig | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/Kconfig b/drivers/dma/Kconfig
> index 2e3b3d3..eda9e34 100644
> --- a/drivers/dma/Kconfig
> +++ b/drivers/dma/Kconfig
> @@ -124,7 +124,7 @@ config MV_XOR
>
> config MX3_IPU
> bool "MX3x Image Processing Unit support"
> - depends on ARCH_MX3
> + depends on ARCH_MXC
> select DMA_ENGINE
> default y
> help
> @@ -215,11 +215,11 @@ config PCH_DMA
>
> config IMX_SDMA
> tristate "i.MX SDMA support"
> - depends on ARCH_MX25 || ARCH_MX3 || ARCH_MX5
> + depends on ARCH_MXC
> select DMA_ENGINE
> help
> Support the i.MX SDMA engine. This engine is integrated into
> - Freescale i.MX25/31/35/51 chips.
> + Freescale i.MX25/31/35/51/53 chips.
>
> config IMX_DMA
> tristate "i.MX DMA support"
> --
> 1.7.5.4
>
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
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-11-08 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 6:41 remove several ARCH_MX* macros Sascha Hauer
2011-08-24 6:41 ` [PATCH 1/5] mmc i.MX: remove individual SoC dependency Sascha Hauer
2011-08-28 17:51 ` Chris Ball
2011-08-24 6:41 ` [PATCH 2/5] dma i.MX: remove individual SOC dependency Sascha Hauer
2011-11-08 15:22 ` Sascha Hauer [this message]
2011-11-08 16:10 ` Vinod Koul
2011-11-08 20:26 ` Uwe Kleine-König
2011-11-09 11:29 ` Sascha Hauer
2011-11-08 20:42 ` Michał Mirosław
2011-11-09 11:27 ` Sascha Hauer
2011-08-24 6:41 ` [PATCH 3/5] USB host i.MX21: remove dependency on MACH_MX21 Sascha Hauer
2011-08-24 6:41 ` [PATCH 4/5] USB gadget i.MX1: remove dependency on ARCH_MXC Sascha Hauer
2011-08-24 6:41 ` [PATCH 5/5] media i.MX1 camera: remove dependency on ARCH_MX1 Sascha Hauer
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=20111108152239.GA9641@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).