From: Peter Maydell <peter.maydell@linaro.org>
To: "KONRAD Frédéric" <fred.konrad@greensocs.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Edgar Iglesias <edgar.iglesias@xilinx.com>,
Alistair Francis <alistair.francis@xilinx.com>,
Mark Burton <mark.burton@greensocs.com>
Subject: Re: [Qemu-devel] [PATCH V2 06/10] docs: add qemu-clock documentation
Date: Tue, 7 Feb 2017 16:13:33 +0000 [thread overview]
Message-ID: <CAFEAcA8uOHb3aUWOcM+Ok_fDiECOfLtx2d2TZp7naKJBcf6+nQ@mail.gmail.com> (raw)
In-Reply-To: <1485424060-12217-7-git-send-email-fred.konrad@greensocs.com>
On 26 January 2017 at 09:47, <fred.konrad@greensocs.com> wrote:
> From: KONRAD Frederic <fred.konrad@greensocs.com>
>
> This adds the qemu-clock documentation.
>
> Signed-off-by: KONRAD Frederic <fred.konrad@greensocs.com>
>
> V1 -> V2:
> * Fixed in accordance with the changes in the previous patches.
> ---
> docs/clock.txt | 108 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 108 insertions(+)
> create mode 100644 docs/clock.txt
Could we have a simple example of what you need to do if you are:
* a device providing a clock source of some kind
* a device that takes a clock input and has one or more
clock outputs which are configured by that device (for
frequency, on/off, etc)
* a device that consumes a clock
please? I think that would help make it more concrete how you
need to use these things.
thanks
-- PMM
next prev parent reply other threads:[~2017-02-07 16:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 9:47 [Qemu-devel] [PATCH V2 00/10] Clock framework API fred.konrad
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 01/10] qemu-clk: introduce qemu-clk qom object fred.konrad
2017-02-05 15:25 ` Cédric Le Goater
2017-02-07 9:20 ` Frederic Konrad
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 02/10] qemu-clk: allow to add a clock to a device fred.konrad
2017-02-06 14:20 ` Cédric Le Goater
2017-02-07 9:22 ` Frederic Konrad
2017-02-07 9:31 ` Cédric Le Goater
2017-02-07 9:49 ` Frederic Konrad
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 03/10] qemu-clk: allow to bind two clocks together fred.konrad
2017-02-06 15:58 ` Cédric Le Goater
2017-02-07 9:45 ` Frederic Konrad
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 04/10] qemu-clk: introduce an init array to help the device construction fred.konrad
2017-02-06 16:02 ` Cédric Le Goater
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 05/10] qdev-monitor: print the device's clock with info qtree fred.konrad
2017-02-06 16:10 ` Cédric Le Goater
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 06/10] docs: add qemu-clock documentation fred.konrad
2017-02-07 16:13 ` Peter Maydell [this message]
2017-02-07 17:15 ` Frederic Konrad
2017-02-07 17:18 ` Peter Maydell
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 07/10] introduce fixed-clock fred.konrad
2017-02-06 16:13 ` Cédric Le Goater
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 08/10] introduce zynqmp_crf fred.konrad
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 09/10] zynqmp: add the zynqmp_crf to the platform fred.konrad
2017-01-26 9:47 ` [Qemu-devel] [PATCH V2 10/10] zynqmp: add reference clock fred.konrad
2017-02-06 16:38 ` Cédric Le Goater
2017-02-03 15:21 ` [Qemu-devel] [PATCH V2 00/10] Clock framework API Frederic Konrad
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=CAFEAcA8uOHb3aUWOcM+Ok_fDiECOfLtx2d2TZp7naKJBcf6+nQ@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=alistair.francis@xilinx.com \
--cc=edgar.iglesias@xilinx.com \
--cc=fred.konrad@greensocs.com \
--cc=mark.burton@greensocs.com \
--cc=qemu-devel@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).