diff options
author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2018-05-03 13:03:27 +0200 |
---|---|---|
committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2018-12-07 14:22:01 +0100 |
commit | 0a1f5df98e52b028bf8b4de3bf63e39702fa5f34 (patch) | |
tree | 7b3d8bfe7a9e760ee2bbb8916d3284f34edfec89 /bsps/or1k | |
parent | score: Avoid sbintime_t in API headers (diff) | |
download | rtems-0a1f5df98e52b028bf8b4de3bf63e39702fa5f34.tar.bz2 |
Simplify _CPU_Counter_difference()
In order to simplify the use of CPU counter values it is beneficial to
have monotonic increasing values within the range of the CPU counter
ticks data type, e.g. 32-bit unsigned integer. This eases the use of
CPU counter timestamps in external tools which do not know the details
of the CPU counter hardware. The CPU counter is the fastest way to get
a time on an RTEMS system.
Such a CPU counter may be also used as the timecounter. Use it on SPARC
for this purpose to simplify the clock drivers.
Update #3456.
Diffstat (limited to 'bsps/or1k')
-rw-r--r-- | bsps/or1k/generic_or1k/clock/clockdrv.c | 8 |
1 files changed, 0 insertions, 8 deletions
diff --git a/bsps/or1k/generic_or1k/clock/clockdrv.c b/bsps/or1k/generic_or1k/clock/clockdrv.c index 44365aa02c..7b8a07fd3d 100644 --- a/bsps/or1k/generic_or1k/clock/clockdrv.c +++ b/bsps/or1k/generic_or1k/clock/clockdrv.c @@ -109,14 +109,6 @@ static void generic_or1k_clock_initialize(void) rtems_timecounter_install(&or1ksim_tc); } -CPU_Counter_ticks _CPU_Counter_difference( - CPU_Counter_ticks second, - CPU_Counter_ticks first -) -{ - return second - first; -} - #define Clock_driver_support_at_tick() generic_or1k_clock_at_tick() #define Clock_driver_support_initialize_hardware() generic_or1k_clock_initialize() |