mirror of
https://github.com/apache/nuttx.git
synced 2026-06-02 01:21:26 +08:00
Cosmetic changed, updated README files, improved comments
This commit is contained in:
@@ -54,6 +54,27 @@
|
|||||||
* logic when the interval timer expires.
|
* logic when the interval timer expires.
|
||||||
*
|
*
|
||||||
****************************************************************************/
|
****************************************************************************/
|
||||||
|
/****************************************************************************
|
||||||
|
* SAMA5 Timer Usage
|
||||||
|
*
|
||||||
|
* This current implementation uses two timers: A one-shot timer to provide
|
||||||
|
* the timed events and a free running timer to provide the current time.
|
||||||
|
* Since timers are a limited resource, that could be an issue on some
|
||||||
|
* systems.
|
||||||
|
*
|
||||||
|
* We could do the job with a single timer if we were to keep the single
|
||||||
|
* timer in a free-running at all times. The SAMA5 timer/counters have
|
||||||
|
* 32-bit counters with the capability to generate a compare interrupt when
|
||||||
|
* the timer matches a compare value but also to continue counting without
|
||||||
|
* stopping (giving another, different interrupt when the timer rolls over
|
||||||
|
* from 0xffffffff to zero). So we could potentially just set the compare
|
||||||
|
* at the number of ticks you want PLUS the current value of timer. Then
|
||||||
|
* you could have both with a single timer: An interval timer and a free-
|
||||||
|
* running counter with the same timer!
|
||||||
|
*
|
||||||
|
* Patches are welcome!
|
||||||
|
*
|
||||||
|
****************************************************************************/
|
||||||
|
|
||||||
/****************************************************************************
|
/****************************************************************************
|
||||||
* Included Files
|
* Included Files
|
||||||
|
|||||||
@@ -2332,6 +2332,8 @@ TRNG and /dev/random
|
|||||||
Tickless OS
|
Tickless OS
|
||||||
===========
|
===========
|
||||||
|
|
||||||
|
Background
|
||||||
|
----------
|
||||||
By default, a NuttX configuration uses a periodic timer interrupt that
|
By default, a NuttX configuration uses a periodic timer interrupt that
|
||||||
drives all system timing. The timer is provided by architecture-specifi
|
drives all system timing. The timer is provided by architecture-specifi
|
||||||
code that calls into NuttX at a rate controlled by CONFIG_USEC_PER_TICK.
|
code that calls into NuttX at a rate controlled by CONFIG_USEC_PER_TICK.
|
||||||
@@ -2368,6 +2370,8 @@ Tickless OS
|
|||||||
OS event will occur, program the interval time and wait for it to fire.
|
OS event will occur, program the interval time and wait for it to fire.
|
||||||
When the interval time fires, then the scheduled activity is performed.
|
When the interval time fires, then the scheduled activity is performed.
|
||||||
|
|
||||||
|
Configuration
|
||||||
|
-------------
|
||||||
The following configuration options will enable support for the Tickless
|
The following configuration options will enable support for the Tickless
|
||||||
OS for the SAMA5D platforms using TC0 channels 0-3 (other timers or
|
OS for the SAMA5D platforms using TC0 channels 0-3 (other timers or
|
||||||
timer channels could be used making the obvious substitutions):
|
timer channels could be used making the obvious substitutions):
|
||||||
@@ -2385,6 +2389,25 @@ Tickless OS
|
|||||||
CONFIG_SAMA5_TICKLESS_FREERUN=1 : Selects TC0 channel 1 for the free-
|
CONFIG_SAMA5_TICKLESS_FREERUN=1 : Selects TC0 channel 1 for the free-
|
||||||
: running timer
|
: running timer
|
||||||
|
|
||||||
|
SAMA5 Timer Usage
|
||||||
|
-----------------
|
||||||
|
This current implementation uses two timers: A one-shot timer to
|
||||||
|
provide the timed events and a free running timer to provide the current
|
||||||
|
time. Since timers are a limited resource, that could be an issue on
|
||||||
|
some systems.
|
||||||
|
|
||||||
|
We could do the job with a single timer if we were to keep the single
|
||||||
|
timer in a free-running at all times. The SAMA5 timer/counters have
|
||||||
|
32-bit counters with the capability to generate a compare interrupt when
|
||||||
|
the timer matches a compare value but also to continue counting without
|
||||||
|
stopping (giving another, different interrupt when the timer rolls over
|
||||||
|
from 0xffffffff to zero). So we could potentially just set the compare
|
||||||
|
at the number of ticks you want PLUS the current value of timer. Then
|
||||||
|
you could have both with a single timer: An interval timer and a free-
|
||||||
|
running counter with the same timer!
|
||||||
|
|
||||||
|
Patches are welcome!
|
||||||
|
|
||||||
I2S Audio Support
|
I2S Audio Support
|
||||||
=================
|
=================
|
||||||
|
|
||||||
|
|||||||
@@ -2648,6 +2648,8 @@ Touchscreen Testing
|
|||||||
Tickless OS
|
Tickless OS
|
||||||
===========
|
===========
|
||||||
|
|
||||||
|
Background
|
||||||
|
----------
|
||||||
By default, a NuttX configuration uses a periodic timer interrupt that
|
By default, a NuttX configuration uses a periodic timer interrupt that
|
||||||
drives all system timing. The timer is provided by architecture-specifi
|
drives all system timing. The timer is provided by architecture-specifi
|
||||||
code that calls into NuttX at a rate controlled by CONFIG_USEC_PER_TICK.
|
code that calls into NuttX at a rate controlled by CONFIG_USEC_PER_TICK.
|
||||||
@@ -2684,6 +2686,8 @@ Tickless OS
|
|||||||
OS event will occur, program the interval time and wait for it to fire.
|
OS event will occur, program the interval time and wait for it to fire.
|
||||||
When the interval time fires, then the scheduled activity is performed.
|
When the interval time fires, then the scheduled activity is performed.
|
||||||
|
|
||||||
|
Configuration
|
||||||
|
-------------
|
||||||
The following configuration options will enable support for the Tickless
|
The following configuration options will enable support for the Tickless
|
||||||
OS for the SAMA5D platforms using TC0 channels 0-3 (other timers or
|
OS for the SAMA5D platforms using TC0 channels 0-3 (other timers or
|
||||||
timer channels could be used making the obvious substitutions):
|
timer channels could be used making the obvious substitutions):
|
||||||
@@ -2701,6 +2705,25 @@ Tickless OS
|
|||||||
CONFIG_SAMA5_TICKLESS_FREERUN=1 : Selects TC0 channel 1 for the free-
|
CONFIG_SAMA5_TICKLESS_FREERUN=1 : Selects TC0 channel 1 for the free-
|
||||||
: running timer
|
: running timer
|
||||||
|
|
||||||
|
SAMA5 Timer Usage
|
||||||
|
-----------------
|
||||||
|
This current implementation uses two timers: A one-shot timer to
|
||||||
|
provide the timed events and a free running timer to provide the current
|
||||||
|
time. Since timers are a limited resource, that could be an issue on
|
||||||
|
some systems.
|
||||||
|
|
||||||
|
We could do the job with a single timer if we were to keep the single
|
||||||
|
timer in a free-running at all times. The SAMA5 timer/counters have
|
||||||
|
32-bit counters with the capability to generate a compare interrupt when
|
||||||
|
the timer matches a compare value but also to continue counting without
|
||||||
|
stopping (giving another, different interrupt when the timer rolls over
|
||||||
|
from 0xffffffff to zero). So we could potentially just set the compare
|
||||||
|
at the number of ticks you want PLUS the current value of timer. Then
|
||||||
|
you could have both with a single timer: An interval timer and a free-
|
||||||
|
running counter with the same timer!
|
||||||
|
|
||||||
|
Patches are welcome!
|
||||||
|
|
||||||
OV2640 Camera Interface
|
OV2640 Camera Interface
|
||||||
=======================
|
=======================
|
||||||
|
|
||||||
|
|||||||
@@ -3112,6 +3112,8 @@ TM7000 LCD/Touchscreen
|
|||||||
Tickless OS
|
Tickless OS
|
||||||
===========
|
===========
|
||||||
|
|
||||||
|
Background
|
||||||
|
----------
|
||||||
By default, a NuttX configuration uses a periodic timer interrupt that
|
By default, a NuttX configuration uses a periodic timer interrupt that
|
||||||
drives all system timing. The timer is provided by architecture-specifi
|
drives all system timing. The timer is provided by architecture-specifi
|
||||||
code that calls into NuttX at a rate controlled by CONFIG_USEC_PER_TICK.
|
code that calls into NuttX at a rate controlled by CONFIG_USEC_PER_TICK.
|
||||||
@@ -3148,6 +3150,8 @@ Tickless OS
|
|||||||
OS event will occur, program the interval time and wait for it to fire.
|
OS event will occur, program the interval time and wait for it to fire.
|
||||||
When the interval time fires, then the scheduled activity is performed.
|
When the interval time fires, then the scheduled activity is performed.
|
||||||
|
|
||||||
|
Configuration
|
||||||
|
-------------
|
||||||
The following configuration options will enable support for the Tickless
|
The following configuration options will enable support for the Tickless
|
||||||
OS for the SAMA5D platforms using TC0 channels 0-3 (other timers or
|
OS for the SAMA5D platforms using TC0 channels 0-3 (other timers or
|
||||||
timer channels could be used making the obvious substitutions):
|
timer channels could be used making the obvious substitutions):
|
||||||
@@ -3165,6 +3169,25 @@ Tickless OS
|
|||||||
CONFIG_SAMA5_TICKLESS_FREERUN=1 : Selects TC0 channel 1 for the free-
|
CONFIG_SAMA5_TICKLESS_FREERUN=1 : Selects TC0 channel 1 for the free-
|
||||||
: running timer
|
: running timer
|
||||||
|
|
||||||
|
SAMA5 Timer Usage
|
||||||
|
-----------------
|
||||||
|
This current implementation uses two timers: A one-shot timer to
|
||||||
|
provide the timed events and a free running timer to provide the current
|
||||||
|
time. Since timers are a limited resource, that could be an issue on
|
||||||
|
some systems.
|
||||||
|
|
||||||
|
We could do the job with a single timer if we were to keep the single
|
||||||
|
timer in a free-running at all times. The SAMA5 timer/counters have
|
||||||
|
32-bit counters with the capability to generate a compare interrupt when
|
||||||
|
the timer matches a compare value but also to continue counting without
|
||||||
|
stopping (giving another, different interrupt when the timer rolls over
|
||||||
|
from 0xffffffff to zero). So we could potentially just set the compare
|
||||||
|
at the number of ticks you want PLUS the current value of timer. Then
|
||||||
|
you could have both with a single timer: An interval timer and a free-
|
||||||
|
running counter with the same timer!
|
||||||
|
|
||||||
|
Patches are welcome!
|
||||||
|
|
||||||
SAMA4D4-EK Configuration Options
|
SAMA4D4-EK Configuration Options
|
||||||
=================================
|
=================================
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user