xous-api-susres
| Crates.io | xous-api-susres |
| lib.rs | xous-api-susres |
| version | |
| source | src |
| created_at | 2022-10-02 18:08:07.049394 |
| updated_at | 2024-12-02 11:16:36.848063 |
| description | Manager of suspend/resume operations |
| homepage | https://betrusted.io/xous-book/ |
| repository | https://github.com/betrusted-io/xous-core/ |
| max_upload_size | |
| id | 678500 |
| Cargo.toml error: | TOML parse error at line 18, column 1 | 18 | autolib = false | ^^^^^^^ unknown field `autolib`, expected one of `name`, `version`, `edition`, `authors`, `description`, `readme`, `license`, `repository`, `homepage`, `documentation`, `build`, `resolver`, `links`, `default-run`, `default_dash_run`, `rust-version`, `rust_dash_version`, `rust_version`, `license-file`, `license_dash_file`, `license_file`, `licenseFile`, `license_capital_file`, `forced-target`, `forced_dash_target`, `autobins`, `autotests`, `autoexamples`, `autobenches`, `publish`, `metadata`, `keywords`, `categories`, `exclude`, `include` |
| size | 0 |
bunnie (bunnie)
documentation
README
Xous Api: susres
This crate defines the Xous suspend/resume API.
The suspend/resume API is responsible for sequencing events before a system powers down, such that all of the SoC hardware blocks will lose state, but the RAM will retain its contents.
Every service that contains hardware state which can be lost when
the SoC is powered down must register with the sequencer, and it
must atomically back up its hardware state to battery-backed RAM
and then call suspend_until_resume, which will block until power
is restored. Once power is restored, the service should copy the
hardware state out of battery-backed RAM and resume operations.
The API also contains hooks for initiating the suspend process, and for rebooting the device.