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.
Some controllers, like Zephyr-based controllers, don't like it when passing multiple connection parameters in the connection request (even if the PHY is supported). For example, with a Zephyr controller (from the Zephyr HCI USB example), when not specifying explicit parameters in the connection request (which is what most of the tools and examples do), this would lead
to the controller returning
HCI_UNSUPPORTED_FEATURE_OR_PARAMETER_VALUE_ERROR
.This change is for only specifying default values for 1M if no explicit preferences are passed (you can still pass arbitrary sets if you want, this only changes the default). It also seems reasonable to pick only 1M by default, since that's the expected baseline for all controllers.