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: Mon, 23 Apr 2012 08:56:23 +0200 [thread overview]
Message-ID: <20120423065623.GA3852@pengutronix.de> (raw)
In-Reply-To: <20120423065259.GR26306@S2101-09.ap.freescale.net>
On Mon, Apr 23, 2012 at 02:53:01PM +0800, Shawn Guo wrote:
> On Mon, Apr 23, 2012 at 08:27:39AM +0200, Sascha Hauer wrote:
> > On Mon, Apr 23, 2012 at 01:18:21PM +0800, Shawn Guo wrote:
> > > On Sun, Apr 22, 2012 at 11:44:39PM -0500, Rob Lee wrote:
> > > > >> 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?
> > > > >>
> > > > > Yep, it works for me.
> > > > >
> > > > Sascha, Shawn, thanks for the response.
> > > >
> > > > Since device_initcall isn't platform specific, it seems I would still
> > > > need a cpu_is_imx6q() function or similiar functionality from a device
> > > > tree call. Or do you have something else in mind that I'm not seeing?
> > > >
> > > I guess Sascha is asking for something like the following.
> > >
> > > static int __init imx_device_init(void)
> > > {
> > > imx5_device_init();
> > > imx6_device_init();
> > > }
> > > device_initcall(imx_device_init)
> > >
> > > static int __init imx6_device_init(void)
> > > {
> > > /*
> > > * do whatever needs to get done in device_initcall time
> > > */
> > > }
> >
> > The problem is more how we can detect that we are actually running a
> > i.MX6 SoC. We could directly ask the devicetree in an initcall or we
> > could introduce a cpu_is_mx6() just like we have a macro for all other
> > i.MX SoCs.
> >
> Oops, my reply was a brain-dead one. Hmm, then it seems that we have
> to introduce cpu_is_mx6() which I tried hard to avoid. I do not have
> a preference between defining a macro and asking device tree.
Since we already have a place in early setup code in which we know that
we are running on an i.MX6 I suggest for the sake of the symmetry of the
universe that we introduce a cpu_is_mx6.
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 |
WARNING: multiple messages have this Message-ID (diff)
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Rob Lee <rob.lee@linaro.org>,
Amit Kucheria <amit.kucheria@linaro.org>,
kernel@pengutronix.de, linaro-dev@lists.linaro.org,
patches@linaro.org, daniel.lezcano@linaro.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality.
Date: Mon, 23 Apr 2012 08:56:23 +0200 [thread overview]
Message-ID: <20120423065623.GA3852@pengutronix.de> (raw)
In-Reply-To: <20120423065259.GR26306@S2101-09.ap.freescale.net>
On Mon, Apr 23, 2012 at 02:53:01PM +0800, Shawn Guo wrote:
> On Mon, Apr 23, 2012 at 08:27:39AM +0200, Sascha Hauer wrote:
> > On Mon, Apr 23, 2012 at 01:18:21PM +0800, Shawn Guo wrote:
> > > On Sun, Apr 22, 2012 at 11:44:39PM -0500, Rob Lee wrote:
> > > > >> 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?
> > > > >>
> > > > > Yep, it works for me.
> > > > >
> > > > Sascha, Shawn, thanks for the response.
> > > >
> > > > Since device_initcall isn't platform specific, it seems I would still
> > > > need a cpu_is_imx6q() function or similiar functionality from a device
> > > > tree call. Or do you have something else in mind that I'm not seeing?
> > > >
> > > I guess Sascha is asking for something like the following.
> > >
> > > static int __init imx_device_init(void)
> > > {
> > > imx5_device_init();
> > > imx6_device_init();
> > > }
> > > device_initcall(imx_device_init)
> > >
> > > static int __init imx6_device_init(void)
> > > {
> > > /*
> > > * do whatever needs to get done in device_initcall time
> > > */
> > > }
> >
> > The problem is more how we can detect that we are actually running a
> > i.MX6 SoC. We could directly ask the devicetree in an initcall or we
> > could introduce a cpu_is_mx6() just like we have a macro for all other
> > i.MX SoCs.
> >
> Oops, my reply was a brain-dead one. Hmm, then it seems that we have
> to introduce cpu_is_mx6() which I tried hard to avoid. I do not have
> a preference between defining a macro and asking device tree.
Since we already have a place in early setup code in which we know that
we are running on an i.MX6 I suggest for the sake of the symmetry of the
universe that we introduce a cpu_is_mx6.
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 |
next prev parent reply other threads:[~2012-04-23 6:56 UTC|newest]
Thread overview: 56+ 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 ` Robert Lee
2012-04-16 23:50 ` [PATCH 1/3] ARM: imx: Add common imx cpuidle init functionality Robert Lee
2012-04-16 23:50 ` Robert Lee
2012-04-16 23:56 ` Jesper Juhl
2012-04-16 23:56 ` Jesper Juhl
2012-04-17 7:43 ` Sascha Hauer
2012-04-17 7:43 ` Sascha Hauer
2012-04-17 13:54 ` Rob Lee
2012-04-17 13:54 ` Rob Lee
2012-04-17 14:13 ` Christian Robottom Reis
2012-04-17 14:13 ` Christian Robottom Reis
2012-04-17 14:32 ` Rob Lee
2012-04-17 14:32 ` Rob Lee
2012-04-17 17:42 ` Sascha Hauer
2012-04-17 17:42 ` Sascha Hauer
2012-04-17 19:32 ` Rob Lee
2012-04-17 19:32 ` Rob Lee
2012-04-19 4:18 ` Rob Lee
2012-04-19 4:18 ` Rob Lee
2012-04-19 6:43 ` Sascha Hauer
2012-04-19 6:43 ` Sascha Hauer
2012-04-20 2:08 ` Shawn Guo
2012-04-20 2:08 ` Shawn Guo
2012-04-23 4:44 ` Rob Lee
2012-04-23 4:44 ` Rob Lee
2012-04-23 5:18 ` Shawn Guo
2012-04-23 5:18 ` Shawn Guo
2012-04-23 6:27 ` Sascha Hauer
2012-04-23 6:27 ` Sascha Hauer
2012-04-23 6:53 ` Shawn Guo
2012-04-23 6:53 ` Shawn Guo
2012-04-23 6:56 ` Sascha Hauer [this message]
2012-04-23 6:56 ` Sascha Hauer
2012-04-23 7:10 ` Shawn Guo
2012-04-23 7:10 ` Shawn Guo
2012-04-23 7:48 ` Sascha Hauer
2012-04-23 7:48 ` Sascha Hauer
2012-04-23 15:45 ` Rob Lee
2012-04-23 15:45 ` Rob Lee
2012-04-24 1:38 ` Shawn Guo
2012-04-24 1:38 ` Shawn Guo
2012-04-24 7:54 ` Russell King - ARM Linux
2012-04-24 7:54 ` Russell King - ARM Linux
2012-04-24 8:36 ` Shawn Guo
2012-04-24 8:36 ` Shawn Guo
2012-04-24 15:40 ` Rob Lee
2012-04-24 15:40 ` Rob Lee
2012-04-24 19:51 ` Russell King - ARM Linux
2012-04-24 19:51 ` Russell King - ARM Linux
2012-04-25 2:06 ` Shawn Guo
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 ` Robert Lee
2012-04-16 23:50 ` [PATCH 3/3] ARM: imx: Add imx6q " Robert Lee
2012-04-16 23:50 ` 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=20120423065623.GA3852@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 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.