From: Julien Grall <julien.grall@citrix.com>
To: "Chris (Christopher) Brand" <chris.brand@broadcom.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "stefano.stabellini@citrix.com" <stefano.stabellini@citrix.com>,
"wei.liu2@citrix.com" <wei.liu2@citrix.com>,
"ian.jackson@eu.citrix.com" <ian.jackson@eu.citrix.com>,
"ian.campbell@citrix.com" <ian.campbell@citrix.com>,
"tim@xen.org" <tim@xen.org>
Subject: Re: [PATCH] xen/arm: Propagate clock-frequency to DOMU if present in the DT timer node
Date: Fri, 12 Jun 2015 07:42:49 -0400 [thread overview]
Message-ID: <557AC5B9.7030200@citrix.com> (raw)
In-Reply-To: <4EE5B48738DDED408878C97C8E050A8B1D7A71B7@SJEXCHMB05.corp.ad.broadcom.com>
On 11/06/2015 17:43, Chris (Christopher) Brand wrote:
> Hi Julien,
Hi Chris,
> The patch does work exactly as advertised.
>
> When I used dtc to convert CONFIG_DTB_FILE from dtb to dts, I could see that it didn't in fact have a timer clock-frequency node. After re-creating the dtb and rebuilding Xen, "ls /proc/device-tree/timer/" shows a clock-frequency file. When I then fire up DomU and do the same command, it too has a clock-frequency node.
Can I get your Tested-by on this patch?
Regards,
--
Julien Grall
next prev parent reply other threads:[~2015-06-12 11:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 14:48 [PATCH] xen/arm: Propagate clock-frequency to DOMU if present in the DT timer node Julien Grall
2015-06-03 22:45 ` Chris (Christopher) Brand
2015-06-03 23:24 ` Julien Grall
2015-06-05 20:14 ` Chris (Christopher) Brand
2015-06-07 21:04 ` Julien Grall
2015-06-08 20:44 ` Chris (Christopher) Brand
2015-06-09 23:48 ` Julien Grall
2015-06-10 17:42 ` Julien Grall
2015-06-10 21:41 ` Chris (Christopher) Brand
2015-06-11 21:43 ` Chris (Christopher) Brand
2015-06-12 11:42 ` Julien Grall [this message]
2015-06-12 15:16 ` Chris (Christopher) Brand
2015-06-17 10:57 ` Ian Campbell
2015-06-17 12:49 ` Julien Grall
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=557AC5B9.7030200@citrix.com \
--to=julien.grall@citrix.com \
--cc=chris.brand@broadcom.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=stefano.stabellini@citrix.com \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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.