From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: imx: move selection between i.MX21 and i.MX27 to CPU family choice
Date: Thu, 3 Mar 2011 17:25:13 +0100 [thread overview]
Message-ID: <20110303162513.GS22310@pengutronix.de> (raw)
In-Reply-To: <20110303121153.GJ29521@pengutronix.de>
Hello Sascha,
On Thu, Mar 03, 2011 at 01:11:53PM +0100, Sascha Hauer wrote:
> config SOC_IMX27
> bool
> + select ARCH_MX2
> + select MACH_MX27
I'd let MACH_MX27 select ARCH_MX2, but that's just a minor detail.
> select CPU_ARM926T
> select ARCH_MXC_AUDMUX_V1
> select IMX_HAVE_DMA_V1
> select IMX_HAVE_IOMUX_V1
> select MXC_AVIC
>
> -if ARCH_MX1
> +config IMX_MULTI_ARCHITECTURE
> + bool "i.MX multi architecture support"
> + depends on ARM_PATCH_PHYS_VIRT
> + depends on AUTO_ZRELADDR
depends on EXPERIMENTAL?
> +
> +if IMX_MULTI_ARCHITECTURE
> +config ARCH_IMX_MULTI_MX1
> + select SOC_IMX1
> + bool "i.MX1 support"
> +
> +config ARCH_IMX_MULTI_MX21
> + select SOC_IMX21
> + bool "i.MX21 support"
> +
> +config ARCH_IMX_MULTI_MX25
> + select SOC_IMX25
> + bool "i.MX25 support"
> +
> +config ARCH_IMX_MULTI_MX27
> + select SOC_IMX27
> + bool "i.MX27 support"
I'm not sure it's a good idea to use SOC_IMX21 et al for both, Kconfig
logic to select machines and to signal there are machines selected with
the correspondig soc.
On reason is that selecting ARCH_IMX_MULTI_MX21 and ARCH_IMX_MULTI_MX27
but no i.MX21 based machine currently makes cpu_is_mx27() more (runtime)
complicated than necessary.
Just judging the UI it looks good. (I.e. I like the explicit "i.MX
multi architecture support" knob.)
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-K?nig |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-03-03 16:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 3:28 [RFC PATCH 1/1] ARM: imx5x: clean up ARCH_MX5X Richard Zhao
2011-03-02 9:54 ` Shawn Guo
2011-03-02 11:25 ` Uwe Kleine-König
2011-03-02 16:06 ` Richard Zhao
2011-03-02 16:33 ` Uwe Kleine-König
2011-03-03 6:17 ` Richard Zhao
2011-03-02 17:23 ` [PATCH] ARM: imx: move selection between i.MX21 and i.MX27 to CPU family choice Uwe Kleine-König
2011-03-03 5:26 ` Richard Zhao
2011-03-03 10:02 ` Uwe Kleine-König
2011-03-03 12:11 ` Sascha Hauer
2011-03-03 16:25 ` Uwe Kleine-König [this message]
2011-03-03 18:00 ` Sascha Hauer
2011-03-03 20:10 ` Uwe Kleine-König
2011-03-04 8:19 ` Sascha Hauer
2011-03-04 10:11 ` Uwe Kleine-König
2011-03-04 21:20 ` Uwe Kleine-König
2011-03-04 22:28 ` Uwe Kleine-König
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=20110303162513.GS22310@pengutronix.de \
--to=u.kleine-koenig@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).