drivers/motor_driver : Expose Configurations to Kconfig#13927
Merged
leandrolanzieri merged 2 commits intoRIOT-OS:masterfrom Apr 23, 2020
Merged
drivers/motor_driver : Expose Configurations to Kconfig#13927leandrolanzieri merged 2 commits intoRIOT-OS:masterfrom
leandrolanzieri merged 2 commits intoRIOT-OS:masterfrom
Conversation
Contributor
leandrolanzieri
left a comment
There was a problem hiding this comment.
Just minor comments. You can squash directly
71 tasks
Add CONFIG_ Prefix for MOTOR_DRIVER_MAX
Expose Configurations to Kconfig Co-Authored-By: Leandro Lanzieri <leandro.lanzieri@haw-hamburg.de>
fe6cd29 to
c654b4e
Compare
Member
Author
Done. Thanks |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 Motor Driver Actuator Device driver to Kconfig.
Testing procedure
New macro was introduced in main.c for testing.
Default State:
Firmware Output
RIOT native interrupts/signals initialized.
LED_RED_OFF
LED_GREEN_ON
RIOT native board initialized.
RIOT native hardware initialization complete.
Auto init xtimer.
main(): This is RIOT! (Version: 2020.07-devel-166-g1774d-Kconfig_motor_driver)
CONFIG_MOTOR_DRIVER_MAX=(2)
Brake motors !!!
Usage with CFLAGS
/tests/driver_motor_driver/Makefile
Firmware Output
RIOT native interrupts/signals initialized.
LED_RED_OFF
LED_GREEN_ON
RIOT native board initialized.
RIOT native hardware initialization complete.
Auto init xtimer.
main(): This is RIOT! (Version: 2020.07-devel-166-g1774d-Kconfig_motor_driver)
CONFIG_MOTOR_DRIVER_MAX=4
Brake motors !!!
Usage with Kconfig
/tests/driver_motor_driver/
Firmware Output
RIOT native interrupts/signals initialized.
LED_RED_OFF
LED_GREEN_ON
RIOT native board initialized.
RIOT native hardware initialization complete.
Auto init xtimer.
main(): This is RIOT! (Version: 2020.07-devel-166-g1774d-Kconfig_motor_driver)
CONFIG_MOTOR_DRIVER_MAX=6
Brake motors !!!
Note : The network device is not available for interfacing hence configurability of macros were only tested.
Issues/PRs references
#12888
@leandrolanzieri