From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Grall Subject: Re: ARM: EXYNOS 5410 - DOM0 not being scheduled Date: Mon, 17 Mar 2014 22:15:37 +0000 Message-ID: <53277409.7010900@linaro.org> References: <53260A3D.5080202@citrix.com> <5326F6CC.3060303@linaro.org> <5326FE1B.3080800@linaro.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Suriyan Ramasami Cc: Ian Campbell , xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org 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