linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality.
Date: Thu, 19 Apr 2012 08:43:08 +0200	[thread overview]
Message-ID: <20120419064308.GH3852@pengutronix.de> (raw)
In-Reply-To: <CAMXH7KGgSmvfqUTC1bufBz0QXbt01dHsPo1cbRA9jLj9mGmfjg@mail.gmail.com>

On Wed, Apr 18, 2012 at 11:18:55PM -0500, Rob Lee wrote:
> >>> If I called imx_cpuidle_init directly from imx5 or imx6q init
> >>> routines, it would be getting called before the coreinit_call of core
> >>> cpuidle causing a failure. ?There were various other directions to
> >>> take and all seemed less desirable than this one.
> >>>
> >>> One alternative would be to add a function to return the pointer to
> >>> the cpuidle driver object based on the machine type. ?Functionality
> >>> exists to identify imx5 as a machine type but not imx6q, so I couldn't
> >>> use that machine based method without adding that extra code.
> >>>
> >>> Another alternative would be to add a general platform lateinit_call
> >>> function to each platforms that support cpuidle.
> >>
> >> Just put the initcall into mm-imx5.c and check the cpu type. Then you
> >> also don't have to make imx5_idle global.
> >
> > That solution is currently available for imx5 but for imx6q it implies
> > adding the cpu type support for imx6q. ?Are you ok with that?
> 
> Sascha or Shawn, any further comments on my question?

I don't think we need a cpu_is_imx6q(), but having some i.MX6 specific
hook at device_initcall time can't be too wrong. Shawn?

Sascha


-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2012-04-19  6:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 23:50 [PATCH 0/3] Add imx cpuidle Robert Lee
2012-04-16 23:50 ` [PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality Robert Lee
2012-04-16 23:56   ` Jesper Juhl
2012-04-17  7:43   ` Sascha Hauer
2012-04-17 13:54     ` Rob Lee
2012-04-17 14:13       ` Christian Robottom Reis
2012-04-17 14:32         ` Rob Lee
2012-04-17 17:42       ` Sascha Hauer
2012-04-17 19:32         ` Rob Lee
2012-04-19  4:18           ` Rob Lee
2012-04-19  6:43             ` Sascha Hauer [this message]
2012-04-20  2:08               ` Shawn Guo
2012-04-23  4:44                 ` Rob Lee
2012-04-23  5:18                   ` Shawn Guo
2012-04-23  6:27                     ` Sascha Hauer
2012-04-23  6:53                       ` Shawn Guo
2012-04-23  6:56                         ` Sascha Hauer
2012-04-23  7:10                           ` Shawn Guo
2012-04-23  7:48                             ` Sascha Hauer
2012-04-23 15:45                               ` Rob Lee
2012-04-24  1:38                                 ` Shawn Guo
2012-04-24  7:54                                   ` Russell King - ARM Linux
2012-04-24  8:36                                     ` Shawn Guo
2012-04-24 15:40                                       ` Rob Lee
2012-04-24 19:51                                         ` Russell King - ARM Linux
2012-04-25  2:06                                           ` Shawn Guo
2012-04-16 23:50 ` [PATCH 2/3] ARM: imx: Add imx5 cpuidle driver Robert Lee
2012-04-16 23:50 ` [PATCH 3/3] ARM: imx: Add imx6q " Robert Lee

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=20120419064308.GH3852@pengutronix.de \
    --to=s.hauer@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).