Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Tony Lindgren <tony@atomide.com>,
	linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	Vaibhav Bedia <vaibhav.bedia@ti.com>
Subject: Re: [PATCH V3 5/7] ARM: OMAP3: Update clocksource timer selection
Date: Tue, 05 Feb 2013 10:39:27 +0200	[thread overview]
Message-ID: <5110C53F.1010203@compulab.co.il> (raw)
In-Reply-To: <1360007196-21350-6-git-send-email-jon-hunter@ti.com>

On 02/04/13 21:46, Jon Hunter wrote:
> When booting with device-tree for OMAP3 and AM335x devices and a gptimer
> is used as the clocksource (which is always the case for AM335x), a
> gptimer located in a power domain that is not always-on is selected.
> Ideally we should use a gptimer located in a power domain that is always
> on (such as the wake-up domain) so that time can be maintained during a
> kernel suspend without keeping on additional power domains unnecessarily.
> 
> In order to fix this so that we can select a gptimer located in a power
> domain that is always-on, the following changes were made ...
> 1. Currently, only when selecting a gptimer to use for a clockevent
>    timer, do we pass a timer property that can be used to select a
>    specific gptimer. Change this so that we can pass a property when
>    selecting a gptimer to use for a clocksource timer too.
> 2. Currently, when selecting either a gptimer to use for a clockevent
>    timer or a clocksource timer and no timer property is passed, then
>    the first available timer is selected regardless of the properties
>    it has. Change this so that if no properties are passed, then a timer
>    that does not have additional features (such as always-on, dsp-irq,
>    pwm, and secure) is selected.
> 
> Please note that using a gptimer for both clocksource and clockevents
> can have a system power impact during idle. The reason being is that
> OMAP and AMxxx devices typically only have one gptimer in a power domain
> that is always-on. Therefore when the kernel is idle both the clocksource
> and clockevent timers will be active and this will keep additional power
> domains on. During kernel suspend, only the clocksource timer is active
> and therefore, it is better to use a gptimer in a power domain that is
> always-on for clocksource.

Hmmm...
Do I miss something or you have forgot to update the commit message?

> 
> Signed-off-by: Jon Hunter <jon-hunter@ti.com>
> ---
>  arch/arm/mach-omap2/timer.c |   33 +++++++++++++++++++++------------
>  1 file changed, 21 insertions(+), 12 deletions(-)

[...]

>  #if defined(CONFIG_ARCH_OMAP3) || defined(CONFIG_SOC_AM33XX)
> -OMAP_SYS_GP_TIMER_INIT(3, 1, "timer_sys_ck", "ti,timer-alwon",
> -		       2, "timer_sys_ck");
> +OMAP_SYS_GP_TIMER_INIT(3, 2, "timer_sys_ck", NULL,
> +		       1, "timer_sys_ck", "ti,timer-alwon");
>  #endif

[...]


-- 
Regards,
Igor.

  reply	other threads:[~2013-02-05  8:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04 19:46 [PATCH V3 0/7] ARM: OMAP2+: System timer updates Jon Hunter
2013-02-04 19:46 ` [PATCH V3 1/7] ARM: OMAP2+: Display correct system timer name Jon Hunter
2013-02-04 19:46 ` [PATCH V3 2/7] ARM: OMAP2+: Remove hard-coded test on timer ID Jon Hunter
2013-02-04 19:46 ` [PATCH V3 3/7] ARM: OMAP2+: Simplify system timer clock definitions Jon Hunter
2013-02-04 19:46 ` [PATCH V3 4/7] ARM: OMAP2+: Simplify system timers definitions Jon Hunter
2013-02-04 19:46 ` [PATCH V3 5/7] ARM: OMAP3: Update clocksource timer selection Jon Hunter
2013-02-05  8:39   ` Igor Grinberg [this message]
2013-02-05 16:49     ` Jon Hunter
2013-02-05 17:10       ` Igor Grinberg
2013-02-04 19:46 ` [PATCH V3 6/7] ARM: OMAP2+: Store ID of system timers in timer structure Jon Hunter
2013-02-04 19:46 ` [PATCH V3 7/7] ARM: OMAP4+: Fix sparse warning in system timers Jon Hunter

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=5110C53F.1010203@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.com \
    --cc=vaibhav.bedia@ti.com \
    /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