2015-11-20 21:37:13 +08:00
|
|
|
|
2016-08-30 20:41:04 +08:00
|
|
|
if BOARD_QUARK_SE_C1000_DEVBOARD
|
2015-11-20 21:37:13 +08:00
|
|
|
|
|
|
|
|
config BOARD
|
2016-08-30 20:41:04 +08:00
|
|
|
default "quark_se_c1000_devboard"
|
2015-11-20 21:37:13 +08:00
|
|
|
|
2017-08-02 19:32:00 +08:00
|
|
|
|
2016-05-20 23:39:56 +08:00
|
|
|
config UART_QMSI_0_HW_FC
|
|
|
|
|
def_bool y
|
|
|
|
|
|
2017-08-02 19:32:00 +08:00
|
|
|
|
kernel: tickless: Add tickless kernel support
Adds event based scheduling logic to the kernel. Updates
management of timeouts, timers, idling etc. based on
time tracked at events rather than periodic ticks. Provides
interfaces for timers to announce and get next timer expiry
based on kernel scheduling decisions involving time slicing
of threads, timeouts and idling. Uses wall time units instead
of ticks in all scheduling activities.
The implementation involves changes in the following areas
1. Management of time in wall units like ms/us instead of ticks
The existing implementation already had an option to configure
number of ticks in a second. The new implementation builds on
top of that feature and provides option to set the size of the
scheduling granurality to mili seconds or micro seconds. This
allows most of the current implementation to be reused. Due to
this re-use and co-existence with tick based kernel, the names
of variables may contain the word "tick". However, in the
tickless kernel implementation, it represents the currently
configured time unit, which would be be mili seconds or
micro seconds. The APIs that take time as a parameter are not
impacted and they continue to pass time in mili seconds.
2. Timers would not be programmed in periodic mode
generating ticks. Instead they would be programmed in one
shot mode to generate events at the time the kernel scheduler
needs to gain control for its scheduling activities like
timers, timeouts, time slicing, idling etc.
3. The scheduler provides interfaces that the timer drivers
use to announce elapsed time and get the next time the scheduler
needs a timer event. It is possible that the scheduler may not
need another timer event, in which case the system would wait
for a non-timer event to wake it up if it is idling.
4. New APIs are defined to be implemented by timer drivers. Also
they need to handler timer events differently. These changes
have been done in the HPET timer driver. In future other timers
that support tickles kernel should implement these APIs as well.
These APIs are to re-program the timer, update and announce
elapsed time.
5. Philosopher and timer_api applications have been enabled to
test tickless kernel. Separate configuration files are created
which define the necessary CONFIG flags. Run these apps using
following command
make pristine && make BOARD=qemu_x86 CONF_FILE=prj_tickless.conf qemu
Jira: ZEP-339 ZEP-1946 ZEP-948
Change-Id: I7d950c31bf1ff929a9066fad42c2f0559a2e5983
Signed-off-by: Ramesh Thomas <ramesh.thomas@intel.com>
2017-02-06 11:37:19 +08:00
|
|
|
if SYS_POWER_MANAGEMENT
|
|
|
|
|
|
|
|
|
|
config BUSY_WAIT_USES_ALTERNATE_CLOCK
|
|
|
|
|
default y
|
|
|
|
|
|
|
|
|
|
endif
|
|
|
|
|
|
2017-08-09 14:21:11 +08:00
|
|
|
config BT_MONITOR_ON_DEV_NAME
|
|
|
|
|
default UART_QMSI_1_NAME if BT_DEBUG_MONITOR
|
2017-08-02 19:32:00 +08:00
|
|
|
|
2017-03-23 23:48:34 +08:00
|
|
|
if IEEE802154_CC2520
|
2016-01-22 20:29:30 +08:00
|
|
|
|
|
|
|
|
config SPI
|
|
|
|
|
def_bool y
|
|
|
|
|
config GPIO
|
|
|
|
|
def_bool y
|
|
|
|
|
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_SPI_DRV_NAME
|
2016-05-08 06:57:14 +08:00
|
|
|
default SPI_1_NAME
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_SPI_FREQ
|
2016-02-18 18:49:45 +08:00
|
|
|
default 4
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_SPI_SLAVE
|
2016-01-22 20:29:30 +08:00
|
|
|
default 1
|
2016-02-03 16:55:39 +08:00
|
|
|
|
2016-03-26 05:30:50 +08:00
|
|
|
|
2016-04-26 21:37:02 +08:00
|
|
|
if GPIO_QMSI
|
2016-03-26 05:30:50 +08:00
|
|
|
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_GPIO_0_NAME
|
2016-05-25 07:17:13 +08:00
|
|
|
default GPIO_QMSI_0_NAME
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_GPIO_1_NAME
|
2016-10-02 22:23:26 +08:00
|
|
|
default GPIO_QMSI_1_NAME
|
2016-03-26 05:30:50 +08:00
|
|
|
|
2016-04-26 21:37:02 +08:00
|
|
|
endif # GPIO_QMSI
|
2016-02-03 16:55:39 +08:00
|
|
|
|
|
|
|
|
if SPI_QMSI
|
2016-05-08 06:57:14 +08:00
|
|
|
config SPI_CS_GPIO
|
2016-02-03 16:55:39 +08:00
|
|
|
def_bool y
|
2016-05-08 06:57:14 +08:00
|
|
|
config SPI_1_CS_GPIO_PORT
|
2016-02-03 16:55:39 +08:00
|
|
|
default GPIO_QMSI_0_NAME
|
2016-05-08 06:57:14 +08:00
|
|
|
config SPI_1_CS_GPIO_PIN
|
2016-02-03 16:55:39 +08:00
|
|
|
default 11
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_GPIO_0_NAME
|
2016-05-25 07:17:13 +08:00
|
|
|
string
|
|
|
|
|
default GPIO_QMSI_0_NAME
|
2017-02-06 18:49:16 +08:00
|
|
|
config IEEE802154_CC2520_GPIO_1_NAME
|
2016-05-25 07:17:13 +08:00
|
|
|
string
|
2016-10-02 22:23:26 +08:00
|
|
|
default GPIO_QMSI_1_NAME
|
2016-02-03 16:55:39 +08:00
|
|
|
endif
|
|
|
|
|
|
2017-03-23 23:48:34 +08:00
|
|
|
endif # IEEE802154_CC2520
|
2016-01-22 20:29:30 +08:00
|
|
|
|
2016-09-09 22:39:47 +08:00
|
|
|
endif # BOARD_QUARK_SE_C1000_DEVBOARD
|