Skip to content

Rebase feature-hal-spec-rtc #5460

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

Conversation

c1728p9
Copy link
Contributor

@c1728p9 c1728p9 commented Nov 8, 2017

Rebase feature-hal-spec-rtc on top of master. This is an alternative to #5447. It preserves the rebase history so when its time to merge to master it can be done reasonably.

c1728p9 and others added 6 commits October 25, 2017 17:16
Keep the prototypes in rtc_api.h even when DEVICE_RTC is not defined.
This allows devices that aren't fully compliant with the RTC API to
still use the header and prototypes.
Keep the RTC code if either DEVICE_RTC or DEVICE_LOWPOWERTIMER is
defined on the devices which use the RTC for both the rtc api and the
low power timer api. This allows DEVICE_LOWPOWERTIMER to be enabled while
DEVICE_RTC is turned off.
Add requirements, tests, an example implementation and additional
function documentation to the HAL RTC API.
Turn off RTC for all devices. When support for a device is added this
should be re-enabled.
RTC specification with test headers (branch feature-hal-spec-rtc)
@theotherjimmy
Copy link
Contributor

Well, github does not seem to like it 😆

@c1728p9 c1728p9 force-pushed the feature-hal-spec-rtc branch from d312da9 to 5e6c46e Compare November 9, 2017 21:44
@c1728p9 c1728p9 closed this Nov 9, 2017
@sg- sg- removed the needs: review label Nov 9, 2017
@c1728p9 c1728p9 deleted the rebase_feature-hal-spec-rtc branch November 9, 2017 21:45
@c1728p9
Copy link
Contributor Author

c1728p9 commented Nov 9, 2017

Closing this since this branch has been rebased

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants