drivers/pn532 : Expose Configurations to Kconfig #13951
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 PN532 Network Device driver to Kconfig.
Testing procedure
New macro was introduced in tests/driver_pn532/main.c for testing.
Firmware was uploaded to FIT IoT Lab test bed.
Default State:
Firmware Output
main(): This is RIOT! (Version: 2020.07-devel-198-gcf64d-Kconfig_pn532)
CONFIG_PN532_BUFFER_LEN=(64)
awake
ver 0.2
set sam 0
Usage with CFLAGS
/tests/driver_pn532/Makefile
Firmware Output
main(): This is RIOT! (Version: 2020.07-devel-198-gcf64d-Kconfig_pn532)
CONFIG_PN532_BUFFER_LEN=128
awake
ver 0.2
set sam 0
Usage with Kconfig
/tests/driver_pn532/
Firmware Output
main(): This is RIOT! (Version: 2020.07-devel-198-gcf64d-Kconfig_pn532)
CONFIG_PN532_BUFFER_LEN=256
awake
ver 0.2
set sam 0
Note : The sensor is not available for interfacing hence configurability of macros were only tested.
Issues/PRs references
#12888
@leandrolanzieri