Lines Matching +full:handle +full:- +full:tx +full:- +full:in +full:- +full:workq
4 # SPDX-License-Identifier: Apache-2.0
12 that have been enabled in the stack, such as GATT support.
113 bool "Mesh-specific workqueue"
116 mesh-specific workqueue. This will ensure that messages are always sent.
117 The application needs to ensure the mesh-specific workqueue size is large
130 CONFIG_BT_BUF_CMD_TX_COUNT, the host returns -ENOBUFS immediately
134 will be affected by other users on the system work queue, resulting in
189 in a friendship, this option can delay transmission of local
191 value. This in turn will result in increase of the power
237 bool "PB-ADV support"
246 prompt "The interval (in seconds) to send the unprovisioned beacon" if BT_MESH_PB_ADV
250 This option specifies the interval (in seconds) at which the
268 in addition to the first transmission.
276 in addition to the first transmission.
285 in addition to the first transmission.
299 bool "PB-GATT Server support"
309 bool "Include Bluetooth device name in scan response"
313 This option includes GAP device name in scan response when
314 the PB-GATT is enabled.
317 bool "PB-GATT Client support"
375 int "Maximum number of nodes in the database"
380 save in the configuration database.
383 int "Maximum number of subnets in the database"
388 saved in the configuration database.
391 int "Maximum number of application keys in the database"
396 be saved in the configuration database.
417 in addition to the first transmission. Can be changed through runtime
426 messages, in milliseconds. Can be changed through runtime
438 unnecessary relaying and helps in getting rid of relay loops. Setting
463 Controls the initial number of retransmissions of relayed messages, in
473 messages, in milliseconds. Can be changed through runtime
491 BT_MESH_RELAY_ADV_SETS allows the increase in the number of buffers
509 Maximum number of simultaneous outgoing multi-segment and/or
521 Maximum number of simultaneous incoming multi-segment and/or
546 int "Maximum number of segments in incoming messages"
554 This value should typically be fine-tuned based on what
565 4-byte MIC and 52 bytes using an 8-byte MIC.
568 int "Maximum number of segments in outgoing messages"
576 This value should typically be fine-tuned based on what
587 4-byte MIC and 52 bytes using an 8-byte MIC.
595 segments in a segmented message. The interval is measured in
624 a unicast address. The interval step is measured in milliseconds and
635 a unicast address. The increment is measured in milliseconds and
653 segments in a segmented message to a multicast address. The
654 interval is measured in milliseconds and calculated using the
663 This value defines a threshold in number of segments of a segmented
676 receiving a new segment. The increment is measured in segments
687 receiving a new segment. The interval is measured in milliseconds
706 size of segments in a segmented message is above the
731 Note that: To ensure sufficient space in CRPL for normal node
734 you should increase the CRPL capacity in your project configuration
743 bool "Persistent storage of RPL in Settings"
745 Persistent storage of RPL in Settings. If BT_SETTINGS is not
746 enabled this choice will provide a non-persistent implementation
769 in the stack. For example, spamming broadcast messages those stack cannot handle
813 of the largest Composition Data Page present in the application.
818 bool "Access layer tx delayable message"
823 However, they are strictly recommended if the device participates in the network with
829 bool "The delayable message in the notification message context"
832 Controls whether the delayable message feature is enabled by default in
884 int "Config Client model timeout in milliseconds"
901 int "Health Client model timeout in milliseconds"
922 In Pull mode (Pull BLOB Transfer Mode), the BLOB Transfer Server
924 control the chunk count in the request. If the BLOB Transfer Server
929 int "Largest BLOB size in bytes"
938 range 64 1048576 # 2^6 - 2^20
940 Minimum acceptable block size in a BLOB transfer. The transfer block
950 Maximum acceptable block size in a BLOB transfer. The transfer block
956 int "Partial Block Report interval in Pull mode"
1007 Set the interval in milliseconds in which chunks are sent during the BLOB transfer.
1079 metadata using the format defined in the Bluetooth Mesh DFU subsystem.
1172 int "Max AD types in extended scanning"
1177 a set of AD types in the scan reports, collected from the
1233 int "Opcodes Aggregator Client model timeout in milliseconds"
1280 bool "Support for On-Demand Private Proxy Client model"
1282 On-Demand Private Proxy Client allows to configure and check the state
1283 of On-Demand Private Proxy Servers. The state determines if the peers will
1288 int "Solicitation PDU RPL Configuration Client model timeout in milliseconds"
1292 This timeout controls how long the On-Demand Private Proxy Client waits
1297 bool "Support for On-Demand Private Proxy Server model"
1301 The On-Demand Private Proxy Server is used to support configuration of
1313 is stored in the SRPL and the SSEQ field value is bigger than the corresponding
1314 stored SSEQ value, or if the SSRC was not stored in the RPL and the SRPL still has
1326 int "Solicitation PDU RPL Configuration Client model timeout in milliseconds"
1345 int "Maximum number of entries in the bridging table"
1349 The maximum number of entries in the bridging table.
1362 int "Bridge Configuration Client model timeout in milliseconds"
1401 using Node Identity. The given value is in seconds. The
1407 bool "Include Bluetooth device name in scan response"
1409 This option includes GAP device name in scan response when
1418 node supports. This helps in reducing unwanted traffic getting sent to
1496 that do not support TF-M.
1500 bool "Use TF-M PSA [EXPERIMENTAL]"
1504 Use TF-M as PSA Crypto API provider. This is only possible on platforms
1505 that support TF-M.
1564 in Progress, we need to keep track of how many hours has passed
1565 in the state, since the specification requires us to remain in
1566 the state at least for 96 hours (Update in Progress has an
1569 In order to fulfill the above requirement, even if the node might
1570 be powered off once in a while, we need to store persistently
1571 how many hours the node has been in the state. This doesn't
1580 duration that the node has been in the current state gets
1617 Time in seconds from the last received message, that the node
1625 Time in seconds between Friend Requests, if a previous Friend
1629 int "RSSIFactor, used in the Friend Offer Delay calculation"
1634 in Friend Offer Delay calculations. 0 = 1, 1 = 1.5, 2 = 2, 3 = 2.5.
1637 int "ReceiveWindowFactor, used in the Friend Offer Delay calculation"
1641 The contribution of the supported Receive Window used in
1651 the Friend node can store in its Friend Queue. As an example,
1663 is in units of milliseconds. When BT_MESH_ADV_LEGACY is used,
1665 to a limitation in the legacy advertiser implementation.
1676 terminated. The value is in units of 100 milliseconds, so e.g.
1687 in value for each iteration. The value is in units of 100
1695 Latency in milliseconds that it takes to enable scanning. This
1696 is in practice how much time in advance before the Receive Window
1734 Receive Window in milliseconds supported by the Friend node.
1766 that we are Friends for. In other words, this determines how
1775 Latency in milliseconds between request for and start of Friend
1791 participate in at the same time.
1830 int "Delay (in seconds) before storing anything persistently"
1834 This value defines in seconds how soon any pending changes
1839 int "How often the sequence number gets updated in storage"
1845 updated in persistent storage (i.e. flash). E.g. a value of 100
1858 …int "Minimum interval after which unsaved RPL and SRPL entries are updated in the settings subsyst…
1859 range -1 1000000
1862 This value defines time in seconds until unsaved RPL and SRPL entries
1869 may make sense. Setting this value to -1 will disable this timer.
1870 In this case, a user is responsible to store pending RPL entries
1871 using @ref bt_mesh_rpl_pending_store. In the mean time, when
1883 bool "Store the Bluetooth Mesh settings in a separate work queue"
1888 the stack's configuration is stored in the system workqueue. This
1904 int "Stack size of the settings workq"
1929 bool "Perform self-tests"
1931 This option adds extra self-tests which are run every time