Changeset 838b78a in rtems-docs


Ignore:
Timestamp:
11/23/21 14:20:06 (15 months ago)
Author:
Sebastian Huber <sebastian.huber@…>
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)
Message:

c-user: Replace "precision" with "resolution"

Resolution is the right term for the documented property.

Location:
c-user/clock
Files:
2 edited

Legend:

Unmodified
Added
Removed

  • c-user/clock/directives.rst

    r513b90d r838b78a  
    256256
    257257The directive accesses a device provided by the :term:`Clock Driver` to get the
    258 time in the highest precision available to the system.  Alternatively, the
     258time in the highest resolution available to the system.  Alternatively, the
    259259:ref:`InterfaceRtemsClockGetRealtimeCoarse` directive may be used to get the
    260 time with less precision and less runtime overhead.
     260time in a lower resolution and with less runtime overhead.
    261261
    262262See :ref:`InterfaceRtemsClockGetRealtimeBintime` and
    … …  
    308308
    309309The directive accesses a device provided by the :term:`Clock Driver` to get the
    310 time in the highest precision available to the system.  Alternatively, the
     310time in the highest resolution available to the system.  Alternatively, the
    311311:ref:`InterfaceRtemsClockGetRealtimeCoarseBintime` directive may be used to get
    312 the time with less precision and less runtime overhead.
     312the time in a lower resolution and with less runtime overhead.
    313313
    314314See :ref:`InterfaceRtemsClockGetRealtime` and
    … …  
    361361
    362362The directive accesses a device provided by the :term:`Clock Driver` to get the
    363 time in the highest precision available to the system.  Alternatively, the
     363time in the highest resolution available to the system.  Alternatively, the
    364364:ref:`InterfaceRtemsClockGetRealtimeCoarseTimeval` directive may be used to get
    365 the time with less precision and less runtime overhead.
     365the time in a lower resolution and with less runtime overhead.
    366366
    367367See :ref:`InterfaceRtemsClockGetRealtime` and
    … …  
    393393
    394394Gets 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.
    396396
    397397.. rubric:: CALLING SEQUENCE:
    … …  
    416416The directive does not access a device to get the time.  It uses a recent
    417417snapshot provided by the :term:`Clock Driver`.  Alternatively, the
    418 :ref:`InterfaceRtemsClockGetRealtime` directive may be used to get the time
    419 with higher precision and higher runtime overhead.
     418:ref:`InterfaceRtemsClockGetRealtime` directive may be used to get the time in
     419a higher resolution and with a higher runtime overhead.
    420420
    421421See :ref:`InterfaceRtemsClockGetRealtimeCoarseBintime` and
    … …  
    447447
    448448Gets 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.
    450450
    451451.. rubric:: CALLING SEQUENCE:
    … …  
    470470snapshot provided by the :term:`Clock Driver`.  Alternatively, the
    471471:ref:`InterfaceRtemsClockGetRealtimeBintime` directive may be used to get the
    472 time with higher precision and higher runtime overhead.
     472time in a higher resolution and with a higher runtime overhead.
    473473
    474474See :ref:`InterfaceRtemsClockGetRealtimeCoarse` and
    … …  
    500500
    501501Gets 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.
    503503
    504504.. rubric:: CALLING SEQUENCE:
    … …  
    524524snapshot provided by the :term:`Clock Driver`.  Alternatively, the
    525525:ref:`InterfaceRtemsClockGetRealtimeTimeval` directive may be used to get the
    526 time with higher precision and higher runtime overhead.
     526time in a higher resolution and with a higher runtime overhead.
    527527
    528528See :ref:`InterfaceRtemsClockGetRealtimeCoarse` and
    … …  
    575575
    576576The directive accesses a device provided by the :term:`Clock Driver` to get the
    577 time in the highest precision available to the system.  Alternatively, the
     577time in the highest resolution available to the system.  Alternatively, the
    578578:ref:`InterfaceRtemsClockGetMonotonicCoarse` directive may be used to get the
    579 time with less precision and less runtime overhead.
     579time with in a lower resolution and with less runtime overhead.
    580580
    581581See :ref:`InterfaceRtemsClockGetMonotonicBintime`,
    … …  
    629629
    630630The directive accesses a device provided by the :term:`Clock Driver` to get the
    631 time in the highest precision available to the system.  Alternatively, the
     631time in the highest resolution available to the system.  Alternatively, the
    632632:ref:`InterfaceRtemsClockGetMonotonicCoarseBintime` directive may be used to
    633 get the time with less precision and less runtime overhead.
     633get the time in a lower resolution and with less runtime overhead.
    634634
    635635See :ref:`InterfaceRtemsClockGetMonotonic`,
    … …  
    678678
    679679The directive accesses a device provided by the :term:`Clock Driver` to get the
    680 time in the highest precision available to the system.
     680time in the highest resolution available to the system.
    681681
    682682See :ref:`InterfaceRtemsClockGetMonotonic`,
    … …  
    730730
    731731The directive accesses a device provided by the :term:`Clock Driver` to get the
    732 time in the highest precision available to the system.  Alternatively, the
     732time in the highest resolution available to the system.  Alternatively, the
    733733:ref:`InterfaceRtemsClockGetMonotonicCoarseTimeval` directive may be used to
    734 get the time with less precision and less runtime overhead.
     734get the time in a lower resolution and with less runtime overhead.
    735735
    736736See :ref:`InterfaceRtemsClockGetMonotonic`,
    … …  
    763763
    764764Gets the time elapsed since some fixed time point in the past measured using
    765 the :term:`CLOCK_MONOTONIC` in coarse precision in seconds and nanoseconds
     765the :term:`CLOCK_MONOTONIC` in coarse resolution in seconds and nanoseconds
    766766format.
    767767
    … …  
    786786The directive does not access a device to get the time.  It uses a recent
    787787snapshot provided by the :term:`Clock Driver`.  Alternatively, the
    788 :ref:`InterfaceRtemsClockGetMonotonic` directive may be used to get the time
    789 with higher precision and higher runtime overhead.
     788:ref:`InterfaceRtemsClockGetMonotonic` directive may be used to get the time in
     789a higher resolution and with a higher runtime overhead.
    790790
    791791See :ref:`InterfaceRtemsClockGetMonotonicCoarseBintime` and
    … …  
    817817
    818818Gets 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.
     819the :term:`CLOCK_MONOTONIC` in coarse resolution in binary time format.
    820820
    821821.. rubric:: CALLING SEQUENCE:
    … …  
    840840snapshot provided by the :term:`Clock Driver`.  Alternatively, the
    841841:ref:`InterfaceRtemsClockGetMonotonicBintime` directive may be used to get the
    842 time with higher precision and higher runtime overhead.
     842time in a higher resolution and with a higher runtime overhead.
    843843
    844844See :ref:`InterfaceRtemsClockGetMonotonicCoarse` and
    … …  
    870870
    871871Gets the time elapsed since some fixed time point in the past measured using
    872 the :term:`CLOCK_MONOTONIC` in coarse precision in seconds and microseconds
     872the :term:`CLOCK_MONOTONIC` in coarse resolution in seconds and microseconds
    873873format.
    874874
    … …  
    894894snapshot provided by the :term:`Clock Driver`.  Alternatively, the
    895895:ref:`InterfaceRtemsClockGetMonotonicTimeval` directive may be used to get the
    896 time with higher precision and higher runtime overhead.
     896time in a higher resolution and with a higher runtime overhead.
    897897
    898898See :ref:`InterfaceRtemsClockGetMonotonicCoarse` and

  • c-user/clock/introduction.rst

    r513b90d r838b78a  
    8282
    8383* :ref:`InterfaceRtemsClockGetRealtimeCoarse` - Gets the time elapsed since the
    84   :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse precision
     84  :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse resolution
    8585  in seconds and nanoseconds format.
    8686
    8787* :ref:`InterfaceRtemsClockGetRealtimeCoarseBintime` - Gets the time elapsed
    8888  since the :term:`Unix epoch` measured using :term:`CLOCK_REALTIME` in coarse
    89   precision in binary time format.
     89  resolution in binary time format.
    9090
    9191* :ref:`InterfaceRtemsClockGetRealtimeCoarseTimeval` - Gets the time elapsed
    9292  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.
    9494
    9595* :ref:`InterfaceRtemsClockGetMonotonic` - Gets the time elapsed since some
    … …  
    111111* :ref:`InterfaceRtemsClockGetMonotonicCoarse` - Gets the time elapsed since
    112112  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.
    114114
    115115* :ref:`InterfaceRtemsClockGetMonotonicCoarseBintime` - Gets the time elapsed
    116116  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.
    118118
    119119* :ref:`InterfaceRtemsClockGetMonotonicCoarseTimeval` - Gets the time elapsed
    120120  since some fixed time point in the past measured using the
    121   :term:`CLOCK_MONOTONIC` in coarse precision in seconds and microseconds
     121  :term:`CLOCK_MONOTONIC` in coarse resolution in seconds and microseconds
    122122  format.
    123123
Note: See TracChangeset for help on using the changeset viewer.