OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/boards/particle/argon/Kconfig.defconfig

12 lines
195 B
Plaintext
Raw Normal View History

kconfig: Clean up header comments and make them consistent Use this short header style in all Kconfig files: # <description> # <copyright> # <license> ... Also change all <description>s from # Kconfig[.extension] - Foo-related options to just # Foo-related options It's clear enough that it's about Kconfig. The <description> cleanup was done with this command, along with some manual cleanup (big letter at the start, etc.) git ls-files '*Kconfig*' | \ xargs sed -i -E '1 s/#\s*Kconfig[\w.-]*\s*-\s*/# /' Signed-off-by: Ulf Magnusson <Ulf.Magnusson@nordicsemi.no>
2019-11-01 20:45:29 +08:00
# Particle Argon board configuration
boards: arm: particle: refactor for commonalities Provide a dtsi file that sets up common capabilities for all Feather-based Particle Mesh devices. Provide additional dtsi files for some obvious peripheral options. Remove the xtensa esp32 image: it didn't build, and there's no indication of how the ESP32 firmware can be updated on the Argon board. Use particle_argon as the nRF52840 side of the board. Add Particle Boron support. Note that dtsi files must be replicated in each board directory until tooling supports DTS includes from a shared area. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2018-12-20 04:46:33 +08:00
# Copyright (c) 2018 Matthias Boesl
# SPDX-License-Identifier: Apache-2.0
if BOARD_PARTICLE_ARGON
boards: particle: fix BT selection When selecting BT we need to select BT_CTRL for most bluetooth samples to work correctly. Let's fix that in the board files. Fixes the following error when CONFIG_BT is selected: zephyr/drivers/bluetooth/hci/h4.c:463:30: error: ‘CONFIG_BT_UART_ON_DEV_NAME’ undeclared (first use in this function) h4_dev = device_get_binding(CONFIG_BT_UART_ON_DEV_NAME); ^~~~~~~~~~~~~~~~~~~~~~~~~~ Signed-off-by: Michael Scott <mike@foundries.io>
2019-01-27 12:03:52 +08:00
config BT_CTLR
boards: arm: nrf: Make Bluetooth optional Instead of enabling Bluetooth by default on nRF5x boards, only enable the controller if Bluetooth has been enabled by the applicaiton. Fixes #5454 Fixes #12215 Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2019-02-08 01:24:30 +08:00
default BT
boards: particle: fix BT selection When selecting BT we need to select BT_CTRL for most bluetooth samples to work correctly. Let's fix that in the board files. Fixes the following error when CONFIG_BT is selected: zephyr/drivers/bluetooth/hci/h4.c:463:30: error: ‘CONFIG_BT_UART_ON_DEV_NAME’ undeclared (first use in this function) h4_dev = device_get_binding(CONFIG_BT_UART_ON_DEV_NAME); ^~~~~~~~~~~~~~~~~~~~~~~~~~ Signed-off-by: Michael Scott <mike@foundries.io>
2019-01-27 12:03:52 +08:00
boards: arm: particle: refactor for commonalities Provide a dtsi file that sets up common capabilities for all Feather-based Particle Mesh devices. Provide additional dtsi files for some obvious peripheral options. Remove the xtensa esp32 image: it didn't build, and there's no indication of how the ESP32 firmware can be updated on the Argon board. Use particle_argon as the nRF52840 side of the board. Add Particle Boron support. Note that dtsi files must be replicated in each board directory until tooling supports DTS includes from a shared area. Signed-off-by: Peter A. Bigot <pab@pabigot.com>
2018-12-20 04:46:33 +08:00
endif # BOARD_PARTICLE_ARGON