OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/arch/x86/soc/atom/Kconfig.defconfig

62 lines
856 B
Plaintext
Raw Normal View History

Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
# Kconfig - ATOM SoC configuration options
#
# Copyright (c) 2014-2015 Wind River Systems, Inc.
#
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
# SPDX-License-Identifier: Apache-2.0
Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
#
Use SoC instead of platform. Change terminology and use SoC instead of platform. An SoC provides features and default configurations available with an SoC. A board implements the SoC and adds more features and IP block specific to the board to extend the SoC functionality such as sensors and debugging features. Change-Id: I15e8d78a6d4ecd5cfb3bc25ced9ba77e5ea1122f Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 21:54:35 +08:00
if SOC_ATOM
Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
Use SoC instead of platform. Change terminology and use SoC instead of platform. An SoC provides features and default configurations available with an SoC. A board implements the SoC and adds more features and IP block specific to the board to extend the SoC functionality such as sensors and debugging features. Change-Id: I15e8d78a6d4ecd5cfb3bc25ced9ba77e5ea1122f Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 21:54:35 +08:00
config SOC
soc: defconfig: Consistently quote string defaults In preparation for introducing a warning. Unquoted string defaults work through a quirk of Kconfig (undefined symbols get their name as their string value), but look confusing. It's done inconsistently now too. Suggested by Kumar Gala. Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2018-05-26 03:19:21 +08:00
default "atom"
Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
config SYS_CLOCK_HW_CYCLES_PER_SEC
default 150000000 if LOAPIC_TIMER
default 25000000 if HPET_TIMER
Kconfig: CPU_MIGHT_SUPPORT_CLFLUSH removal. Remove CPU_MIGHT_SUPPORT_CLFLUSH as excessive. Removal the flag requires adding per-SoC cnfiguration, as some Quark models support clflush instruction, but some do not, even on compiler level. Change-Id: I655cba00c629db55d1813c199a2fe08b2d60ef4f Signed-off-by: Dmitriy Korovkin <dmitriy.korovkin@windriver.com>
2016-03-01 00:12:40 +08:00
config CLFLUSH_DETECT
def_bool y if CACHE_FLUSHING
Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
if UART_NS16550
config UART_NS16550_PCI
def_bool n
config UART_NS16550_PORT_0
def_bool y
if UART_NS16550_PORT_0
config UART_NS16550_PORT_0_OPTIONS
default 0
endif # UART_NS16550_PORT_0
config UART_NS16550_PORT_1
def_bool y
if UART_NS16550_PORT_1
config UART_NS16550_PORT_1_OPTIONS
default 0
endif # UART_NS16550_PORT_1
endif # UART_NS16550
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
if BT_UART
Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
if UART_PIPE
config UART_PIPE_ON_DEV_NAME
default "UART_1"
endif
Bluetooth: Kconfig: Rename CONFIG_BLUETOOTH_* to CONFIG_BT_* The API name space for Bluetooth is bt_* and BT_* so it makes sense to align the Kconfig name space with this. The additional benefit is that this also makes the names shorter. It is also in line with what Linux uses for Bluetooth Kconfig entries. Some Bluetooth-related Networking Kconfig defines are renamed as well in order to be consistent, such as NET_L2_BLUETOOTH. Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2017-08-09 14:21:11 +08:00
config BT_MONITOR_ON_DEV_NAME
default "UART_1" if BT_DEBUG_MONITOR
dts: x86: Add device tree support for atom based devices Signed-off-by: Savinay Dharmappa <savinay.dharmappa@intel.com>
2017-11-22 03:21:19 +08:00
endif
Bluetooth: Add custom "monitor" protocol logging over UART With most boards there's no simple way to get access to the HCI traffic. Simultaneously these boards only have one external UART for the console. This patch introduces a protocol which combines both normal logs and HCI logs over a single binary protocol sent over the console UART. The protocol is modeled based on the btsnoop/monitor protocols used by BlueZ, and the first tool that's able to decode this is btmon from BlueZ ("btmon --tty <tty>"). For platforms with two or more external UARTs it is still possible to use CONFIG_UART_CONSOLE as long as the UART devices used are different, however on platforms with a single external UART UART_CONSOLE should be disabled if BLUETOOTH_DEBUG_MONITOR is enabled (in this case printk/printf get encoded to the monitor protocol). Origin: Original Change-Id: I9d3997c7a06fe48e7decb212b2ac9bd8b8f9b74c Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2016-04-20 22:54:07 +08:00
Introduce the Atom SoC This is a generic Atom configuration that can be inherited by boards with Atom SoC like the minnowboard. Change-Id: I06ab999062be7811d14755fd34440dee8f8b81ed Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2015-12-17 13:03:40 +08:00
endif