Changeset 838b78a in rtems-docs
- Timestamp:
- 11/23/21 14:20:06 (15 months ago)
- Branches:
- master
- Children:
- 8731bd6
- Parents:
- 513b90d
- git-author:
- Sebastian Huber <sebastian.huber@…> (11/23/21 14:20:06)
- git-committer:
- Sebastian Huber <sebastian.huber@…> (11/23/21 14:21:00)
- Location:
- c-user/clock
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
c-user/clock/directives.rst
r513b90d r838b78a 256 256 257 257 The directive accesses a device provided by the :term:`Clock Driver` to get the 258 time in the highest precision available to the system. Alternatively, the258 time in the highest resolution available to the system. Alternatively, the 259 259 :ref:`InterfaceRtemsClockGetRealtimeCoarse` directive may be used to get the 260 time with less precision andless runtime overhead.260 time in a lower resolution and with less runtime overhead. 261 261 262 262 See :ref:`InterfaceRtemsClockGetRealtimeBintime` and … … 308 308 309 309 The directive accesses a device provided by the :term:`Clock Driver` to get the 310 time in the highest precision available to the system. Alternatively, the310 time in the highest resolution available to the system. Alternatively, the 311 311 :ref:`InterfaceRtemsClockGetRealtimeCoarseBintime` directive may be used to get 312 the time with less precision andless runtime overhead.312 the time in a lower resolution and with less runtime overhead. 313 313 314 314 See :ref:`InterfaceRtemsClockGetRealtime` and … … 361 361 362 362 The directive accesses a device provided by the :term:`Clock Driver` to get the 363 time in the highest precision available to the system. Alternatively, the363 time in the highest resolution available to the system. Alternatively, the 364 364 :ref:`InterfaceRtemsClockGetRealtimeCoarseTimeval` directive may be used to get 365 the time with less precision andless runtime overhead.365 the time in a lower resolution and with less runtime overhead. 366 366 367 367 See :ref:`InterfaceRtemsClockGetRealtime` and … … 393 393 394 394 Gets the time elapsed since the :term:`Unix epoch` measured using 395 :term:`CLOCK_REALTIME` in coarse precision in seconds and nanoseconds format.395 :term:`CLOCK_REALTIME` in coarse resolution in seconds and nanoseconds format. 396 396 397 397 .. rubric:: CALLING SEQUENCE: … … 416 416 The directive does not access a device to get the time. It uses a recent 417 417 snapshot provided by the :term:`Clock Driver`. Alternatively, the 418 :ref:`InterfaceRtemsClockGetRealtime` directive may be used to get the time 419 with higher precision andhigher runtime overhead.418 :ref:`InterfaceRtemsClockGetRealtime` directive may be used to get the time in 419 a higher resolution and with a higher runtime overhead. 420 420 421 421 See :ref:`InterfaceRtemsClockGetRealtimeCoarseBintime` and … … 447 447 448 448 Gets the time elapsed since the :term:`Unix epoch` measured using 449 :term:`CLOCK_REALTIME` in coarse precision in binary time format.449 :term:`CLOCK_REALTIME` in coarse resolution in binary time format. 450 450 451 451 .. rubric:: CALLING SEQUENCE: … … 470 470 snapshot provided by the :term:`Clock Driver`. Alternatively, the 471 471 :ref:`InterfaceRtemsClockGetRealtimeBintime` directive may be used to get the 472 time with higher precision andhigher runtime overhead.472 time in a higher resolution and with a higher runtime overhead. 473 473 474 474 See :ref:`InterfaceRtemsClockGetRealtimeCoarse` and … … 500 500 501 501 Gets the time elapsed since the :term:`Unix epoch` measured using 502 :term:`CLOCK_REALTIME` in coarse precision in seconds and microseconds format.502 :term:`CLOCK_REALTIME` in coarse resolution in seconds and microseconds format. 503 503 504 504 .. rubric:: CALLING SEQUENCE: … … 524 524 snapshot provided by the :term:`Clock Driver`. Alternatively, the 525 525 :ref:`InterfaceRtemsClockGetRealtimeTimeval` directive may be used to get the 526 time with higher precision andhigher runtime overhead.526 time in a higher resolution and with a higher runtime overhead. 527 527 528 528 See :ref:`InterfaceRtemsClockGetRealtimeCoarse` and … … 575 575 576 576 The directive accesses a device provided by the :term:`Clock Driver` to get the 577 time in the highest precision available to the system. Alternatively, the577 time in the highest resolution available to the system. Alternatively, the 578 578 :ref:`InterfaceRtemsClockGetMonotonicCoarse` directive may be used to get the 579 time with less precision andless runtime overhead.579 time with in a lower resolution and with less runtime overhead. 580 580 581 581 See :ref:`InterfaceRtemsClockGetMonotonicBintime`, … … 629 629 630 630 The directive accesses a device provided by the :term:`Clock Driver` to get the 631 time in the highest precision available to the system. Alternatively, the631 time in the highest resolution available to the system. Alternatively, the 632 632 :ref:`InterfaceRtemsClockGetMonotonicCoarseBintime` directive may be used to 633 get the time with less precision andless runtime overhead.633 get the time in a lower resolution and with less runtime overhead. 634 634 635 635 See :ref:`InterfaceRtemsClockGetMonotonic`, … … 678 678 679 679 The directive accesses a device provided by the :term:`Clock Driver` to get the 680 time in the highest precision available to the system.680 time in the highest resolution available to the system. 681 681 682 682 See :ref:`InterfaceRtemsClockGetMonotonic`, … … 730 730 731 731 The directive accesses a device provided by the :term:`Clock Driver` to get the 732 time in the highest precision available to the system. Alternatively, the732 time in the highest resolution available to the system. Alternatively, the 733 733 :ref:`InterfaceRtemsClockGetMonotonicCoarseTimeval` directive may be used to 734 get the time with less precision andless runtime overhead.734 get the time in a lower resolution and with less runtime overhead. 735 735 736 736 See :ref:`InterfaceRtemsClockGetMonotonic`, … … 763 763 764 764 Gets the time elapsed since some fixed time point in the past measured using 765 the :term:`CLOCK_MONOTONIC` in coarse precision in seconds and nanoseconds765 the :term:`CLOCK_MONOTONIC` in coarse resolution in seconds and nanoseconds 766 766 format. 767 767 … … 786 786 The directive does not access a device to get the time. It uses a recent 787 787 snapshot provided by the :term:`Clock Driver`. Alternatively, the 788 :ref:`InterfaceRtemsClockGetMonotonic` directive may be used to get the time 789 with higher precision andhigher runtime overhead.788 :ref:`InterfaceRtemsClockGetMonotonic` directive may be used to get the time in 789 a higher resolution and with a higher runtime overhead. 790 790 791 791 See :ref:`InterfaceRtemsClockGetMonotonicCoarseBintime` and … … 817 817 818 818 Gets the time elapsed since some fixed time point in the past measured using 819 the :term:`CLOCK_MONOTONIC` in coarse precision in binary time format.819 the :term:`CLOCK_MONOTONIC` in coarse resolution in binary time format. 820 820 821 821 .. rubric:: CALLING SEQUENCE: … … 840 840 snapshot provided by the :term:`Clock Driver`. Alternatively, the 841 841 :ref:`InterfaceRtemsClockGetMonotonicBintime` directive may be used to get the 842 time with higher precision andhigher runtime overhead.842 time in a higher resolution and with a higher runtime overhead. 843 843 844 844 See :ref:`InterfaceRtemsClockGetMonotonicCoarse` and … … 870 870 871 871 Gets the time elapsed since some fixed time point in the past measured using 872 the :term:`CLOCK_MONOTONIC` in coarse precision in seconds and microseconds872 the :term:`CLOCK_MONOTONIC` in coarse resolution in seconds and microseconds 873 873 format. 874 874 … … 894 894 snapshot provided by the :term:`Clock Driver`. Alternatively, the 895 895 :ref:`InterfaceRtemsClockGetMonotonicTimeval` directive may be used to get the 896 time with higher precision andhigher runtime overhead.896 time in a higher resolution and with a higher runtime overhead. 897 897 898 898 See :ref:`InterfaceRtemsClockGetMonotonicCoarse` and -
c-user/clock/introduction.rst
r513b90d r838b78a 82 82 83 83 * :ref:`InterfaceRtemsClockGetRealtimeCoarse` - Gets the time elapsed since the 84 :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse precision84 :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse resolution 85 85 in seconds and nanoseconds format. 86 86 87 87 * :ref:`InterfaceRtemsClockGetRealtimeCoarseBintime` - Gets the time elapsed 88 88 since the :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse 89 precision in binary time format.89 resolution in binary time format. 90 90 91 91 * :ref:`InterfaceRtemsClockGetRealtimeCoarseTimeval` - Gets the time elapsed 92 92 since the :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse 93 precision in seconds and microseconds format.93 resolution in seconds and microseconds format. 94 94 95 95 * :ref:`InterfaceRtemsClockGetMonotonic` - Gets the time elapsed since some … … 111 111 * :ref:`InterfaceRtemsClockGetMonotonicCoarse` - Gets the time elapsed since 112 112 some fixed time point in the past measured using the :term:`CLOCK_MONOTONIC` 113 in coarse precision in seconds and nanoseconds format.113 in coarse resolution in seconds and nanoseconds format. 114 114 115 115 * :ref:`InterfaceRtemsClockGetMonotonicCoarseBintime` - Gets the time elapsed 116 116 since some fixed time point in the past measured using the 117 :term:`CLOCK_MONOTONIC` in coarse precision in binary time format.117 :term:`CLOCK_MONOTONIC` in coarse resolution in binary time format. 118 118 119 119 * :ref:`InterfaceRtemsClockGetMonotonicCoarseTimeval` - Gets the time elapsed 120 120 since some fixed time point in the past measured using the 121 :term:`CLOCK_MONOTONIC` in coarse precision in seconds and microseconds121 :term:`CLOCK_MONOTONIC` in coarse resolution in seconds and microseconds 122 122 format. 123 123
Note: See TracChangeset
for help on using the changeset viewer.