docs/devel/clocks.rst

14 The object is *Clock* and its QOM name is ``clock`` (in C code, the macro
21 In these cases a Clock object is a child of a Device object, but this
29     | Clock 1 |      |       Device B       |   |   Device C   |
31     |         |>>-+-->>|Clock 2|  |Clock 3|>>--->>|Clock 6|    |
35                   |  |            |Clock 4|>>
39                   |  |            |Clock 5|>>--->>|Clock 7|    |
44                   +----------------------------->>|Clock 8|    |
91 Both functions return the created Clock pointer, which should be saved in the
109         Clock *clk_in;
110         Clock *clk_out;
157 Clock callbacks
187    this callback, Clock API functions like ``clock_get()`` or
190    During this callback, Clock API functions like ``clock_ticks_to_ns()``
206    Clock *clk = qdev_get_clock_in(DEVICE(mydev), "clk_in");
212    Clock *clk = qdev_get_clock_out(DEVICE(mydev), "clk_out");
243   |  |Clock 1|>>-->>|Clock 2|>>+-->>|Clock 3| |Clock 5|>>>>|Clock 6|>>
251                   |            +-->>|Clock 4|    |                   |
257 In the above example, when *Clock 1* is updated by *Device A*, three
258 clocks get the new clock period value: *Clock 2*, *Clock 3* and *Clock 4*.
263 Clock multiplier and divider settings
268 The Clock API supports a built-in period multiplier/divider
297 ``clock_set_ns()`` or ``clock_set_hz()`` should be called on the Clock
495 Clock state is not migrated automatically. Every device must handle its
501 Clock states can be migrated by adding an entry into the device
510         Clock *clk;