linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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: Wed, 9 Nov 2011 12:27:34 +0100	[thread overview]
Message-ID: <20111109112734.GI16886@pengutronix.de> (raw)
In-Reply-To: <CAHXqBFKps1jsaKCr9yqQY72zAQHT6HU78eJ+adbYfnhRhkKQog@mail.gmail.com>

On Tue, Nov 08, 2011 at 09:42:56PM +0100, Micha? Miros?aw wrote:
> 2011/8/24 Sascha Hauer <s.hauer@pengutronix.de>:
> > 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.
> [...]
> > ?config MX3_IPU
> > ? ? ? ?bool "MX3x Image Processing Unit support"
> > - ? ? ? depends on ARCH_MX3
> > + ? ? ? depends on ARCH_MXC
> > ? ? ? ?select DMA_ENGINE
> > ? ? ? ?default y
> > ? ? ? ?help
> 
> You could instead make it depend on HAVE_MX3_IPU and select this
> symbol from relevant model config. Leaving it for the users is making
> every one of them redo the work you already did.

I thought about this. I came to the conclusion that these are quite hard
to change when they are present in many subsystems (I try to get rid of
ARCH_MXx macros for some time now). Also with upcoming devicetree
support the IMX_HAVE_ macros will loose their meaning anyway. Being a
bit more relaxed with the 'depends on' only means that a user might
compile in some unused drivers, which is the standard case on other
architectures like x86 anyway.

Sascha

-- 
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 |

  reply	other threads:[~2011-11-09 11:27 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
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 [this message]
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=20111109112734.GI16886@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).