From: robherring2@gmail.com (Rob Herring)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] cpuidle / calxeda: remove redundant Kconfig option
Date: Tue, 19 Mar 2013 10:13:51 -0500 [thread overview]
Message-ID: <514880AF.7010404@gmail.com> (raw)
In-Reply-To: <514877B5.6080200@linaro.org>
On 03/19/2013 09:35 AM, Daniel Lezcano wrote:
> On 03/19/2013 01:22 PM, Rob Herring wrote:
>> On 03/12/2013 04:27 AM, Daniel Lezcano wrote:
>>> When the CPU_IDLE and the ARCH_HIGHBANK options are set it is
>>> pointless to define a new option CPU_IDLE_CALXEDA because it
>>> is redundant.
>>>
>>> The Makefile drivers directory contains a condition to compile
>>> the cpuidle drivers:
>>>
>>> obj-$(CONFIG_CPU_IDLE) += cpuidle/
>>>
>>> Hence, if CPU_IDLE is not set we won't enter this directory.
>>>
>>> This patch removes the useless Kconfig option and replaces the
>>> condition in the Makefile by CONFIG_ARCH_HIGHBANK.
>>
>> If I have multiple platforms including highbank compiled in, but want to
>> disable cpuidle just for highbank, then you can't disable it at compile
>> time.
>
> Could you elaborate a bit ? Is it today possible to have multiple
> platforms in a single kernel ?
You've heard of single zImage, right? Vexpress, mvebu, highbank, imx,
omap2+, socfpga, vt8500 off the top of my head as of 3.8.
Rob
next prev parent reply other threads:[~2013-03-19 15:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-12 9:27 [PATCH 1/2] cpuidle / kirkwood: remove redundant Kconfig option Daniel Lezcano
2013-03-12 9:27 ` [PATCH 2/2] cpuidle / calxeda: " Daniel Lezcano
2013-03-19 11:49 ` Daniel Lezcano
2013-03-19 12:22 ` Rob Herring
2013-03-19 14:35 ` Daniel Lezcano
2013-03-19 15:13 ` Rob Herring [this message]
2013-03-19 22:03 ` Daniel Lezcano
2013-03-12 11:22 ` [PATCH 1/2] cpuidle / kirkwood: " Jason Cooper
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=514880AF.7010404@gmail.com \
--to=robherring2@gmail.com \
--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).