From: Julien Grall <julien.grall@linaro.org>
To: Suriyan Ramasami <suriyan.r@gmail.com>
Cc: Ian Campbell <ian.campbell@citrix.com>, xen-devel@lists.xen.org
Subject: Re: ARM: EXYNOS 5410 - DOM0 not being scheduled
Date: Mon, 17 Mar 2014 22:15:37 +0000 [thread overview]
Message-ID: <53277409.7010900@linaro.org> (raw)
In-Reply-To: <CANoR_OBOny52hw0TRr3JoaRiC_Q_zw42wiYzz4qt_RxVNnehCg@mail.gmail.com>
On 17/03/14 18:22, Suriyan Ramasami wrote:
> Hello Julien and Ian,
Hello Suriyan,
> You can tell that I am just so excited! So, I did get dom0 to run now!
great ! Thank you for the log and dig into this issue.
> For the moment I just hardcoded arch_timer_rate to 24000000 in
> drivers/clocksource/arm_arch_timer.c and dom0 boots up!
I'm not sure what you meant by hardcoding, how did you do it?
> So, now it remains, what is the right way to do the correction:
> 1. no dom0 output
Already answer to it on a previous mail :).
> 2. arch_timer_rate coming up as 0 in dom0 inspite of the dtb defining
> clock-frequency.
The clock-frequency properties is not given to dom0. It should be able
to retrieve the frequency from the timer (CNTFRQ). That would mean that
u-boot is not correctly set up the frequency (it's the only one able to
do it as it need to be done in secure world).
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-03-17 22:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 14:44 ARM: EXYNOS 5410 - DOM0 not being scheduled Suriyan Ramasami
2014-03-16 20:31 ` Julien Grall
2014-03-17 13:17 ` Suriyan Ramasami
2014-03-17 13:21 ` Julien Grall
2014-03-17 13:32 ` Suriyan Ramasami
2014-03-17 13:52 ` Julien Grall
2014-03-17 17:39 ` Suriyan Ramasami
2014-03-17 18:10 ` Suriyan Ramasami
2014-03-17 18:22 ` Suriyan Ramasami
2014-03-17 22:15 ` Julien Grall [this message]
2014-03-18 9:52 ` Ian Campbell
2014-03-18 12:04 ` Julien Grall
2014-03-18 13:37 ` Ian Campbell
2014-03-18 15:41 ` Suriyan Ramasami
2014-03-18 16:09 ` Julien Grall
2014-03-17 22:03 ` Julien Grall
2014-03-17 10:09 ` Ian Campbell
2014-03-17 13:24 ` Suriyan Ramasami
2014-03-17 13:36 ` Ian Campbell
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=53277409.7010900@linaro.org \
--to=julien.grall@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=suriyan.r@gmail.com \
--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.