linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: arnaud.patard@rtp-net.org (Arnaud Patard (Rtp))
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: iMX5 BBG: add cpuidle driver parameters
Date: Tue, 08 Feb 2011 18:24:57 +0100	[thread overview]
Message-ID: <87hbcev3py.fsf@lechat.rtp-net.org> (raw)
In-Reply-To: <20110208171635.GA12943@matterhorn.lan> (Amit Kucheria's message of "Tue, 8 Feb 2011 19:16:35 +0200")

Amit Kucheria <amit.kucheria@linaro.org> writes:

> On 11 Feb 08, Yong Shen wrote:
>> Hi Arnaud,
>> 
>> I also took a while to think about this before posting patches. I prefer to
>> put it in board related code since the various PMIC used on each boards may
>> have influence on cpuidle latency or other charactors, although it could be
>> minor.
>> 
>
> Then those minor differences can be addressed in the common driver by using #ifdef
> conditionals.
>
> The cpuidle driver certainly shouldn't be board-specific.

agreed, except on #ifdef. One should be able to build one kernel for
several imx51 boards and #ifdef will probably prevent that.

Arnaud

  reply	other threads:[~2011-02-08 17:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-08 15:14 [PATCH 0/2] cpuidle driver on iMX platform yong.shen at linaro.org
2011-02-08 15:14 ` [PATCH 1/2] ARM: iMX: cpuidle driver yong.shen at linaro.org
2011-02-08 15:14 ` [PATCH 2/2] ARM: iMX5 BBG: add cpuidle driver parameters yong.shen at linaro.org
2011-02-08 15:29   ` Arnaud Patard (Rtp)
2011-02-08 15:51     ` Yong Shen
2011-02-08 17:16       ` Amit Kucheria
2011-02-08 17:24         ` Arnaud Patard (Rtp) [this message]
2011-02-08 17:40           ` Amit Kucheria
2011-02-08 17:50       ` Rob Herring
2011-02-09  9:40         ` Yong Shen
2011-02-09 10:52       ` Vishwanath Sripathy
2011-02-09 11:19         ` Yong Shen

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=87hbcev3py.fsf@lechat.rtp-net.org \
    --to=arnaud.patard@rtp-net.org \
    --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).