drivers/cc110x : Expose Configurations to Kconfig #13897
Merged
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.
Contribution description
This PR exposes compile configurations in CC110X Network Device driver to Kconfig.
Testing procedure
The firmware was uploaded to FIT/IoT-LAB Test Bed and following results were obtained.
Default State:
Firmware Output
magnrc_netif: netdev init failed: -134
rc_netif: netdev init failed: -134
07-devel-97-g01a8c6-Kconfig_cc110x)
CONFIG_CC110X_DEFAULT_CHANNEL=(0U)
cc110x driver test application
..................
Usage with CFLAGS
/tests/driver_ads101x/Makefile
Firmware Output
magnrc_netif: netdev init failed: -134
rc_netif: netdev init failed: -134
07-devel-97-g01a8c6-Kconfig_cc110x)
CONFIG_CC110X_DEFAULT_CHANNEL=3
cc110x driver test application
..................
Usage with Kconfig
/tests/cc110x/
Firmware Output
magnrc_netif: netdev init failed: -134
rc_netif: netdev init failed: -134
07-devel-97-g01a8c6-Kconfig_cc110x)
CONFIG_CC110X_DEFAULT_CHANNEL=7
cc110x driver test application
..................
Note : The network device is not available fro interfacing hence configurability of macros were only tested.
Issues/PRs references
#12888
@leandrolanzieri