diff options
| author | Linus Nordberg <linus@nordberg.se> | 2016-06-10 16:07:27 +0200 |
|---|---|---|
| committer | Linus Nordberg <linus@nordberg.se> | 2016-06-10 16:07:27 +0200 |
| commit | 54cd4de78da2534b61c26a7f07abf45907e582d0 (patch) | |
| tree | dc25868bdbf7cdfc7dcdf98b65f12667d381503d /LICENSE.txt | |
| parent | 4f229e0b1083154ee033ca9c2fd5c5367e1621ae (diff) | |
Do wipe MKM when tamper is detected, sleep when not.
Writing the MKM in "sequential mode" (a.k.a. "burst") but still
busy-waiting for confirmation of SPI write operation being done.
Would using an interrupt be faster?
Sleeping is done in "power down mode". There are less sleepy modes
which presumably consume more power but might wake up quicker. A good
start would be to figure out how long time it takes to wake up from
power down.
Diffstat (limited to 'LICENSE.txt')
0 files changed, 0 insertions, 0 deletions