linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lorenzo.pieralisi@arm.com (Lorenzo Pieralisi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] ARM: tegra: cpuidle: implement cpuidle_state.enter_freeze()
Date: Wed, 20 May 2015 10:04:55 +0100	[thread overview]
Message-ID: <20150520090455.GC29274@red-moon> (raw)
In-Reply-To: <555C4C0D.4040605@collabora.com>

On Wed, May 20, 2015 at 09:55:41AM +0100, Tomeu Vizoso wrote:
> On 05/20/2015 10:44 AM, Lorenzo Pieralisi wrote:
> > On Tue, May 19, 2015 at 03:49:12PM +0100, Tomeu Vizoso wrote:
> >> This callback is expected to do the same as enter() but it has to
> >> guarantee that interrupts aren't enabled at any point in its execution,
> >> as the tick is frozen.
> >>
> >> It will be called when the system goes to suspend-to-idle and will
> >> reduce power usage because CPUs won't be awaken for unnecessary IRQs.
> >>
> >> By setting the CPUIDLE_FLAG_TIMER_STOP flag, we can reuse the same code
> >> for both the enter() and enter_freeze() callbacks.
> >>
> >> Signed-off-by: Tomeu Vizoso <tomeu.vizoso@collabora.com>
> >> Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
> >>
> >> ---
> >>
> >> v3:	* Set CPUIDLE_FLAG_TIMER_STOP to simplify things as suggested by
> >> 	Lorenzo Pieralisi
> >> v2:	* Disable FIQs also when suspending-to-idle
> >> ---
> >>  arch/arm/mach-tegra/cpuidle-tegra114.c | 13 +++++++++----
> >>  1 file changed, 9 insertions(+), 4 deletions(-)
> >>
> >> diff --git a/arch/arm/mach-tegra/cpuidle-tegra114.c b/arch/arm/mach-tegra/cpuidle-tegra114.c
> >> index 155807f..7e59ac0 100644
> >> --- a/arch/arm/mach-tegra/cpuidle-tegra114.c
> >> +++ b/arch/arm/mach-tegra/cpuidle-tegra114.c
> >> @@ -44,16 +44,12 @@ static int tegra114_idle_power_down(struct cpuidle_device *dev,
> >>  	tegra_set_cpu_in_lp2();
> >>  	cpu_pm_enter();
> >>  
> >> -	tick_broadcast_enter();
> >> -
> >>  	call_firmware_op(prepare_idle);
> >>  
> >>  	/* Do suspend by ourselves if the firmware does not implement it */
> >>  	if (call_firmware_op(do_idle, 0) == -ENOSYS)
> >>  		cpu_suspend(0, tegra30_sleep_cpu_secondary_finish);
> >>  
> >> -	tick_broadcast_exit();
> >> -
> >>  	cpu_pm_exit();
> >>  	tegra_clear_cpu_in_lp2();
> >>  
> >> @@ -61,6 +57,13 @@ static int tegra114_idle_power_down(struct cpuidle_device *dev,
> >>  
> >>  	return index;
> >>  }
> >> +
> >> +static void tegra114_idle_enter_freeze(struct cpuidle_device *dev,
> >> +				       struct cpuidle_driver *drv,
> >> +				       int index)
> >> +{
> >> +       tegra114_idle_power_down(dev, drv, index);
> >> +}
> > 
> > You do not need this function, remove it and update the enter_freeze
> > pointer below with tegra114_idle_power_down please.
> 
> How so? The callbacks have different signatures.

Sorry, glossed over it, never mind.

Lorenzo

  reply	other threads:[~2015-05-20  9:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 14:49 [PATCH v3] ARM: tegra: cpuidle: implement cpuidle_state.enter_freeze() Tomeu Vizoso
2015-05-20  8:44 ` Lorenzo Pieralisi
2015-05-20  8:55   ` Tomeu Vizoso
2015-05-20  9:04     ` Lorenzo Pieralisi [this message]
2015-05-21  1:02 ` Rafael J. Wysocki
2015-06-18  7:09   ` Tomeu Vizoso
2015-06-29  9:00     ` Thierry Reding
2015-06-29  9:18       ` Tomeu Vizoso
2015-08-13 14:54 ` Thierry Reding

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=20150520090455.GC29274@red-moon \
    --to=lorenzo.pieralisi@arm.com \
    --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).