All of lore.kernel.org
 help / color / mirror / Atom feed
From: Leo Yan <leoy@marvell.com>
To: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org
Subject: [Question] Verification For arm64: suspend/resume implementation
Date: Fri, 13 Sep 2013 10:53:53 +0800	[thread overview]
Message-ID: <52327E41.1070904@marvell.com> (raw)

hi Lorenzo,

I have applied your ARM64's suspend/resume related patches and can built 
successfully. i want to verify these patches on foundation model 
firstly, so below are my questions:

"Code has been tested on AEM v8 models and a simple CPU idle driver that 
enables a C-state where CPUs are reset when wfi is hit."

1. Can u help share this simple cpu idle driver?
2. On the foundation model, if the core is placed into reset state, then 
if there have interrupt is routed to the core, the core still cannot be 
waken up anymore; because the reset bit cannot be released by h/w. So 
how can let the core return back from the reset state?

-- 
Thx,
Leo Yan

WARNING: multiple messages have this Message-ID (diff)
From: leoy@marvell.com (Leo Yan)
To: linux-arm-kernel@lists.infradead.org
Subject: [Question] Verification For arm64: suspend/resume implementation
Date: Fri, 13 Sep 2013 10:53:53 +0800	[thread overview]
Message-ID: <52327E41.1070904@marvell.com> (raw)

hi Lorenzo,

I have applied your ARM64's suspend/resume related patches and can built 
successfully. i want to verify these patches on foundation model 
firstly, so below are my questions:

"Code has been tested on AEM v8 models and a simple CPU idle driver that 
enables a C-state where CPUs are reset when wfi is hit."

1. Can u help share this simple cpu idle driver?
2. On the foundation model, if the core is placed into reset state, then 
if there have interrupt is routed to the core, the core still cannot be 
waken up anymore; because the reset bit cannot be released by h/w. So 
how can let the core return back from the reset state?

-- 
Thx,
Leo Yan

             reply	other threads:[~2013-09-13  2:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13  2:53 Leo Yan [this message]
2013-09-13  2:53 ` [Question] Verification For arm64: suspend/resume implementation Leo Yan
2013-09-13  3:04 ` Jisheng Zhang
2013-09-13 14:40 ` Lorenzo Pieralisi
2013-09-13 14:40   ` Lorenzo Pieralisi
2013-09-23 11:11   ` Leo Yan
2013-09-23 11:11     ` Leo Yan
2013-09-23 15:26     ` Achin Gupta
2013-09-23 15:26       ` Achin Gupta
2013-09-24  2:00       ` Leo Yan
2013-09-24  2:00         ` Leo Yan
2013-09-24  9:02         ` Achin Gupta
2013-09-24  9:02           ` Achin Gupta
2013-09-24 11:49           ` Leo Yan
2013-09-24 11:49             ` Leo Yan
2013-09-24 13:00             ` Catalin Marinas
2013-09-24 13:00               ` Catalin Marinas
2013-09-26 11:12               ` Leo Yan
2013-09-26 11:12                 ` Leo Yan
2013-09-26 16:53                 ` Catalin Marinas
2013-09-26 16:53                   ` Catalin Marinas
2013-09-27  2:53                   ` Leo Yan
2013-09-27  2:53                     ` Leo Yan

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=52327E41.1070904@marvell.com \
    --to=leoy@marvell.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lorenzo.pieralisi@arm.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 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.