[PATCH 02/12] score: Add ticks per second to configuration

[Chris Johns]

On 8/04/2016 4:49 PM, Sebastian Huber wrote:
> This avoids the calculation of this value at run-time, similar to
> rtems_configuration_get_nanoseconds_per_tick().
>
> Delete TOD_TICKS_PER_SECOND and replace it with
> rtems_configuration_get_ticks_per_second().
> --- a/cpukit/sapi/include/confdefs.h
> +++ b/cpukit/sapi/include/confdefs.h
> @@ -3413,6 +3413,7 @@ extern rtems_initialization_tasks_table Initialization_tasks[];
>       CONFIGURE_MAXIMUM_POSIX_KEY_VALUE_PAIRS,  /*   enabled */
>       CONFIGURE_MICROSECONDS_PER_TICK,          /* microseconds per clock tick */
>       1000 * CONFIGURE_MICROSECONDS_PER_TICK,   /* nanoseconds per clock tick */
> +    1000000 / CONFIGURE_MICROSECONDS_PER_TICK,/* ticks per second */
>       CONFIGURE_TICKS_PER_TIMESLICE,            /* ticks per timeslice quantum */
>       CONFIGURE_IDLE_TASK_BODY,                 /* user's IDLE task */
>       CONFIGURE_IDLE_TASK_STACK_SIZE,           /* IDLE task stack size */

I assume the microsecond, nanosecond and tick per sec values all need to 
agree.

Does anything check this is the case and raise a fatal error if they do not?

Chris