177e9b93bf
Mesh models may have a data that needs to be stored persistently. Currently, the models should call bt_mesh_model_data_store and the store will happen in the calling context. Most likely that it will be called in BT RX thread as this is the context from which model's opcodes handlers are called. Thus, the thread will be blocked until the store is finished. Another issues is that some models may have states that changes frequently. Triggering the store on every state change may wear out flash. Therefore, the models need to implement some postpone mechanism to reduce the flash wear out. The mesh stack has already implemented the mechanism of deferred store with its own settings. The models could use it instead of implementing their own mechanism. In combination with the mesh settings workqueue, the models can store their data without blocking the stack work. Signed-off-by: Pavel Vasilyev <pavel.vasilyev@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| api | ||
| autopts | ||
| img | ||
| bluetooth-arch.rst | ||
| bluetooth-audio-arch.rst | ||
| bluetooth-ctlr-arch.rst | ||
| bluetooth-dev.rst | ||
| bluetooth-qual.rst | ||
| bluetooth-shell.rst | ||
| bluetooth-tools.rst | ||
| dis-pics.rst | ||
| gap-pics.rst | ||
| gatt-pics.rst | ||
| index.rst | ||
| l2cap-pics.rst | ||
| mesh-pics.rst | ||
| overview.rst | ||
| rfcomm-pics.rst | ||
| sm-pics.rst | ||