-
Notifications
You must be signed in to change notification settings - Fork 6.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Renesas: Smartbond: RTC Driver Update #72817
Renesas: Smartbond: RTC Driver Update #72817
Conversation
f0ae9b5
to
0abc423
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You could introduce the shared util
zephyr/drivers/rtc/rtc_utils.h
Line 26 in bc183d1
bool rtc_utils_validate_rtc_time(const struct rtc_time *timeptr, uint16_t mask); |
0abc423
to
db6b58a
Compare
This commit should fix the followings: 1. When an alarm event is initialized, the driver should only consume the valid alarm fields, based on the given mask. Otherwise, the driver should use default valid subfield values. 2. Setting an alarm event should not return with error code if the timer and/or calendar counters have yet to be initialized, explicitly. Instead, a log warning should be issued. Signed-off-by: Ioannis Karachalios <ioannis.karachalios.px@renesas.com>
This commit should add support for the DA1469x Pro DevKit. Signed-off-by: Ioannis Karachalios <ioannis.karachalios.px@renesas.com>
db6b58a
to
96cf924
Compare
Done. The RTC controller should detect invalid alarm fields and API should return with -EINVAL. However, it should be more efficient to use the mentioned utility before accessing the RTC alarm registers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good :)
This PR should fix few RTC driver issues and add support to the RTC test suite.