<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div dir="ltr"><div>Thanks, v2 coming shortly.</div><div><br></div><div>Kinsey<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 28, 2023 at 1:28 PM Sebastian Huber <<a href="mailto:sebastian.huber@embedded-brains.de">sebastian.huber@embedded-brains.de</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 28.06.23 20:22, Kinsey Moore wrote:<br>
> rtems_task_wake_after takes a parameter in terms of a count of clock<br>
> ticks and not a measure in a subunit of seconds. This updates<br>
> documentation to reflect that and recommends clock_nanosleep() for<br>
> applications requiring sleep for a time-based duration instead of a<br>
> count of clock ticks.<br>
> <br>
> Updates #4772<br>
> ---<br>
> spec/rtems/task/if/wake-after.yml | 26 +++++++++++++++-----------<br>
> 1 file changed, 15 insertions(+), 11 deletions(-)<br>
> <br>
> diff --git a/spec/rtems/task/if/wake-after.yml b/spec/rtems/task/if/wake-after.yml<br>
> index b3805251..a5791f14 100644<br>
> --- a/spec/rtems/task/if/wake-after.yml<br>
> +++ b/spec/rtems/task/if/wake-after.yml<br>
> @@ -1,7 +1,7 @@<br>
> SPDX-License-Identifier: CC-BY-SA-4.0 OR BSD-2-Clause<br>
> brief: |<br>
> - Wakes up after an interval in ${/glossary/clock-tick:/plural} or yields the<br>
> - processor.<br>
> + Wakes up after a count of ${/glossary/clock-tick:/plural} have occurred or<br>
> + yields the processor.<br>
> copyrights:<br>
> - Copyright (C) 2021 embedded brains GmbH (<a href="http://www.embedded-brains.de" rel="noreferrer" target="_blank">http://www.embedded-brains.de</a>)<br>
> - Copyright (C) 1988, 2017 On-Line Applications Research Corporation (OAR)<br>
<br>
Maybe update to 2023.<br>
<br>
> @@ -15,15 +15,15 @@ definition:<br>
> variants: []<br>
> description: |<br>
> This directive blocks the calling task for the specified ${.:/params[0]/name}<br>
> - of clock ticks if the value is not equal to ${yield-processor:/name}. When<br>
> - the requested interval has elapsed, the task is made ready. The clock tick<br>
> - directives automatically updates the delay period. The calling task may give<br>
> - up the processor and remain in the ready state by specifying a value of<br>
> - ${yield-processor:/name} in ${.:/params[0]/name}.<br>
> + count of clock ticks if the value is not equal to ${yield-processor:/name}.<br>
> + When the requested count of ticks have occurred, the task is made ready. The<br>
> + clock tick directives automatically update the delay period. The calling task<br>
> + may give up the processor and remain in the ready state by specifying a value<br>
> + of ${yield-processor:/name} in ${.:/params[0]/name}.<br>
> enabled-by: true<br>
> index-entries:<br>
> -- delay a task for an interval<br>
> -- wake up after an interval<br>
> +- delay a task for a count of clock ticks<br>
> +- wake up after a count of clock ticks<br>
> interface-type: function<br>
> links:<br>
> - role: interface-placement<br>
> @@ -40,10 +40,14 @@ name: rtems_task_wake_after<br>
> notes: |<br>
> Setting the system date and time with the ${../../clock/if/set:/name}<br>
> directive and similar directives which set ${/glossary/clock-realtime:/term}<br>
> - have no effect on a ${wake-after:/name} blocked task.<br>
> + have no effect on a ${wake-after:/name} blocked task. The delay until first<br>
> + clock tick will never be a whole clock tick interval since this directive will<br>
> + never excute exactly on a clock tick. Applications requiring use of a clock<br>
> + (CLOCK_REALTIME or CLOCK_MONOTONIC) instead of clock ticks should make use of<br>
<br>
(${/glossary/clock-realtime:/term} or <br>
${/glossary/clock-monotonic:/term}) instead...<br>
<br>
> + ${/c/if/clock-nanosleep:/name}.<br>
> params:<br>
> - description: |<br>
> - is the interval in ${/glossary/clock-tick:/plural} to delay the task or<br>
> + is the count of ${/glossary/clock-tick:/plural} to delay the task or<br>
> ${yield-processor:/name} to yield the processor.<br>
> dir: null<br>
> name: ticks<br>
<br>
Thanks, it is now clear to me.<br>
<br>
-- <br>
embedded brains GmbH<br>
Herr Sebastian HUBER<br>
Dornierstr. 4<br>
82178 Puchheim<br>
Germany<br>
email: <a href="mailto:sebastian.huber@embedded-brains.de" target="_blank">sebastian.huber@embedded-brains.de</a><br>
phone: +49-89-18 94 741 - 16<br>
fax: +49-89-18 94 741 - 08<br>
<br>
Registergericht: Amtsgericht München<br>
Registernummer: HRB 157899<br>
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler<br>
Unsere Datenschutzerklärung finden Sie hier:<br>
<a href="https://embedded-brains.de/datenschutzerklaerung/" rel="noreferrer" target="_blank">https://embedded-brains.de/datenschutzerklaerung/</a><br>
_______________________________________________<br>
devel mailing list<br>
<a href="mailto:devel@rtems.org" target="_blank">devel@rtems.org</a><br>
<a href="http://lists.rtems.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">http://lists.rtems.org/mailman/listinfo/devel</a></blockquote></div>