From: Ian Campbell <Ian.Campbell@citrix.com>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: keir@xen.org, ian.jackson@eu.citrix.com,
Julien Grall <julien.grall@linaro.org>, Tim Deegan <tim@xen.org>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Jan Beulich <jbeulich@suse.com>
Subject: Re: [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support
Date: Tue, 29 Jul 2014 18:36:56 +0100 [thread overview]
Message-ID: <1406655416.28644.45.camel@dagon.hellion.org.uk> (raw)
In-Reply-To: <CANoR_OBuFgJa1MHQEPHWZ7B5Rrb_+-KWc3nQWKedV52+HkLjhw@mail.gmail.com>
On Tue, 2014-07-29 at 08:49 -0700, Suriyan Ramasami wrote:
> On Tue, Jul 29, 2014 at 12:30 AM, Ian Campbell <Ian.Campbell@citrix.com> wrote:
> > On Mon, 2014-07-28 at 15:25 -0700, Suriyan Ramasami wrote:
> >> So, why is any other CPU other than CPU0 not able to read the CNTFRQ
> >> register? Is my CPU turn on code causing this issue, or is something
> >> extra needed to be done to the other CPUs in the bring up code?
> >
> > Are you sure you are writing CNTFRQ on every pCPU? This is a processor
> > local register so it needs setting everywhere, not just once.
> >
> Ah! I didn't know that. I was setting it only once on the booting CPU
> in u-boot through am smc call.
All cp registers are always local. At least I can't think of an
exception offhand.
> > You symptoms are sounding very much like it is only set on the boot CPU.
> >
> Thanks for pointing this out. I am wondering if I should go the psci
> route for the Exynos 5410 or add an smc call in the cpu bring up code.
PSCI would certainly be preferable if it is available for your platform.
A basic PSCI framework got added to u-boot mainline just this week, if
that is helpful.
Ian.
next prev parent reply other threads:[~2014-07-29 17:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 22:47 [ARM:PATCH v1 1/1] Add Odroid-XU (Exynos5410) support Suriyan Ramasami
2014-07-25 8:18 ` Ian Campbell
2014-07-25 12:19 ` Julien Grall
2014-07-25 12:39 ` Ian Campbell
2014-07-25 17:45 ` Suriyan Ramasami
2014-07-25 20:05 ` Ian Campbell
2014-07-26 0:06 ` Suriyan Ramasami
2014-07-26 7:26 ` Suriyan Ramasami
2014-07-26 11:28 ` Julien Grall
2014-07-26 16:02 ` Suriyan Ramasami
2014-07-26 17:58 ` Julien Grall
2014-07-26 20:26 ` Suriyan Ramasami
2014-07-26 21:24 ` Julien Grall
2014-07-26 21:26 ` Julien Grall
2014-07-27 18:12 ` Suriyan Ramasami
2014-07-28 12:53 ` Julien Grall
2014-07-28 18:06 ` Suriyan Ramasami
2014-07-28 20:19 ` Suriyan Ramasami
2014-07-28 22:25 ` Suriyan Ramasami
2014-07-29 7:30 ` Ian Campbell
2014-07-29 15:49 ` Suriyan Ramasami
2014-07-29 17:36 ` Ian Campbell [this message]
2014-08-12 19:05 ` 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=1406655416.28644.45.camel@dagon.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@linaro.org \
--cc=keir@xen.org \
--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 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).