IMX suspend: Difference between revisions
No edit summary |
(Add category Debian) |
||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
{{PageHeader|Suspend to RAM}} | {{PageHeader|Suspend to RAM}} | ||
{{DocImage|category1=Yocto|category2=VAR-SOM-MX6 | {{DocImage|category1=Yocto|category2=Debian}} | ||
= Suspend to RAM = | [[Category:VAR-SOM-MX6]] | ||
[[Category:DART-6UL]] | |||
[[Category:VAR-SOM-MX7]] | |||
=Suspend to RAM= | |||
This state offers significant power savings as everything in the system is put into a low-power state, except for memory, which is placed into the self-refresh mode to retain its contents.<br> | This state offers significant power savings as everything in the system is put into a low-power state, except for memory, which is placed into the self-refresh mode to retain its contents.<br> | ||
To suspend to RAM: | To suspend to RAM, run: | ||
# pm-suspend | |||
< | =Wake up= | ||
<br> | There are many possible ways to wake up from suspend.<br> | ||
A few examples:<br> | |||
- Pushing the ON/OFF button (when present on the board)<br> | |||
- Pushing a button on the board which has the boolean property "gpio-key,wakeup" set in its device tree node (under gpio_keys), e.g.: | |||
gpio-keys { | |||
compatible = "gpio-keys"; | |||
pinctrl-names = "default"; | |||
pinctrl-0 = <&pinctrl_gpio_keys>; | |||
back { | |||
label = "Back"; | |||
gpios = <&gpio5 20 GPIO_ACTIVE_LOW>; | |||
linux,code = <KEY_BACK>; | |||
'''gpio-key,wakeup'''; | |||
}; | |||
}; | |||
- Using the RTC you can wake at a specific time (see the [[IMX_RTC|RTC section]])<br> | |||
= Current consumption when suspended = | =Current consumption when suspended= | ||
== VAR-SOM-MX6 "L" revisions (1GB RAM) == | ==VAR-SOM-MX6 "L" revisions (1GB RAM)== | ||
17.2mA with a 3.7V Li-Po<br> | 17.2mA with a 3.7V Li-Po<br> | ||
<br> | <br> | ||
Warning: Only "L" (for Low-power) revisions of VAR-SOM-MX6 can be operated at 3.7V! | Warning: Only "L" (for Low-power) revisions of VAR-SOM-MX6 can be operated at 3.7V! | ||
== DART-MX6 == | ==DART-MX6== | ||
9mA with a 3.7V Li-Po<br> | 9mA with a 3.7V Li-Po<br> | ||
== VAR-DART-6UL == | ==VAR-DART-6UL== | ||
4.5mA at 3.3V<br> | 4.5mA at 3.3V<br> | ||
== VAR-SOM-MX7 == | ==VAR-SOM-MX7== | ||
Transistor Q1 should be shorted in order to measure the sleep current correctly. | |||
Please check out the CustomBoard schematics for additional information. | |||
Latest revision as of 19:30, 28 April 2023
Suspend to RAM
This state offers significant power savings as everything in the system is put into a low-power state, except for memory, which is placed into the self-refresh mode to retain its contents.
To suspend to RAM, run:
# pm-suspend
Wake up
There are many possible ways to wake up from suspend.
A few examples:
- Pushing the ON/OFF button (when present on the board)
- Pushing a button on the board which has the boolean property "gpio-key,wakeup" set in its device tree node (under gpio_keys), e.g.:
gpio-keys {
compatible = "gpio-keys";
pinctrl-names = "default";
pinctrl-0 = <&pinctrl_gpio_keys>;
back {
label = "Back";
gpios = <&gpio5 20 GPIO_ACTIVE_LOW>;
linux,code = <KEY_BACK>;
gpio-key,wakeup;
};
};
- Using the RTC you can wake at a specific time (see the RTC section)
Current consumption when suspended
VAR-SOM-MX6 "L" revisions (1GB RAM)
17.2mA with a 3.7V Li-Po
Warning: Only "L" (for Low-power) revisions of VAR-SOM-MX6 can be operated at 3.7V!
DART-MX6
9mA with a 3.7V Li-Po
VAR-DART-6UL
4.5mA at 3.3V
VAR-SOM-MX7
Transistor Q1 should be shorted in order to measure the sleep current correctly. Please check out the CustomBoard schematics for additional information.