93b0ced44b
The initialization procedures need to be called in the following order: - basic hardware initialization; - devices initialization; - hardware clock initialization, that the kernel needs to run the kernel server. This way, the board initialization routines is placed to the pure_early_init level to make sure it runs first, all device initialization procedures run at pure_init level, so they are initialized early enough to be used for debugging if needed. Hardware clock initialization is placed on nano_early_init level to make sure hardware clock is initialized just before the kernel server starts. Change-Id: Ieecf9f0252c47c621b7208969687dc1113fc2ad0 Signed-off-by: Dmitriy Korovkin <dmitriy.korovkin@windriver.com>
52 lines
2.3 KiB
C
52 lines
2.3 KiB
C
/* initialize system clock driver */
|
|
|
|
/*
|
|
* Copyright (c) 2015 Wind River Systems, Inc.
|
|
*
|
|
* Redistribution and use in source and binary forms, with or without
|
|
* modification, are permitted provided that the following conditions are met:
|
|
*
|
|
* 1) Redistributions of source code must retain the above copyright notice,
|
|
* this list of conditions and the following disclaimer.
|
|
*
|
|
* 2) Redistributions in binary form must reproduce the above copyright notice,
|
|
* this list of conditions and the following disclaimer in the documentation
|
|
* and/or other materials provided with the distribution.
|
|
*
|
|
* 3) Neither the name of Wind River Systems nor the names of its contributors
|
|
* may be used to endorse or promote products derived from this software without
|
|
* specific prior written permission.
|
|
*
|
|
* THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
|
|
* AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
|
|
* LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
|
|
* CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
|
|
* SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
|
|
* INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
|
|
* CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
|
|
* ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
|
* POSSIBILITY OF SUCH DAMAGE.
|
|
*/
|
|
|
|
/*
|
|
DESCRIPTION
|
|
Initializing the timer driver is done in this module to reduce code duplication.
|
|
Although both nanokernel and microkernel systems initialize the timer driver at
|
|
the same point, the two systems differ in when the system can begin to process
|
|
system clock ticks. A nanokernel system can process system clock ticks once
|
|
the driver has initialized. However, in a microkernel system all system clock
|
|
ticks are deferred (and stored on the kernel server command stack) until the
|
|
kernel server fiber starts and begins processing any queued ticks.
|
|
*/
|
|
|
|
#include <nanokernel.h>
|
|
#include <init.h>
|
|
#include <drivers/system_timer.h>
|
|
|
|
DECLARE_DEVICE_INIT_CONFIG(sys_clock, "sys_clock",
|
|
_sys_clock_driver_init, NULL);
|
|
|
|
nano_late_init(sys_clock, NULL);
|