All of lore.kernel.org
 help / color / mirror / Atom feed
From: daniel.lezcano@linaro.org (Daniel Lezcano)
To: linux-arm-kernel@lists.infradead.org
Subject: IMX: board hardware macro
Date: Wed, 27 Mar 2013 14:53:26 +0100	[thread overview]
Message-ID: <5152F9D6.1010500@linaro.org> (raw)
In-Reply-To: <20130327123359.GD2674@S2101-09.ap.freescale.net>

On 03/27/2013 01:34 PM, Shawn Guo wrote:
> On Wed, Mar 27, 2013 at 10:13:17AM +0100, Daniel Lezcano wrote:
>> Do these macros exist ?
> 
> There is cpu_is_mx51(), but no cpu_is_mx6() stuff.  I do not understand
> why these are needed.  The cpuidle initialization should be done in SoC
> specific hook like how it's done for imx6q right now.  So why do you
> need such macros?

Well I am sure that will fit, but I wanted to create a single cpuidle
init function for all the platforms in order to encapsulate the cpuidle
drivers and then with the incoming patchset, factor out the code.

I will send a RFC for the changes, so we can discuss about it and choose
the direction you think more convenient to unify the code across the
different cpuidle drivers.

Thanks
  -- Daniel


-- 
 <http://www.linaro.org/> Linaro.org ? Open source software for ARM SoCs

Follow Linaro:  <http://www.facebook.com/pages/Linaro> Facebook |
<http://twitter.com/#!/linaroorg> Twitter |
<http://www.linaro.org/linaro-blog/> Blog

      reply	other threads:[~2013-03-27 13:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-26 22:31 IMX: board hardware macro Daniel Lezcano
2013-03-27  6:33 ` Shawn Guo
2013-03-27  9:13   ` Daniel Lezcano
2013-03-27 12:34     ` Shawn Guo
2013-03-27 13:53       ` Daniel Lezcano [this message]

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=5152F9D6.1010500@linaro.org \
    --to=daniel.lezcano@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.