From: David Gibson <david@gibson.dropbear.id.au>
To: alarson@ddci.com
Cc: agraf@suse.de, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [Qemu-devel] Subject: [PATCH] target-ppc: Add global timer group A to open-pic.
Date: Wed, 3 May 2017 15:14:52 +1000 [thread overview]
Message-ID: <20170503051452.GL10741@umbus.fritz.box> (raw)
In-Reply-To: <OF2ACF2223.8C7339DB-ON86258115.000819F0-86258115.0008E549@ddci.com>
[-- Attachment #1: Type: text/plain, Size: 1202 bytes --]
On Tue, May 02, 2017 at 08:37:09PM -0500, alarson@ddci.com wrote:
> David Gibson <david@gibson.dropbear.id.au> wrote on 04/25/2017 11:34:41
> PM:
>
> Thanks for the review David. I'll send an updated patch soon with all
> your comments addressed and all other s/0/NULL or false/ as
> appropriate and a better commit message.
>
> Just to clarify my concern; the patch causes the QEMU openpic timer to
> be hard coded at 100MHZ. This is common, but the openpic spec has
> numerous ways the clock could be driven and the actual frequency
> depends on target board configuration. Given that no other users are
> apparently using the QEMU openpic timer, it is probably ok, but I did
> want to point out the deficiency.
Ah, ok. The usual way to handle this is to have the frequency as a
property on the device. The board code which constructs the openPIC
value can then set it to the appropriate value.
Having an interim step where its hardcoded to 100 MHz is perfectly ok
though.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-05-03 6:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 21:58 [Qemu-devel] Subject: [PATCH] target-ppc: Add global timer group A to open-pic Aaron Larson
2017-04-23 23:17 ` David Gibson
2017-04-24 0:37 ` alarson
2017-04-26 2:51 ` David Gibson
2017-04-26 4:34 ` David Gibson
2017-05-03 1:37 ` alarson
2017-05-03 5:14 ` David Gibson [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-04-21 21:48 Aaron Larson
2017-04-21 21:52 ` no-reply
2017-04-21 22:12 ` alarson
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=20170503051452.GL10741@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=alarson@ddci.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.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).