rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-07-26 16:32:45 +08:00
Code Issues Packages Projects Releases Wiki Activity

Cleanups.

Browse Source
This commit is contained in:
Chris Johns 2016-01-27 09:38:16 +11:00 committed by Amar Takhar
parent 66220bcbd7
commit 1a72a9806f
6 changed files with 729 additions and 721 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
c_user/interrupt_manager.rst
View File

@ -266,14 +266,14 @@ INTERRUPT_CATCH - Establish an ISR
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
ISR established successfully
.. list-table::
``RTEMS_INVALID_NUMBER``
illegal vector number
``RTEMS_INVALID_ADDRESS``
illegal ISR entry point or invalid ``old_isr_handler``
* - ``RTEMS_SUCCESSFUL``
- ISR established successfully
* - ``RTEMS_INVALID_NUMBER``
- illegal vector number
* - ``RTEMS_INVALID_ADDRESS``
- illegal ISR entry point or invalid ``old_isr_handler``
**DESCRIPTION:**

6
c_user/key_concepts.rst
View File

@ -262,8 +262,8 @@ large.
The rate monotonic scheduling algorithm is a hard real-time scheduling
methodology. This methodology provides rules which allows one to guarantee
that a set of independent periodic tasks will always meet their deadlines -
even under transient overload conditions. The rate monotonic manager provides
that a set of independent periodic tasks will always meet their deadlines even
under transient overload conditions. The rate monotonic manager provides
directives built upon the Clock Manager's interval timer support routines.
Interval timing is not sufficient for the many applications which require that
@ -274,7 +274,7 @@ request to delay until midnight on New Year's Eve before lowering the ball at
Times Square. The data type ``rtems_time_of_day`` is used to specify calendar
time in RTEMS services. See `Time and Date Data Structures`_
... index:: rtems_time_of_day
.. index:: rtems_time_of_day
Obviously, the directives which use intervals or wall time cannot operate
without some external mechanism which provides a periodic clock tick. This

122
c_user/rate_monotonic_manager.rst
View File

@ -479,14 +479,14 @@ monotonic period will be returned. The following table details the
relationship between the period's status and the directive status code returned
by the ``rtems_rate_monotonic_period`` directive:
``RTEMS_SUCCESSFUL``
period is running
.. list-table::
``RTEMS_TIMEOUT``
period has expired
``RTEMS_NOT_DEFINED``
period has never been initiated
* - ``RTEMS_SUCCESSFUL``
- period is running
* - ``RTEMS_TIMEOUT``
- period has expired
* - ``RTEMS_NOT_DEFINED``
- period has never been initiated
Obtaining the status of a rate monotonic period does not alter the state or
length of that period.
@ -655,14 +655,14 @@ RATE_MONOTONIC_CREATE - Create a rate monotonic period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
rate monotonic period created successfully
.. list-table::
``RTEMS_INVALID_NAME``
invalid period name
``RTEMS_TOO_MANY``
too many periods created
* - ``RTEMS_SUCCESSFUL``
- rate monotonic period created successfully
* - ``RTEMS_INVALID_NAME``
- invalid period name
* - ``RTEMS_TOO_MANY``
- too many periods created
**DESCRIPTION:**
@ -696,11 +696,12 @@ RATE_MONOTONIC_IDENT - Get ID of a period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period identified successfully
.. list-table::
``RTEMS_INVALID_NAME``
period name not found
* - ``RTEMS_SUCCESSFUL``
- period identified successfully
* - ``RTEMS_INVALID_NAME``
- period name not found
**DESCRIPTION:**
@ -732,14 +733,14 @@ RATE_MONOTONIC_CANCEL - Cancel a period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period canceled successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid rate monotonic period id
``RTEMS_NOT_OWNER_OF_RESOURCE``
rate monotonic period not created by calling task
* - ``RTEMS_SUCCESSFUL``
- period canceled successfully
* - ``RTEMS_INVALID_ID``
- invalid rate monotonic period id
* - ``RTEMS_NOT_OWNER_OF_RESOURCE``
- rate monotonic period not created by calling task
**DESCRIPTION:**
@ -771,11 +772,12 @@ RATE_MONOTONIC_DELETE - Delete a rate monotonic period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period deleted successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid rate monotonic period id
* - ``RTEMS_SUCCESSFUL``
- period deleted successfully
* - ``RTEMS_INVALID_ID``
- invalid rate monotonic period id
**DESCRIPTION:**
@ -811,21 +813,18 @@ RATE_MONOTONIC_PERIOD - Conclude current/Start next period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period initiated successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid rate monotonic period id
``RTEMS_NOT_OWNER_OF_RESOURCE``
period not created by calling task
``RTEMS_NOT_DEFINED``
period has never been initiated (only possible when period is set to
PERIOD_STATUS)
``RTEMS_TIMEOUT``
period has expired
* - ``RTEMS_SUCCESSFUL``
- period initiated successfully
* - ``RTEMS_INVALID_ID``
- invalid rate monotonic period id
* - ``RTEMS_NOT_OWNER_OF_RESOURCE``
- period not created by calling task
* - ``RTEMS_NOT_DEFINED``
- period has never been initiated (only possible when period is set to PERIOD_STATUS)
* - ``RTEMS_TIMEOUT``
- period has expired
**DESCRIPTION:**
@ -863,14 +862,14 @@ RATE_MONOTONIC_GET_STATUS - Obtain status from a period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period initiated successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid rate monotonic period id
``RTEMS_INVALID_ADDRESS``
invalid address of status
* - ``RTEMS_SUCCESSFUL``
- period initiated successfully
* - ``RTEMS_INVALID_ID``
- invalid rate monotonic period id
* - ``RTEMS_INVALID_ADDRESS``
- invalid address of status
**DESCRIPTION:**
@ -926,14 +925,14 @@ RATE_MONOTONIC_GET_STATISTICS - Obtain statistics from a period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period initiated successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid rate monotonic period id
``RTEMS_INVALID_ADDRESS``
invalid address of statistics
* - ``RTEMS_SUCCESSFUL``
- period initiated successfully
* - ``RTEMS_INVALID_ID``
- invalid rate monotonic period id
* - ``RTEMS_INVALID_ADDRESS``
- invalid address of statistics
**DESCRIPTION:**
@ -993,11 +992,12 @@ RATE_MONOTONIC_RESET_STATISTICS - Reset statistics for a period
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
period initiated successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid rate monotonic period id
* - ``RTEMS_SUCCESSFUL``
- period initiated successfully
* - ``RTEMS_INVALID_ID``
- invalid rate monotonic period id
**DESCRIPTION:**

2
c_user/rtems_data_types.rst
View File

@ -100,7 +100,6 @@ alphabetical order:
.. index:: rtems_fatal_extension
``rtems_fatal_extension``
The entry point for a fatal error user extension handler routine.
.. index:: rtems_id
@ -117,7 +116,6 @@ alphabetical order:
.. index:: rtems_interrupt_level
``rtems_interrupt_level``
The data structure used with the ``rtems_interrupt_disable``,
``rtems_interrupt_enable``, and ``rtems_interrupt_flash`` routines. This
data type is CPU dependent and usually corresponds to the contents of the

1126
c_user/semaphore_manager.rst
View File

File diff suppressed because it is too large Load Diff

180
c_user/timer_manager.rst
View File

@ -206,17 +206,16 @@ TIMER_CREATE - Create a timer
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer created successfully
.. list-table::
``RTEMS_INVALID_ADDRESS``
``id`` is NULL
``RTEMS_INVALID_NAME``
invalid timer name
``RTEMS_TOO_MANY``
too many timers created
* - ``RTEMS_SUCCESSFUL``
- timer created successfully
* - ``RTEMS_INVALID_ADDRESS``
- ``id`` is NULL
* - ``RTEMS_INVALID_NAME``
- invalid timer name
* - ``RTEMS_TOO_MANY``
- too many timers created
**DESCRIPTION:**
@ -248,14 +247,14 @@ TIMER_IDENT - Get ID of a timer
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer identified successfully
.. list-table::
``RTEMS_INVALID_ADDRESS``
``id`` is NULL
``RTEMS_INVALID_NAME``
timer name not found
* - ``RTEMS_SUCCESSFUL``
- timer identified successfully
* - ``RTEMS_INVALID_ADDRESS``
- ``id`` is NULL
* - ``RTEMS_INVALID_NAME``
- timer name not found
**DESCRIPTION:**
@ -287,11 +286,12 @@ TIMER_CANCEL - Cancel a timer
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer canceled successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid timer id
* - ``RTEMS_SUCCESSFUL``
- timer canceled successfully
* - ``RTEMS_INVALID_ID``
- invalid timer id
**DESCRIPTION:**
@ -321,11 +321,12 @@ TIMER_DELETE - Delete a timer
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer deleted successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid timer id
* - ``RTEMS_SUCCESSFUL``
- timer deleted successfully
* - ``RTEMS_INVALID_ID``
- invalid timer id
**DESCRIPTION:**
@ -360,17 +361,16 @@ TIMER_FIRE_AFTER - Fire timer after interval
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer initiated successfully
.. list-table::
``RTEMS_INVALID_ADDRESS``
``routine`` is NULL
``RTEMS_INVALID_ID``
invalid timer id
``RTEMS_INVALID_NUMBER``
invalid interval
* - ``RTEMS_SUCCESSFUL``
- timer initiated successfully
* - ``RTEMS_INVALID_ADDRESS``
- ``routine`` is NULL
* - ``RTEMS_INVALID_ID``
- invalid timer id
* - ``RTEMS_INVALID_NUMBER``
- invalid interval
**DESCRIPTION:**
@ -404,23 +404,20 @@ TIMER_FIRE_WHEN - Fire timer when specified
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer initiated successfully
.. list-table::
``RTEMS_INVALID_ADDRESS``
``routine`` is NULL
``RTEMS_INVALID_ADDRESS``
``wall_time`` is NULL
``RTEMS_INVALID_ID``
invalid timer id
``RTEMS_NOT_DEFINED``
system date and time is not set
``RTEMS_INVALID_CLOCK``
invalid time of day
* - ``RTEMS_SUCCESSFUL``
- timer initiated successfully
* - ``RTEMS_INVALID_ADDRESS``
- ``routine`` is NULL
* - ``RTEMS_INVALID_ADDRESS``
- ``wall_time`` is NULL
* - ``RTEMS_INVALID_ID``
- invalid timer id
* - ``RTEMS_NOT_DEFINED``
- system date and time is not set
* - ``RTEMS_INVALID_CLOCK``
- invalid time of day
**DESCRIPTION:**
@ -454,11 +451,12 @@ TIMER_INITIATE_SERVER - Initiate server for task-based timers
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
Timer Server initiated successfully
.. list-table::
``RTEMS_TOO_MANY``
too many tasks created
* - ``RTEMS_SUCCESSFUL``
- Timer Server initiated successfully
* - ``RTEMS_TOO_MANY``
- too many tasks created
**DESCRIPTION:**
@ -498,20 +496,18 @@ TIMER_SERVER_FIRE_AFTER - Fire task-based timer after interval
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer initiated successfully
.. list-table::
``RTEMS_INVALID_ADDRESS``
``routine`` is NULL
``RTEMS_INVALID_ID``
invalid timer id
``RTEMS_INVALID_NUMBER``
invalid interval
``RTEMS_INCORRECT_STATE``
Timer Server not initiated
* - ``RTEMS_SUCCESSFUL``
- timer initiated successfully
* - ``RTEMS_INVALID_ADDRESS``
- ``routine`` is NULL
* - ``RTEMS_INVALID_ID``
- invalid timer id
* - ``RTEMS_INVALID_NUMBER``
- invalid interval
* - ``RTEMS_INCORRECT_STATE``
- Timer Server not initiated
**DESCRIPTION:**
@ -548,26 +544,22 @@ TIMER_SERVER_FIRE_WHEN - Fire task-based timer when specified
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer initiated successfully
.. list-table::
``RTEMS_INVALID_ADDRESS``
``routine`` is NULL
``RTEMS_INVALID_ADDRESS``
``wall_time`` is NULL
``RTEMS_INVALID_ID``
invalid timer id
``RTEMS_NOT_DEFINED``
system date and time is not set
``RTEMS_INVALID_CLOCK``
invalid time of day
``RTEMS_INCORRECT_STATE``
Timer Server not initiated
* - ``RTEMS_SUCCESSFUL``
- timer initiated successfully
* - ``RTEMS_INVALID_ADDRESS``
- ``routine`` is NULL
* - ``RTEMS_INVALID_ADDRESS``
- ``wall_time`` is NULL
* - ``RTEMS_INVALID_ID``
- invalid timer id
* - ``RTEMS_NOT_DEFINED``
- system date and time is not set
* - ``RTEMS_INVALID_CLOCK``
- invalid time of day
* - ``RTEMS_INCORRECT_STATE``
- Timer Server not initiated
**DESCRIPTION:**
@ -601,14 +593,14 @@ TIMER_RESET - Reset an interval timer
**DIRECTIVE STATUS CODES:**
``RTEMS_SUCCESSFUL``
timer reset successfully
.. list-table::
``RTEMS_INVALID_ID``
invalid timer id
``RTEMS_NOT_DEFINED``
attempted to reset a when or newly created timer
* - ``RTEMS_SUCCESSFUL``
- timer reset successfully
* - ``RTEMS_INVALID_ID``
- invalid timer id
* - ``RTEMS_NOT_DEFINED``
- attempted to reset a when or newly created timer
**DESCRIPTION:**