linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: York Sun <yorksun@freescale.com>
To: Dongsheng Wang <dongsheng.wang@freescale.com>,
	<scottwood@freescale.com>, <leoli@freescale.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] fsl/smp: add low power boot support to replace spin boot
Date: Thu, 15 Jan 2015 09:08:36 -0800	[thread overview]
Message-ID: <54B7F414.2020609@freescale.com> (raw)
In-Reply-To: <1421301930-10035-1-git-send-email-dongsheng.wang@freescale.com>



On 01/14/2015 10:05 PM, Dongsheng Wang wrote:
> From: Wang Dongsheng <dongsheng.wang@freescale.com>
> 
> U-boot put non-boot cpus into an low power state(PW10/PW20 or DOZE) when cpu
> powered up. To exit low power state kernel will send DOORBELL or MPIC-IPI
> signal to all those CPUs.
> 
> e500/e500v2 use mpic to send IPI signal.
> e500mc and later use doorbell to send IPI signal.
> 
> This feature tested on:
> POWER UP TEST:
> P1022DS(e500v2),96k times.
> P4080(e500mc),  110k times.
> T1024(e5500),   83k times.
> T4240(e6500),   150k times.
> 
> CPU HOTPLUG TEST:
> P1022DS(e500v2),1.4 million times.
> P4080(e500mc),  1.8 million times.
> T1024(e5500),   1.3 million times.
> T4240(e6500),   1.1 million times.
> 
> Signed-off-by: Wang Dongsheng <dongsheng.wang@freescale.com>
> 

This is a very good move. Can you explain what has been tested for 100K times,
or over a million times?

Have you verified on older e500v2 platforms, such as MPC8572?

York

  parent reply	other threads:[~2015-01-15 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-15  6:05 [PATCH] fsl/smp: add low power boot support to replace spin boot Dongsheng Wang
2015-01-15  6:46 ` Dongsheng.Wang
2015-01-15 17:08 ` York Sun [this message]
2015-01-16  2:49   ` Dongsheng.Wang
2015-01-20  0:46 ` Scott Wood

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=54B7F414.2020609@freescale.com \
    --to=yorksun@freescale.com \
    --cc=dongsheng.wang@freescale.com \
    --cc=leoli@freescale.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).