Add PlatformManager::Shutdown to permit the event loop to terminate p… #1531
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…roperly for POSIX platforms
Problem
Right now POSIX platforms (and FreeRTOS) expect the event loop to run forever. In order to allow the platform specific event loop for tool like chip-tool it would be useful to allow it to terminate properly if needed.
For example examples/chip-tool could be used to launch a single command and then terminate. At some points I would like to compile chip-tool against the host POSIX platform in order to emulate a high level controller and use the same codepaths.
Summary of Changes
I would like to say that this patch fixes #742 but it is only a subpart of it as far as I can tell.