Bluetooth: Mesh: Use default provisioning protocol timeout in RPR Client
The timeout used upon opening the link with the server relates to the PB-Remote Link Open procedure, but not to the whole provisioning procedure. For the provisioning procedure, the timeout should be at least 60 seconds as explained in section 5.4.4. Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no>
This commit is contained in:
parent
e9a20cc3b6
commit
3e14c13d8d
2 changed files with 10 additions and 1 deletions
|
@ -4,7 +4,11 @@
|
|||
* SPDX-License-Identifier: Apache-2.0
|
||||
*/
|
||||
|
||||
#define PROTOCOL_TIMEOUT K_SECONDS(60)
|
||||
/** Provisioning protocol timeout in seconds. */
|
||||
#define PROTOCOL_TIMEOUT_SEC 60
|
||||
|
||||
/** Provisioning protocol timeout. */
|
||||
#define PROTOCOL_TIMEOUT K_SECONDS(PROTOCOL_TIMEOUT_SEC)
|
||||
|
||||
/** @def PROV_BEARER_BUF_HEADROOM
|
||||
*
|
||||
|
|
|
@ -59,6 +59,11 @@ static void link_report(struct bt_mesh_rpr_cli *cli,
|
|||
bearer.link = BEARER_LINK_OPENED;
|
||||
LOG_DBG("Opened");
|
||||
bearer.cb->link_opened(&pb_remote_cli, &ctx);
|
||||
|
||||
/* PB-Remote Open Link procedure timeout is configurable, but the provisioning
|
||||
* protocol timeout is not. Use default provisioning protocol timeout.
|
||||
*/
|
||||
cli->link.time = PROTOCOL_TIMEOUT_SEC;
|
||||
return;
|
||||
}
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue