[mwayned]

All,

Thank you for your help. I have spliced lines 28 to 129 of the stm32mp157c-dk2-m4-examples.dts at the end of the osd32mp1-red.dts file and rebuilt the dtb file.
With this change in place I see various peripherals drivers failing on startup due to the now different DMA configuration (this is good, I don’t need those peripherals and it shows my device tree changes are on board). I can still control putting the M4 to sleep/waking it up as I can see the current decrease/increase respectively. However when trying to put the A7s to sleep the “systemctl suspend” command has no effect on power consumption (or the terminal interactivity, can continue to interact with the shell). If I call “systemctl suspend” again I get this message:

Failed to suspend system via logind: There’s already a shutdown or sleep operation in progress

dmesg outputs this:
[ 353.395298] PM: suspend entry (deep)
[ 353.397488] PM: Syncing filesystems … done.

Is the “suspend” script located at /etc/systemd/sleep.conf configured to properly sleep? I uncommented lines in this file pertaining to suspend

AllowSuspend=yes
SuspendState=mem standby freeze

but with or without those lines the “systemctl suspend” command has no effect on the system, and upon subsequent calls will result in the “Failed to suspend…. already a shutdown or sleep operation in progress” error message from above.

Is there a simpler way to demonstrate the low power modes of both the M4 and the A7 that I am missing?

Thanks,
Matthew

[mwayned]

Neeraj,

Could you specify which nodes in the stm32mp157c-dk2-m4-examples.dts should be integrated into the osd32mp1-red.dts in order to get these examples functioning?
I have attempted many high level merges of this file into or taking the place of the osd32mp1-red.dts file without success.

Thanks,
Matthew

[mwayned]

Neeraj,

Thank you for the help, sorry for the slow reply.

I copied the dtb file you suggested over the existing one with this command:

cp kernel/linux-4.19.94/arch/arm/boot/dts/stm32mp157c-dk2-m4-examples.dtb /media/<user>/bootfs/osd32mp1-red.dtb

the boot now hangs at ” Waiting for root device /dev/mmcblk1p6…”

Copying the correct osd32mp1-red.dtb back into place results in proper booting again.

Should I investigate differences between stm32mp167a-dk1.dts (the file that defines the pins and sd card devices for stm32mp157c-dk2-m4-examples.dtb) and osd32mp1-red.dts?

Thanks,
Matthew

[Author]

Posts