From: Sascha Hauer <s.hauer@pengutronix.de>
To: Rob Lee <rob.lee@linaro.org>
Cc: kernel@pengutronix.de, shawn.guo@linaro.org,
amit.kucheria@linaro.org, daniel.lezcano@linaro.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
patches@linaro.org, jj@chaosbits.net
Subject: Re: [PATCH v3 2/3] ARM: imx: Add imx5 cpuidle driver
Date: Thu, 10 May 2012 14:41:30 +0200 [thread overview]
Message-ID: <20120510124130.GS27341@pengutronix.de> (raw)
In-Reply-To: <CAMXH7KF7eznzF7AzM_JzwJ1jOm-1J4biqd=PvKMSa=ex8YFQrA@mail.gmail.com>
On Wed, May 09, 2012 at 09:27:02AM -0500, Rob Lee wrote:
> Sascha,
>
> >
> > This clk_get should go away here and be moved somewhere to
> > initialization. Also, if getting this clock fails we can still
> > do regular cpu_do_idle. Additionally, if clk_get fails, we'll
> > have a ERR_PTR value in gpc_dvfs_clk in which case the
> > gpc_dvfs_clk == NULL won't trigger next time you are here and
> > then you'll enable a nonexisting clock below.
> >
>
> Agree. I'd prefer to enable this clock during intialization and just
> leave it running. It is supposed to be a very low power clock and I
> couldn't measuring any power difference with and without it being
> enabled
Ok, even better.
> >
> > I wonder why you don't add the default ARM_CPUIDLE_WFI_STATE_PWR state.
> > The above is something different, right? It has a greater exit latency
> > than ARM_CPUIDLE_WFI_STATE_PWR, so why don't we add it here aswell?
>
> Yes and no. Yes this is a different state but no, it doesn't have a
> significantly greater exit latency, or at least a large enough exit
> latency to warrant an extra state in my opinion. According to the
> i.MX5 documentation, the extra exit time beyond basic WFI required for
> the "WAIT_UNCLOCKED_POWER_OFF" state is 500ns (this is due to a
> difference in i.MX5 hardware implementation compared to all other ARM
> platforms). In reality, it did require a few more microseconds to
> perform in my testing just based on the extra register writes in
> mx5_cpu_lp_set(). I'd like to clean up mx5_cpu_lp_set() and add a
> global variable to track the previous state and to just exit out if
> the new state is the same as the old.
Do you think it's worth it? You buy skipping the read with an additional
test.
> I could do this cleanup as part of this patchset if you prefer that.
Yes please. Cleanups before adding new features is always a good reason
to apply a patch series ;)
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-05-10 12:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 21:16 [PATCH v3 0/3] Add imx cpuidle Robert Lee
2012-05-07 21:16 ` [PATCH v3 1/3] ARM: imx: Add common imx cpuidle init functionality Robert Lee
2012-05-07 21:16 ` [PATCH v3 2/3] ARM: imx: Add imx5 cpuidle driver Robert Lee
2012-05-09 8:02 ` Sascha Hauer
2012-05-09 14:27 ` Rob Lee
2012-05-10 12:41 ` Sascha Hauer [this message]
2012-05-10 14:10 ` Rob Lee
2012-05-07 21:16 ` [PATCH v3 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=20120510124130.GS27341@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=amit.kucheria@linaro.org \
--cc=daniel.lezcano@linaro.org \
--cc=jj@chaosbits.net \
--cc=kernel@pengutronix.de \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
--cc=rob.lee@linaro.org \
--cc=shawn.guo@linaro.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).