From: Leo Yan <leoy@marvell.com>
To: Achin Gupta <achin.gupta@arm.com>
Cc: Lorenzo Pieralisi <Lorenzo.Pieralisi@arm.com>,
Yu Tang <ytang5@marvell.com>, Zhou Zhu <zzhu3@marvell.com>,
Neil Zhang <zhangwm@marvell.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: [Question] Verification For arm64: suspend/resume implementation
Date: Tue, 24 Sep 2013 10:00:38 +0800 [thread overview]
Message-ID: <5240F246.6050402@marvell.com> (raw)
In-Reply-To: <20130923152606.GA6157@e102648.cambridge.arm.com>
On 09/23/2013 11:26 PM, Achin Gupta wrote:
> The foundation model (if thats what you are using) does not model an
> ARM cpu implementation. The CPUECTLR is a cpu specific register
> (imp. def.) so it is not present. The caches on the Foundation Model
> are inherently coherent so you do not need to access this register. If
> you do then the access is treated as an illegal instruction.
>
Thx for the info. So do u mean i need use FVP Model for A53?
Here have another question, ARM have the example code for boot wrapper
which will switch from EL3 to secure EL1 rather than non-secure's EL1?
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: Tue, 24 Sep 2013 10:00:38 +0800 [thread overview]
Message-ID: <5240F246.6050402@marvell.com> (raw)
In-Reply-To: <20130923152606.GA6157@e102648.cambridge.arm.com>
On 09/23/2013 11:26 PM, Achin Gupta wrote:
> The foundation model (if thats what you are using) does not model an
> ARM cpu implementation. The CPUECTLR is a cpu specific register
> (imp. def.) so it is not present. The caches on the Foundation Model
> are inherently coherent so you do not need to access this register. If
> you do then the access is treated as an illegal instruction.
>
Thx for the info. So do u mean i need use FVP Model for A53?
Here have another question, ARM have the example code for boot wrapper
which will switch from EL3 to secure EL1 rather than non-secure's EL1?
Thx,
Leo Yan
next prev parent reply other threads:[~2013-09-24 2:01 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 2:53 [Question] Verification For arm64: suspend/resume implementation Leo Yan
2013-09-13 2:53 ` 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 [this message]
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=5240F246.6050402@marvell.com \
--to=leoy@marvell.com \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=achin.gupta@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=ytang5@marvell.com \
--cc=zhangwm@marvell.com \
--cc=zzhu3@marvell.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.