michaelh/zephyr
1
0
Fork 0
Code Releases Activity

bluetooth: mesh: Doc fix Bluetooth mesh to Mesh

Browse source 
SIG has changed Bluetooth mesh to Bluetooth Mesh
Updating zephyr docs accordingly
Leaving out old release notes

Signed-off-by: Mia Koen <mia.koen@nordicsemi.no>
This commit is contained in:
Mia Koen 2023-11-29 13:33:33 +01:00 • committed by Fabio Baltieri
commit 0bcad09392
60 changed files with 140 additions and 140 deletions
Download patch file Download diff file Expand all files Collapse all files

20
subsys/bluetooth/mesh/Kconfig
View file

@ -1,13 +1,13 @@
# Bluetooth mesh configuration options
# Bluetooth Mesh configuration options
# Copyright (c) 2017 Intel Corporation
# SPDX-License-Identifier: Apache-2.0
menuconfig BT_MESH
bool "Bluetooth mesh support"
bool "Bluetooth Mesh support"
depends on BT_OBSERVER && BT_BROADCASTER
help
This option enables Bluetooth mesh support. The specific
This option enables Bluetooth Mesh support. The specific
features that are available may depend on other features
that have been enabled in the stack, such as GATT support.
@ -598,7 +598,7 @@ config BT_MESH_ACCESS_LAYER_MSG
help
This option allows the application to directly access
Bluetooth access layer messages without the need to
instantiate Bluetooth mesh models.
instantiate Bluetooth Mesh models.
config BT_MESH_MODEL_VND_MSG_CID_FORCE
bool "Force vendor model to use the corresponding CID field message"
@ -1049,9 +1049,9 @@ config BT_MESH_FRIEND_ADV_LATENCY
endif # BT_MESH_FRIEND
menuconfig BT_MESH_V1d1
bool "Bluetooth mesh v1.1 support"
bool "Bluetooth Mesh v1.1 support"
help
This option enables Bluetooth mesh v1.1 support. Bluetooth mesh v1.1
This option enables Bluetooth Mesh v1.1 support. Bluetooth Mesh v1.1
is backward compatible with v1.0.1.
config BT_MESH_ECDH_P256_CMAC_AES128_AES_CCM
@ -1201,7 +1201,7 @@ config BT_MESH_DFU_METADATA
bool "Support for the default metadata format"
help
This option adds a set of functions that can be used to encode and decode a firmware
metadata using the format defined in the Bluetooth mesh DFU subsystem.
metadata using the format defined in the Bluetooth Mesh DFU subsystem.
config BT_MESH_DFU_URI_MAXLEN
int "DFU URI max length"
@ -1734,16 +1734,16 @@ config BT_MESH_RPL_STORE_TIMEOUT
endif # BT_MESH_RPL_STORAGE_MODE_SETTINGS && BT_SETTINGS
config BT_MESH_SETTINGS_WORKQ
bool "Store the Bluetooth mesh settings in a separate work queue"
bool "Store the Bluetooth Mesh settings in a separate work queue"
default y
help
This option enables a separate cooperative thread which is used to
store Bluetooth mesh configuration. When this option is disabled,
store Bluetooth Mesh configuration. When this option is disabled,
the stack's configuration is stored in the system workqueue. This
means that the system workqueue will be blocked for the time needed
to store the pending data. This time may significantly increase if
the flash driver does the erase operation. Enabling this option
allows Bluetooth mesh not to block the system workqueue, and thus
allows Bluetooth Mesh not to block the system workqueue, and thus
process the incoming and outgoing messages while the flash driver
waits for the controller to allocate the time needed to write the
data and/or erase the required flash pages.

2
subsys/bluetooth/mesh/access.h
View file

@ -94,7 +94,7 @@ void bt_mesh_msg_cb_set(void (*cb)(uint32_t opcode, struct bt_mesh_msg_ctx *ctx,
* Send a mesh model layer message out into the mesh network without having instantiated
* the relevant mesh models.
*
* @param ctx The Bluetooth mesh message context.
* @param ctx The Bluetooth Mesh message context.
* @param buf The message payload.
*
* @return 0 on success or negative error code on failure.

2
subsys/bluetooth/mesh/settings.c
View file

@ -88,7 +88,7 @@ static int mesh_commit(void)
}
if (!atomic_test_bit(bt_dev.flags, BT_DEV_ENABLE)) {
/* The Bluetooth mesh settings loader calls bt_mesh_start() immediately
/* The Bluetooth Mesh settings loader calls bt_mesh_start() immediately
* after loading the settings. This is not intended to work before
* bt_enable(). The doc on @ref bt_enable requires the "bt/" settings
* tree to be loaded after @ref bt_enable is completed, so this handler

10
subsys/bluetooth/mesh/shell/Kconfig
View file

@ -1,13 +1,13 @@
# Bluetooth mesh shell configuration options
# Bluetooth Mesh shell configuration options
# Copyright (c) 2022 Nordic Semiconductor
# SPDX-License-Identifier: Apache-2.0
menuconfig BT_MESH_SHELL
bool "Bluetooth mesh shell"
bool "Bluetooth Mesh shell"
select SHELL
help
Activate shell module that provides Bluetooth mesh commands to
Activate shell module that provides Bluetooth Mesh commands to
the console.
if BT_MESH_SHELL
@ -24,7 +24,7 @@ config BT_MESH_SHELL_PROV_CTX_INSTANCE
depends on BT_MESH_SHELL_PROV
help
This option enables the provisioning context instance in the
Bluetooth mesh shell module together with several provisioning
Bluetooth Mesh shell module together with several provisioning
commands and target utility features. To use the provisioning
context instance, use bt_mesh_shell_prov in the
initialization of mesh.
@ -54,7 +54,7 @@ config BT_MESH_SHELL_HEALTH_SRV_INSTANCE
depends on BT_MESH_SHELL_TEST
help
This option enables Health Server model instance in the
Bluetooth mesh shell module together with fault controlling
Bluetooth Mesh shell module together with fault controlling
shell commands. To use the model instance, add bt_mesh_shell_health_srv
to the device composition data. Use BT_MESH_SHELL_HEALTH_PUB_DEFINE to
instantiate publication context.

2
subsys/bluetooth/mesh/shell/shell.c
View file

@ -1814,5 +1814,5 @@ SHELL_STATIC_SUBCMD_SET_CREATE(mesh_cmds,
SHELL_SUBCMD_SET_END
);
SHELL_CMD_ARG_REGISTER(mesh, &mesh_cmds, "Bluetooth mesh shell commands",
SHELL_CMD_ARG_REGISTER(mesh, &mesh_cmds, "Bluetooth Mesh shell commands",
bt_mesh_shell_mdl_cmds_help, 1, 1);