From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Ian Campbell <Ian.Campbell@citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [ARM:PATCH v2 1/1] Pass the timer clock-frequency to DOM0
Date: Sun, 13 Apr 2014 22:40:45 +0100 [thread overview]
Message-ID: <534B045D.4080409@linaro.org> (raw)
In-Reply-To: <CANoR_OAppWXxjPqeb99R1NZt4Zd6oOCRGe3Z_QT2YtXFpJeKSQ@mail.gmail.com>
On 13/04/14 21:48, Suriyan Ramasami wrote:
> On Sun, Apr 13, 2014 at 1:20 PM, Julien Grall <julien.grall@linaro.org> wrote:
> fanta's patch to get the CPU up in NS HYP mode is in hardkernel's git
> repository ->
> https://github.com/hardkernel/u-boot/commit/56e5bdcb95d41f9236554de0578b0017a9f232a5
>
> Hence, it would appear that the SPL BL2 code is entered in NS HYP mode.
>
> Also, BL1 I believe is signed and encrypted - hence no access. BL2 can
> be signed and that is how currently we are entering in NS HYP.
Thanks for the explanation.
By any chance, do you know if the Arndale octa (exynos 5420) also bring
CPU in HYP mode the same way?
> Apparently the tzsw can be signed too, and hence, I was thinking of
> modifying a current smc call to have it set the CNTFRQ, which I
> believe will be in monitor mode.
We had the same issue on the Arndale last year. Luckily u-boot were
booting in Secure mode.
It would be great to have a firmware that correctly configure the Arch
timer (according the ARM ARM). But I bet the Arndale octa will have the
same issue. So we will have to handle this such configuration in Xen.
Can you send a new version with remarks make previously?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-04-13 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-27 3:54 [ARM:PATCH v2 1/1] Pass the timer clock-frequency to DOM0 Suriyan Ramasami
2014-03-27 21:48 ` Julien Grall
2014-03-27 22:16 ` Suriyan Ramasami
2014-03-28 14:04 ` Julien Grall
2014-04-01 11:12 ` Ian Campbell
2014-04-11 16:05 ` Suriyan Ramasami
2014-04-11 16:32 ` Julien Grall
2014-04-13 19:28 ` Suriyan Ramasami
2014-04-13 20:20 ` Julien Grall
2014-04-13 20:48 ` Suriyan Ramasami
2014-04-13 21:40 ` Julien Grall [this message]
2014-04-13 22:55 ` Suriyan Ramasami
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=534B045D.4080409@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=suriyan.r@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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 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.