Skip to content
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

cpu/kinetis: implement Low-Leakage Wakeup Unit and add support to UART #14377

Closed
wants to merge 5 commits into from

Conversation

benemorius
Copy link
Member

@benemorius benemorius commented Jun 27, 2020

Contribution description

Split out of #11789 and originally partly from #7897, this PR adds support for the Kinetis LLWU peripheral (which is used by other peripherals to wake from the lowest power mode) and adds UART support to make use of it.

This allows sleeping all the way down to the lowest power mode (~5uA) while retaining a working LEUART or even UART by waking on a pin interrupt instead of waking via the UART hardware.

Testing procedure

Compile with CFLAGS=-DPM_BLOCKER_INITIAL=0x0 make to unblock all modes by default and confirm that the shell remains working.

It should remain working either (depending on the baud rate and board clock configuration) because the correct power mode has been blocked to keep the UART clocked or because it is able to wake via LLWU or GPIO interrupt, but in any case it should "automatically" remain working for any baud and board configuration.

Currently there are bugs preventing GPIO interrupts from working properly on Kinetis. This is fixed in #14376.

There also may be an issue with some boards working at baud rates below 115200 which appears to be reproducible on master.

Issues/PRs references

This PR needs #14376 for GPIO interrupt bugfixes.

@MrKevinWeiss MrKevinWeiss added State: waiting for other PR State: The PR requires another PR to be merged first Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation labels Jun 30, 2020
@stale
Copy link

stale bot commented Jan 2, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you want me to ignore this issue, please mark it with the "State: don't stale" label. Thank you for your contributions.

@stale stale bot added the State: stale State: The issue / PR has no activity for >185 days label Jan 2, 2021
@stale stale bot closed this Feb 2, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
State: stale State: The issue / PR has no activity for >185 days State: waiting for other PR State: The PR requires another PR to be merged first Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants