include/hw/clock.h

26  * Argument to ClockCallback functions indicating why the callback
28  * is used to specify which events are interesting when the callback
33     ClockPreUpdate = 2, /* Clock period is about to update */
41  *  + periods from 2^-32ns up to 4seconds
51  * macro helpers to convert to hertz / nanosecond
66  * @children: list of clocks connected to this one (it is their source)
67  * @sibling: structure used to form a clock list
84     /* Ratio of the parent clock to run the child clocks at */
95  * vmstate description entry to be added in device vmsd.
121  * Helper function to create a new clock and parent it to @parent. There is no
122  * need to call clock_setup_canonical_path on the returned clock as it is done
131  * @clk: the clock to register the callback into
133  * @opaque: the argument to the callback
150  * value is also copied to @clk and its subtree but no callback is
152  * Further @src update will be propagated to @clk and its subtree.
160  * Returns true if the clock has a source clock connected to it.
163  * device code can use this to check in its realize method that
173  * @clk: the clock to initialize.
176  * Set the local cached period value of @clk to @value.
198  * It is an error to call this function on a clock which has a source.
206  * @clk: the clock to update.
209  * Update the @clk to the new @value. All connected clocks will be informed
210  * of this update. This is equivalent to call @clock_set() then
232  * @clk: the clk to fetch the clock
248  * @clk: the clock to query
252  * to tick @ticks times. Because a clock can have a period
254  * to use this function when calculating things like timer
255  * expiry deadlines, rather than attempting to obtain a "period
259  * The result could in theory be too large to fit in a 64-bit
261  * large; to avoid overflow the result will be saturated to INT64_MAX
262  * (because this is the largest valid input to the QEMUTimer APIs).
274      * units, and we can convert to nanoseconds by multiplying by  in clock_ticks_to_ns()
287  * @clk: the clock to query
292  * is not a whole number of nanoseconds, it is important to use this
293  * function rather than attempting to obtain a "period in nanoseconds"
300  * cases we truncate the result to a 64-bit value. This is on the
301  * assumption that generally the result is going to be used to report
311      * The hi, lo inputs to divu128() are (ns << 32) as a 128 bit value.  in clock_ns_to_ticks()
355  * as their parent. This function allows you to adjust the multiplier
356  * and divider used to derive the child clock frequency.
362  * Setting the multiplier to 0 will stop the child clocks.
363  * Setting the divider to 0 is a programming error (diagnosed with