diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-11-23 15:05:00 +0100 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2021-11-23 15:14:27 +0100 |
commit | 51d85ca2fb2c12438a5487c80f4fd4fa6b1800e8 (patch) | |
tree | 41c72cfd5762867f1f6aa6810cc84fc793d5aae5 | |
parent | spec: Add GRLIB errata (diff) | |
download | rtems-central-51d85ca2fb2c12438a5487c80f4fd4fa6b1800e8.tar.bz2 |
spec: Replace "precision" with "resolution"
19 files changed, 55 insertions, 55 deletions
diff --git a/spec/rtems/clock/if/get-monotonic-bintime.yml b/spec/rtems/clock/if/get-monotonic-bintime.yml index cef5ed27..72130ca9 100644 --- a/spec/rtems/clock/if/get-monotonic-bintime.yml +++ b/spec/rtems/clock/if/get-monotonic-bintime.yml @@ -30,10 +30,10 @@ links: name: rtems_clock_get_monotonic_bintime notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. Alternatively, the ${get-monotonic-coarse-bintime:/name} directive may be used to get the time - with less precision and less runtime overhead. + in a lower resolution and with less runtime overhead. See ${get-monotonic:/name}, ${get-monotonic-sbintime:/name}, and ${get-monotonic-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-monotonic-coarse-bintime.yml b/spec/rtems/clock/if/get-monotonic-coarse-bintime.yml index 9681d202..8c1e1ca0 100644 --- a/spec/rtems/clock/if/get-monotonic-coarse-bintime.yml +++ b/spec/rtems/clock/if/get-monotonic-coarse-bintime.yml @@ -1,7 +1,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause brief: | Gets the time elapsed since some fixed time point in the past measured using - the ${/glossary/clock-monotonic:/term} in coarse precision in binary time + the ${/glossary/clock-monotonic:/term} in coarse resolution in binary time format. copyrights: - Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de) @@ -32,8 +32,8 @@ name: rtems_clock_get_monotonic_coarse_bintime notes: | The directive does not access a device to get the time. It uses a recent snapshot provided by the ${/glossary/clock-driver:/term}. Alternatively, the - ${get-monotonic-bintime:/name} directive may be used to get the time with - higher precision and higher runtime overhead. + ${get-monotonic-bintime:/name} directive may be used to get the time in a + higher resolution and with a higher runtime overhead. See ${get-monotonic-coarse:/name} and ${get-monotonic-coarse-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-monotonic-coarse-timeval.yml b/spec/rtems/clock/if/get-monotonic-coarse-timeval.yml index c665d46f..b4ed7f12 100644 --- a/spec/rtems/clock/if/get-monotonic-coarse-timeval.yml +++ b/spec/rtems/clock/if/get-monotonic-coarse-timeval.yml @@ -1,7 +1,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause brief: | Gets the time elapsed since some fixed time point in the past measured using - the ${/glossary/clock-monotonic:/term} in coarse precision in seconds and + the ${/glossary/clock-monotonic:/term} in coarse resolution in seconds and microseconds format. copyrights: - Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de) @@ -32,8 +32,8 @@ name: rtems_clock_get_monotonic_coarse_timeval notes: | The directive does not access a device to get the time. It uses a recent snapshot provided by the ${/glossary/clock-driver:/term}. Alternatively, the - ${get-monotonic-timeval:/name} directive may be used to get the time with - higher precision and higher runtime overhead. + ${get-monotonic-timeval:/name} directive may be used to get the time in a + higher resolution and with a higher runtime overhead. See ${get-monotonic-coarse:/name} and ${get-monotonic-coarse-bintime:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-monotonic-coarse.yml b/spec/rtems/clock/if/get-monotonic-coarse.yml index 09295755..7fdfef77 100644 --- a/spec/rtems/clock/if/get-monotonic-coarse.yml +++ b/spec/rtems/clock/if/get-monotonic-coarse.yml @@ -1,7 +1,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause brief: | Gets the time elapsed since some fixed time point in the past measured using - the ${/glossary/clock-monotonic:/term} in coarse precision in seconds and + the ${/glossary/clock-monotonic:/term} in coarse resolution in seconds and nanoseconds format. copyrights: - Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de) @@ -32,8 +32,8 @@ name: rtems_clock_get_monotonic_coarse notes: | The directive does not access a device to get the time. It uses a recent snapshot provided by the ${/glossary/clock-driver:/term}. Alternatively, the - ${get-monotonic:/name} directive may be used to get the time with higher - precision and higher runtime overhead. + ${get-monotonic:/name} directive may be used to get the time in a higher + resolution and with a higher runtime overhead. See ${get-monotonic-coarse-bintime:/name} and ${get-monotonic-coarse-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-monotonic-sbintime.yml b/spec/rtems/clock/if/get-monotonic-sbintime.yml index 1ed2d681..ae071740 100644 --- a/spec/rtems/clock/if/get-monotonic-sbintime.yml +++ b/spec/rtems/clock/if/get-monotonic-sbintime.yml @@ -29,7 +29,7 @@ links: name: rtems_clock_get_monotonic_sbintime notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. See ${get-monotonic:/name}, ${get-monotonic-bintime:/name}, and diff --git a/spec/rtems/clock/if/get-monotonic-timeval.yml b/spec/rtems/clock/if/get-monotonic-timeval.yml index 532edc1f..f2942475 100644 --- a/spec/rtems/clock/if/get-monotonic-timeval.yml +++ b/spec/rtems/clock/if/get-monotonic-timeval.yml @@ -30,10 +30,10 @@ links: name: rtems_clock_get_monotonic_timeval notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. Alternatively, the ${get-monotonic-coarse-timeval:/name} directive may be used to get the time - with less precision and less runtime overhead. + in a lower resolution and with less runtime overhead. See ${get-monotonic:/name}, ${get-monotonic-bintime:/name}, and ${get-monotonic-sbintime:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-monotonic.yml b/spec/rtems/clock/if/get-monotonic.yml index 99858218..ae08e4c6 100644 --- a/spec/rtems/clock/if/get-monotonic.yml +++ b/spec/rtems/clock/if/get-monotonic.yml @@ -30,10 +30,10 @@ links: name: rtems_clock_get_monotonic notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. Alternatively, the - ${get-monotonic-coarse:/name} directive may be used to get the time with less - precision and less runtime overhead. + ${get-monotonic-coarse:/name} directive may be used to get the time with in a + lower resolution and with less runtime overhead. See ${get-monotonic-bintime:/name}, ${get-monotonic-sbintime:/name}, and ${get-monotonic-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-realtime-bintime.yml b/spec/rtems/clock/if/get-realtime-bintime.yml index 092bc300..2b531a82 100644 --- a/spec/rtems/clock/if/get-realtime-bintime.yml +++ b/spec/rtems/clock/if/get-realtime-bintime.yml @@ -30,10 +30,10 @@ links: name: rtems_clock_get_realtime_bintime notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. Alternatively, the - ${get-realtime-coarse-bintime:/name} directive may be used to get the time - with less precision and less runtime overhead. + ${get-realtime-coarse-bintime:/name} directive may be used to get the time in + a lower resolution and with less runtime overhead. See ${get-realtime:/name} and ${get-realtime-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-realtime-coarse-bintime.yml b/spec/rtems/clock/if/get-realtime-coarse-bintime.yml index 12c4f6d6..18b24baf 100644 --- a/spec/rtems/clock/if/get-realtime-coarse-bintime.yml +++ b/spec/rtems/clock/if/get-realtime-coarse-bintime.yml @@ -1,7 +1,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause brief: | Gets the time elapsed since the ${/glossary/unix-epoch:/term} measured using - ${/glossary/clock-realtime:/term} in coarse precision in binary time format. + ${/glossary/clock-realtime:/term} in coarse resolution in binary time format. copyrights: - Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de) definition: @@ -31,8 +31,8 @@ name: rtems_clock_get_realtime_coarse_bintime notes: | The directive does not access a device to get the time. It uses a recent snapshot provided by the ${/glossary/clock-driver:/term}. Alternatively, the - ${get-realtime-bintime:/name} directive may be used to get the time with - higher precision and higher runtime overhead. + ${get-realtime-bintime:/name} directive may be used to get the time in a + higher resolution and with a higher runtime overhead. See ${get-realtime-coarse:/name} and ${get-realtime-coarse-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-realtime-coarse-timeval.yml b/spec/rtems/clock/if/get-realtime-coarse-timeval.yml index ce6e3dc4..e47bb75b 100644 --- a/spec/rtems/clock/if/get-realtime-coarse-timeval.yml +++ b/spec/rtems/clock/if/get-realtime-coarse-timeval.yml @@ -1,7 +1,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause brief: | Gets the time elapsed since the ${/glossary/unix-epoch:/term} measured using - ${/glossary/clock-realtime:/term} in coarse precision in seconds and + ${/glossary/clock-realtime:/term} in coarse resolution in seconds and microseconds format. copyrights: - Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de) @@ -32,8 +32,8 @@ name: rtems_clock_get_realtime_coarse_timeval notes: | The directive does not access a device to get the time. It uses a recent snapshot provided by the ${/glossary/clock-driver:/term}. Alternatively, the - ${get-realtime-timeval:/name} directive may be used to get the time with - higher precision and higher runtime overhead. + ${get-realtime-timeval:/name} directive may be used to get the time in a + higher resolution and with a higher runtime overhead. See ${get-realtime-coarse:/name} and ${get-realtime-coarse-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-realtime-coarse.yml b/spec/rtems/clock/if/get-realtime-coarse.yml index 2fe61eb2..21c6aa9c 100644 --- a/spec/rtems/clock/if/get-realtime-coarse.yml +++ b/spec/rtems/clock/if/get-realtime-coarse.yml @@ -1,7 +1,7 @@ SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause brief: | Gets the time elapsed since the ${/glossary/unix-epoch:/term} measured using - ${/glossary/clock-realtime:/term} in coarse precision in seconds and + ${/glossary/clock-realtime:/term} in coarse resolution in seconds and nanoseconds format. copyrights: - Copyright (C) 2021 embedded brains GmbH (http://www.embedded-brains.de) @@ -32,8 +32,8 @@ name: rtems_clock_get_realtime_coarse notes: | The directive does not access a device to get the time. It uses a recent snapshot provided by the ${/glossary/clock-driver:/term}. Alternatively, the - ${get-realtime:/name} directive may be used to get the time with - higher precision and higher runtime overhead. + ${get-realtime:/name} directive may be used to get the time in a higher + resolution and with a higher runtime overhead. See ${get-realtime-coarse-bintime:/name} and ${get-realtime-coarse-timeval:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-realtime-timeval.yml b/spec/rtems/clock/if/get-realtime-timeval.yml index dcbee87b..e5edd0d2 100644 --- a/spec/rtems/clock/if/get-realtime-timeval.yml +++ b/spec/rtems/clock/if/get-realtime-timeval.yml @@ -30,10 +30,10 @@ links: name: rtems_clock_get_realtime_timeval notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. Alternatively, the - ${get-realtime-coarse-timeval:/name} directive may be used to get the time - with less precision and less runtime overhead. + ${get-realtime-coarse-timeval:/name} directive may be used to get the time in + a lower resolution and with less runtime overhead. See ${get-realtime:/name} and ${get-realtime-bintime:/name} to get the time in alternative formats. diff --git a/spec/rtems/clock/if/get-realtime.yml b/spec/rtems/clock/if/get-realtime.yml index 912d4142..04a53191 100644 --- a/spec/rtems/clock/if/get-realtime.yml +++ b/spec/rtems/clock/if/get-realtime.yml @@ -30,10 +30,10 @@ links: name: rtems_clock_get_realtime notes: | The directive accesses a device provided by the - ${/glossary/clock-driver:/term} to get the time in the highest precision + ${/glossary/clock-driver:/term} to get the time in the highest resolution available to the system. Alternatively, the - ${get-realtime-coarse:/name} directive may be used to get the time with less - precision and less runtime overhead. + ${get-realtime-coarse:/name} directive may be used to get the time in a lower + resolution and with less runtime overhead. See ${get-realtime-bintime:/name} and ${get-realtime-timeval:/name} to get the time in alternative formats. diff --git a/spec/score/timecounter/req/get-coarse-no-device.yml b/spec/score/timecounter/req/get-coarse-no-device.yml index 752ee27a..a54b90e4 100644 --- a/spec/score/timecounter/req/get-coarse-no-device.yml +++ b/spec/score/timecounter/req/get-coarse-no-device.yml @@ -10,6 +10,6 @@ rationale: null references: [] requirement-type: functional text: | - The directives to get time values in a coarse precision shall not use the + The directives to get time values in a coarse resolution shall not use the currently installed timecounter. type: requirement diff --git a/spec/score/timecounter/req/get-coarse.yml b/spec/score/timecounter/req/get-coarse.yml index 875d4550..bdd1c0e7 100644 --- a/spec/score/timecounter/req/get-coarse.yml +++ b/spec/score/timecounter/req/get-coarse.yml @@ -11,5 +11,5 @@ references: [] requirement-type: non-functional text: | The timecounter component shall implement directives to get time values in a - coarse precision. + coarse resolution. type: requirement diff --git a/spec/score/timecounter/req/get-device.yml b/spec/score/timecounter/req/get-device.yml index 27219ebc..1897478c 100644 --- a/spec/score/timecounter/req/get-device.yml +++ b/spec/score/timecounter/req/get-device.yml @@ -10,6 +10,6 @@ rationale: null references: [] requirement-type: functional text: | - The directives to get time values in the highest precision shall use the + The directives to get time values in the highest resolution shall use the currently installed timecounter to get a clock snapshot. type: requirement diff --git a/spec/score/timecounter/req/get-large-delta.yml b/spec/score/timecounter/req/get-large-delta.yml index 1b7770b3..5ca6ec31 100644 --- a/spec/score/timecounter/req/get-large-delta.yml +++ b/spec/score/timecounter/req/get-large-delta.yml @@ -12,5 +12,5 @@ requirement-type: functional text: | While the timehand used to get the time was not updated for one second or more, while the timecounter of the timehand did not overflow, the directives - to get time values in the highest precision shall return the correct time. + to get time values in the highest resolution shall return the correct time. type: requirement diff --git a/spec/score/timecounter/req/get.yml b/spec/score/timecounter/req/get.yml index fa8234e6..f109b415 100644 --- a/spec/score/timecounter/req/get.yml +++ b/spec/score/timecounter/req/get.yml @@ -11,5 +11,5 @@ references: [] requirement-type: non-functional text: | The timecounter component shall implement directives to get time values in - the highest precision available to the system. + the highest resolution available to the system. type: requirement diff --git a/spec/score/timecounter/val/install.yml b/spec/score/timecounter/val/install.yml index b9c25702..fb8041dc 100644 --- a/spec/score/timecounter/val/install.yml +++ b/spec/score/timecounter/val/install.yml @@ -50,7 +50,7 @@ test-actions: - role: validation uid: ../req/clock-realtime-initial-frozen - brief: | - Check the initial ${/glossary/clock-realtime:/term} in coarse precision + Check the initial ${/glossary/clock-realtime:/term} in coarse resolution in seconds and nanoseconds format. code: | rtems_clock_get_realtime_coarse( &ts ); @@ -63,7 +63,7 @@ test-actions: uid: /rtems/clock/req/get-realtime-coarse - brief: | Check that ${/glossary/clock-realtime:/term} is frozen in coarse - precision in seconds and nanoseconds format. + resolution in seconds and nanoseconds format. code: | rtems_clock_get_realtime_coarse( &ts ); T_eq_i64( ts.tv_sec, 567993600 ); @@ -94,7 +94,7 @@ test-actions: - role: validation uid: ../req/clock-realtime-initial-frozen - brief: | - Check the initial ${/glossary/clock-realtime:/term} in coarse precision + Check the initial ${/glossary/clock-realtime:/term} in coarse resolution in binary time format. code: | rtems_clock_get_realtime_coarse_bintime( &bt ); @@ -107,7 +107,7 @@ test-actions: uid: /rtems/clock/req/get-realtime-coarse - brief: | Check that ${/glossary/clock-realtime:/term} is frozen in coarse - precision in binary time format. + resolution in binary time format. code: | rtems_clock_get_realtime_coarse_bintime( &bt ); T_eq_i64( bt.sec, 567993600 ); @@ -138,7 +138,7 @@ test-actions: - role: validation uid: ../req/clock-realtime-initial-frozen - brief: | - Check the initial ${/glossary/clock-realtime:/term} in coarse precision + Check the initial ${/glossary/clock-realtime:/term} in coarse resolution in seconds and microseconds format. code: | rtems_clock_get_realtime_coarse_timeval( &tv ); @@ -151,7 +151,7 @@ test-actions: uid: /rtems/clock/req/get-realtime-coarse - brief: | Check that ${/glossary/clock-realtime:/term} is frozen in coarse - precision in seconds and microseconds format. + resolution in seconds and microseconds format. code: | rtems_clock_get_realtime_coarse_timeval( &tv ); T_eq_i64( tv.tv_sec, 567993600 ); @@ -231,7 +231,7 @@ test-actions: - role: validation uid: ../req/clock-monotonic-initial-frozen - brief: | - Check the initial ${/glossary/clock-monotonic:/term} in coarse precision + Check the initial ${/glossary/clock-monotonic:/term} in coarse resolution in seconds and nanoseconds format. code: | rtems_clock_get_monotonic_coarse( &ts ); @@ -244,7 +244,7 @@ test-actions: uid: /rtems/clock/req/get-monotonic-coarse - brief: | Check that ${/glossary/clock-monotonic:/term} is frozen in coarse - precision in seconds and nanoseconds format. + resolution in seconds and nanoseconds format. code: | rtems_clock_get_monotonic_coarse( &ts ); T_eq_i64( ts.tv_sec, 1 ); @@ -275,7 +275,7 @@ test-actions: - role: validation uid: ../req/clock-monotonic-initial-frozen - brief: | - Check the initial ${/glossary/clock-monotonic:/term} in coarse precision + Check the initial ${/glossary/clock-monotonic:/term} in coarse resolution in binary time format. code: | rtems_clock_get_monotonic_coarse_bintime( &bt ); @@ -288,7 +288,7 @@ test-actions: uid: /rtems/clock/req/get-monotonic-coarse - brief: | Check that ${/glossary/clock-monotonic:/term} is frozen in coarse - precision in binary time format. + resolution in binary time format. code: | rtems_clock_get_monotonic_coarse_bintime( &bt ); T_eq_i64( bt.sec, 1 ); @@ -339,7 +339,7 @@ test-actions: - role: validation uid: ../req/clock-monotonic-initial-frozen - brief: | - Check the initial ${/glossary/clock-monotonic:/term} in coarse precision + Check the initial ${/glossary/clock-monotonic:/term} in coarse resolution in seconds and microseconds format. code: | rtems_clock_get_monotonic_coarse_timeval( &tv ); @@ -352,7 +352,7 @@ test-actions: uid: /rtems/clock/req/get-monotonic-coarse - brief: | Check that ${/glossary/clock-monotonic:/term} is frozen in coarse - precision in seconds and microseconds format. + resolution in seconds and microseconds format. code: | rtems_clock_get_monotonic_coarse_timeval( &tv ); T_eq_i64( tv.tv_sec, 1 ); @@ -461,7 +461,7 @@ test-actions: uid: ../req/install-quality links: [] - action-brief: | - Call the directives to get the time in the highest precision available to + Call the directives to get the time in the highest resolution available to the system. action-code: | Timecounter *tc; @@ -552,7 +552,7 @@ test-actions: uid: /rtems/clock/req/get-monotonic links: [] - action-brief: | - Call the directives to get the time in a coarse precision. + Call the directives to get the time in a coarse resolution. action-code: | Timecounter *tc; uint32_t counter; @@ -664,7 +664,7 @@ test-actions: uid: /rtems/clock/req/get-boot-time links: [] - action-brief: | - Call the directives to get the time in the highest precision available to + Call the directives to get the time in the highest resolution available to the system. action-code: | Timecounter *tc; |