We’re using a Riverdi touch screen connected via MIPI DSI to the Mallow board. Everything is working as expected and there aren’t any functionality issues, but we’ve noticed additional power consumption when we use Suspend-to-RAM now while the screen is plugged in (~25mA → ~50mA).
Is there any way to fully cut power to the MIPI DSI before suspending, or is this something that cannot be controlled from the SBC side and the “fault” is on the screen?
I’ve tried manually setting the PWR_DN pin of the screen after unbinding the drivers, but it didn’t net any better results so I’m assuming this is something that is already being handled.
Thanks!
Hi, I’m the Toradex AI Assistant.
I might make mistakes or occasionally get you wrong. Our support team will step in if needed.
I’d be glad to help! Could you let me know which OS and version you are using? Also, which specific Verdin module are you running on the Mallow carrier board?
The power consumption increase you’re seeing during suspend is likely related to how the MIPI DSI interface and display are being handled during the suspend/resume cycle. To provide the most accurate guidance on managing MIPI DSI power control during suspend, I’ll need to know:
- Hardware: Which Verdin module (e.g., Verdin i.MX8M Plus, Verdin AM62, etc.)
- OS Version: Which version of Torizon OS or Yocto BSP are you running?
You can get this information by running the tdx-info command on your device. More details about this tool are available at: Getting Device Information with Tdx-Info | Toradex Developer Center
Common platforms to consider:
- Hardware: Verdin i.MX8M Plus, Verdin AM62, Aquila AM69, Apalis i.MX8QP, Colibri i.MX8X, Ivy Carrier Board, Ixora Carrier Board, Mallow Carrier Board
- OS: Yocto 7.2.0, Torizon 6.8.2, Torizon OS 6, BSP 7, BSP 6, Torizon OS 7.2.0-build.13
Once I know your specific platform, I can provide detailed guidance on MIPI DSI power management during suspend operations, including any platform-specific considerations for power rail control and display interface handling.
Best regards, Toradex AI Assistant.
Did you like my answer? 
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
@ToradexAI
Here’s the specs on one of the devices we’re testing this with and what we’re aiming to run in production, at least regarding the hardware:
–Software summary–
Bootloader: U-Boot
Kernel version: 6.6.119-7.6.0-devel-g1cf2a32cf35e #1-Torizon SMP PREEMPT Fri Jan 30 09:13:14 UTC 2026
Kernel command line: root=LABEL=otaroot rootfstype=ext4 quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3 ostree=/ostree/boot.1/torizon/c9c37e6f354a4e61c2c68f7f4e1a3958574b2766e10a11eb88964c0f37318d3f/0
Distro name: NAME=“Torizon OS”
Distro version: VERSION_ID=7.6.0-devel-202602-build.17
Distro variant: VARIANT=“Docker”
Hostname: verdin-imx8mp-08797431
–Hardware info–
HW model: Toradex Verdin iMX8M Plus on Verdin Development Board
Toradex version: 0063 V1.1B
Serial number: 08797431
Processor arch: aarch64
Thanks for the detailed information! With your Verdin iMX8M Plus (0063 V1.1B) running Torizon OS 7.6.0, I can help address the increased power consumption during suspend when using your MIPI DSI display.
Understanding the Power Consumption Issue
The increased power consumption you’re experiencing (~25mA → ~50mA) during Suspend-to-RAM is indeed related to the display subsystem remaining partially active(1). The Verdin iMX8M Plus power consumption documentation shows that suspend mode to RAM typically consumes around 0.15-0.18W under normal conditions(1).
MIPI DSI Power Management Options
1. Display Backlight PWM Control
The display backlight PWM (PWM_3_DSI) can be controlled to reduce power consumption(2). For the Verdin iMX8M Plus, PWM_3_DSI corresponds to PWM3 and uses /sys/class/pwm/pwmchip2/(2). You can disable the backlight before suspend:
echo 0 > /sys/class/pwm/pwmchip2/pwm0/enable
(2)
2. Suspend/Resume Implementation
You can implement suspend functionality from within a container without root permissions by bind mounting the necessary system files(3). Here’s how to suspend the system:
# docker run -it --rm -v /sys/power/state:/sys/power/state torizon/debian:4
## echo mem > /sys/power/state
(3)
3. Wake-up Configuration
To ensure proper wake-up functionality, you can configure RTC wake-up or UART wake-up(3):
For RTC wake-up (5 seconds):
# docker run -it --rm -v /sys/class/rtc/rtc1/wakealarm:/sys/class/rtc/rtc1/wakealarm -v /sys/power/state:/sys/power/state torizon/debian:4
## echo +5 > /sys/class/rtc/rtc1/wakealarm; echo mem > /sys/power/state
(3)
Recommendations
-
Check Display Driver Configuration: The increased power consumption suggests the MIPI DSI interface or display controller isn’t fully entering low-power mode. This is typically controlled by the display driver in the device tree.
-
PWM Backlight Control: Ensure the display backlight PWM is properly disabled before suspend, as shown above(2).
-
Device Tree Modifications: You may need to customize the device tree to ensure proper power sequencing of the display rails during suspend/resume cycles.
-
Display Power Rails: Since you mentioned trying the PWR_DN pin manually, the issue might be related to other power rails (VDDIO, AVDD) that need to be controlled during suspend.
The power consumption increase you’re seeing is likely due to the MIPI DSI controller or display remaining in a partial power state rather than fully powering down during suspend-to-RAM.
Best regards, Toradex AI Assistant.
Did you like my answer?
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.
Dear @edvin.hansson,
Thank you for bringing up the hurdle you are facing.
The 25 - 50 mA flowing into the screen are at 5V, delivering a power of 250 mW at most. Perhaps the PWR_DN pin for the screen is not yet fully taken care of. May I ask what power consumption you are aiming to reach during the suspend to RAM state from the display? Would the current experienced power consumption be a show stopper for you?
Best regards,
Collin
Hi @collin.tx,
Thanks for the quick response.
We’ve previously seen around ~20-25mA at 12v during Suspend-to-RAM with no screen or HDMI screens powered externally, so that’s our main target for now. Our use case has the Toradex SBC powered by battery and suspended for most of its operation (>95%), only waking up on interaction and re-entering Suspend-to-RAM within ~2-3 minutes. The DSI screen consuming an extra ~25mA would ~2x our power use.
I tried via gpioset 3 28=0to manually set it after unbinding the drivers, but it didn’t reduce the power consumption.
Thanks!
Dear @edvin.hansson,
apologies for the late reply. I am in contact with our partner manager, who is getting in contact with riverdi for this issue, so we can find a solution for you.
Best regards,
Collin
Dear @edvin.hansson,
I just got a reply and Riverdi would be glad to talk with you about the hurdle you are facing. Would it be possible for you to contact them on the following email address?
tech@riverdi.com
Best regards,
Collin
Hi @collin.tx,
No worries about the delay.
We’ve emailed our account manager at Riverdi regarding this and have received a response stating that it’s not possible in the “standard version” of the display that we have but that it’s something that can be achieved with a custom PCB for the display.
But if I’m understanding you correctly, this isn’t something that can be achieved on the Toradex Mallow board side? As in, we cannot completely turn off the power to the MIPI DSI port going to the Riverdi display?
Thanks!
Kind regards,
Edvin
Dear @edvin.hansson,
Thank you for your fast reply. You are indeed correct, that on the Mallow board itself the switching off of the DSI display is not implemented, as can be seen on the following image:
If you would like to control the marked power supplies, I would suggest creating a custom board, in which these lines are power gated. Does this help you in your further evaluation?
Best regards,
Collin
