From: Julien Grall <julien.grall@linaro.org>
To: vijay.kilari@gmail.com, Ian.Campbell@citrix.com,
stefano.stabellini@eu.citrix.com, stefano.stabellini@citrix.com,
xen-devel@lists.xen.org
Cc: Prasun.Kapoor@caviumnetworks.com, vijaya.kumar@caviumnetworks.com
Subject: Re: [PATCH] xen/arm: remove check for generic timer support for arm64
Date: Mon, 02 Jun 2014 12:06:33 +0100 [thread overview]
Message-ID: <538C5AB9.9070306@linaro.org> (raw)
In-Reply-To: <1401698241-20722-1-git-send-email-vijay.kilari@gmail.com>
Hi Vijay,
On 06/02/2014 09:37 AM, vijay.kilari@gmail.com wrote:
> From: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
>
> arm64 always supports generic timer. So check is not required
> for arm64. For platforms which supports only aarch64 mode this
> check always passes and panics
You should explain why it always panics... i.e On AArch-64 only
implementation, this register is RES0.
A link to the ARM ARM section might be also useful.
> Signed-off-by: Vijaya Kumar K <Vijaya.Kumar@caviumnetworks.com>
> ---
> xen/arch/arm/time.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/xen/arch/arm/time.c b/xen/arch/arm/time.c
> index 4c3e1a6..801c130 100644
> --- a/xen/arch/arm/time.c
> +++ b/xen/arch/arm/time.c
> @@ -138,8 +138,10 @@ int __init init_xen_time(void)
> panic("Timer: Cannot initialize platform timer");
>
> /* Check that this CPU supports the Generic Timer interface */
> +#ifdef CONFIG_ARM_32
With this solution, you don't check aarch32 generic timer support on an
ARMv8 host.
I think you have to do smth like:
if ( cpu_has_aarch32 && !cpu_has_gentimer )
> if ( !cpu_has_gentimer )
> panic("CPU does not support the Generic Timer v1 interface");
> +#endif
> res = dt_property_read_u32(dev, "clock-frequency", &rate);
> if ( res )
>
Regards,
--
Julien Grall
next prev parent reply other threads:[~2014-06-02 11:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 8:37 [PATCH] xen/arm: remove check for generic timer support for arm64 vijay.kilari
2014-06-02 11:06 ` Julien Grall [this message]
2014-06-02 11:09 ` Ian Campbell
2014-06-02 11:13 ` Julien Grall
2014-06-02 13:03 ` Ian Campbell
2014-06-02 13:23 ` Julien Grall
2014-06-02 13:30 ` Ian Campbell
2014-06-02 13:39 ` Julien Grall
2014-06-02 13:59 ` Vijay Kilari
2014-06-02 14:02 ` Ian Campbell
2014-06-02 14:08 ` Vijay Kilari
2014-06-02 14:11 ` Ian Campbell
2014-06-02 14:13 ` Julien Grall
2014-06-02 14:21 ` Ian Campbell
2014-06-02 14:10 ` Julien Grall
2014-06-02 14:12 ` Ian Campbell
2014-06-02 14:01 ` Ian Campbell
2014-06-02 14:48 ` Ian Campbell
2014-06-02 14:50 ` Julien Grall
2014-06-02 14:53 ` 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=538C5AB9.9070306@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=Prasun.Kapoor@caviumnetworks.com \
--cc=stefano.stabellini@citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=vijay.kilari@gmail.com \
--cc=vijaya.kumar@caviumnetworks.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.