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

87 lines
1.8 KiB
Plaintext
Raw Normal View History

kconfig: untangle ordering and dependencies There are two major issues with the kconfig: () Some of the config options have incorrect dependencies inside help under menuconfig. For example, CONFIG_GPIO depends on BOARD_GALILEO. () Since the SoC and board specific kconfig files are parsed first, the help screen would say, for example, CONFIG_SPI is defined at arch/arm/soc/fsl_frdm_k64f/Kconfig. This is incorrect because the actual config is defined in drivers/spi/Kconfig. These cause great confusion to users of menuconfig/xconfig. To fix these, the SoC and board defaults are now to be parsed last. Note that the position swapping of defaults in this patch is due to the fact the the default parsed last will be used. And, spi_test is broken due to the fact that it requires CONFIG_SPI_INTEL_PORT_1, but never enables it anywhere. This is bypassed for now. Origin: refactored and edited from existing files Change-Id: I2a4b1ae5be4d27e68c960aa47d91ef350f2d500f Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-26 05:30:50 +08:00
# Kconfig - TI LM3S6965 platform configuration options
#
# Copyright (c) 2014-2015 Wind River Systems, Inc.
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#
if SOC_TI_LM3S6965
config SOC
default ti_lm3s6965
config SRAM_BASE_ADDRESS
default 0x20000000
config FLASH_BASE_ADDRESS
default 0x00000000
config NUM_IRQ_PRIO_BITS
int
default 3
config NUM_IRQS
int
# must be >= the highest interrupt number used
# - include the UART interrupts
default 34
config SYS_CLOCK_HW_CYCLES_PER_SEC
int
default 12000000
if UART_STELLARIS
config UART_STELLARIS_PORT_0
def_bool y
if UART_STELLARIS_PORT_0
config UART_STELLARIS_PORT_0_IRQ_PRI
default 3
config UART_STELLARIS_PORT_0_BAUD_RATE
default 115200
endif
config UART_STELLARIS_PORT_1
def_bool y
if UART_STELLARIS_PORT_1
config UART_STELLARIS_PORT_1_IRQ_PRI
default 3
config UART_STELLARIS_PORT_1_BAUD_RATE
default 115200
endif
config UART_STELLARIS_PORT_2
def_bool y
if UART_STELLARIS_PORT_2
config UART_STELLARIS_PORT_2_IRQ_PRI
default 3
config UART_STELLARIS_PORT_2_BAUD_RATE
default 115200
endif
endif # UART_STELLARIS
config BLUETOOTH_UART_ON_DEV_NAME
default "UART_1" if BLUETOOTH_UART
config UART_PIPE_ON_DEV_NAME
default "UART_2" if UART_PIPE
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
config BLUETOOTH_MONITOR_ON_DEV_NAME
default "UART_2" if BLUETOOTH_DEBUG_MONITOR
kconfig: untangle ordering and dependencies There are two major issues with the kconfig: () Some of the config options have incorrect dependencies inside help under menuconfig. For example, CONFIG_GPIO depends on BOARD_GALILEO. () Since the SoC and board specific kconfig files are parsed first, the help screen would say, for example, CONFIG_SPI is defined at arch/arm/soc/fsl_frdm_k64f/Kconfig. This is incorrect because the actual config is defined in drivers/spi/Kconfig. These cause great confusion to users of menuconfig/xconfig. To fix these, the SoC and board defaults are now to be parsed last. Note that the position swapping of defaults in this patch is due to the fact the the default parsed last will be used. And, spi_test is broken due to the fact that it requires CONFIG_SPI_INTEL_PORT_1, but never enables it anywhere. This is bypassed for now. Origin: refactored and edited from existing files Change-Id: I2a4b1ae5be4d27e68c960aa47d91ef350f2d500f Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2016-03-26 05:30:50 +08:00
endif