From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Paul Bolle" <pebolle@tiscali.nl>
Cc: "Russell King" <linux@arm.linux.org.uk>,
"Richard Weinberger" <richard@nod.at>,
linux-kernel@vger.kernel.org,
"Sascha Hauer" <kernel@pengutronix.de>,
"Shawn Guo" <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm: imx: remove MACH_MXLADS
Date: Mon, 17 Feb 2014 08:43:07 +0400 [thread overview]
Message-ID: <1392612187.657010375@f87.i.mail.ru> (raw)
In-Reply-To: <1392582900.28866.85.camel@x220>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 2040 bytes --]
ÐоÑкÑеÑенÑе, 16 ÑевÑÐ°Ð»Ñ 2014, 21:35 +01:00 Ð¾Ñ Paul Bolle <pebolle@tiscali.nl>:
> On Sun, 2014-02-16 at 23:21 +0400, Alexander Shiyan wrote:
> > ÐоÑкÑеÑенÑе, 16 ÑевÑÐ°Ð»Ñ 2014, 20:12 +01:00 Ð¾Ñ Paul Bolle
> <pebolle@tiscali.nl>:
> > > On Sun, 2014-02-16 at 23:06 +0400, Alexander Shiyan wrote:
> > > > Kconfig selects MACH_MXLADS, this enables machine_arch_type
> > > > from include/generated/mach-types.h which used for machine_is_xx()
> macro,
> > > > so if multiple boards is defined in the kernel, this cause to incorrect
> > > matching.
> > >
> > > But, as I stated in the commit explanation, there are no users of
> > > machine_is_mxlads().
> >
> > If you have MXLADS and FOO boards support in the kernel (for example)
> > and you want to start MXLADS version, your machine_is_FOO() will be
> positive,
> > since machine_arch_type will be constant value FOO in this case.
>
> I think it might be helpful - for people trying to understand this
> thread - to add a quote from https://lkml.org/lkml/2013/3/8/473 :
> So, the result is that:
> - de-selected platforms have their if (machine_is_xxx()) { } optimised
> out of the kernel.
> - for a kernel built targetting one platform, all the
> if (machine_is_xxx()) tests are optimised away, leaving only the
> relevant code behind.
> - otherwise, we get the _appropriate_ conditional code for the
> configuration generated.
>
> Back to the issue at hand: without my patch ARCH_MX1ADS selects
> MACH_MXLADS. So it seems in this case people will have to select
> ARCH_MX1ADS besides selecting FOO. Wouldn't that solve this problem?
> Note that the MACH_MXLADS is now basically meant to be selected by
> ARCH_MX1ADS and not set directly anyway.
It seems that even in the current state, Kconfig for i.MX contains an error.
As a start, we should rename ARCH_MX1ADS to MACH_MX1ADS first.
---
ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2014-02-17 4:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-16 18:03 Paul Bolle
2014-02-16 18:16 ` Alexander Shiyan
2014-02-16 18:43 ` Paul Bolle
2014-02-16 19:06 ` Alexander Shiyan
2014-02-16 19:12 ` Paul Bolle
2014-02-16 19:21 ` Alexander Shiyan
2014-02-16 20:35 ` Paul Bolle
2014-02-17 4:43 ` Alexander Shiyan [this message]
2014-02-17 9:02 ` Paul Bolle
2014-02-17 9:18 ` 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=1392612187.657010375@f87.i.mail.ru \
--to=shc_work@mail.ru \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pebolle@tiscali.nl \
--cc=richard@nod.at \
--cc=shawn.guo@linaro.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
all inboxes | Powered by JetHome®