I’m using a Verdin iMX8MM Q 2GB WB IT on the Verdin Devolopment Board V1.1B.
When I suspend the SOM by software command, the CTRL_SLEEP_MOCI# remains high, although the Verdin Family Specification says in Table 2, Section 5.3 that this signal has to go low in sleep state.
The issue around CTRL_SLEEP_MOCI for the Verdin iMX8M Plus and the Verdin iMX8M Mini has been fixed* since BSP 6.6.0.
I am not sure why the issue tracker has not been updated, I will raise this internally.
Upon further discussion about this issue, it turns out that there are a few things that you need to be careful when configuring your device to get a reliable CTRL_SLEEP_MOCI on the Verdin iMX8MP.
Can you clarify which peripherals you plan to rely on this behavior?
If you prefer, we can take this discussion to another thread or a private message to the moderators here on the community.
It’s great that the problem has now been solved.
Since the thread was originally about the Verdin iMX8MM:
Upon further discussion about this issue, it turns out that there are a few things that you need to be careful when configuring your device to get a reliable CTRL_SLEEP_MOCI on the Verdin iMX8MP.
Does this also apply to the Verdin iMX8MM?
We want to use the signal of CTRL_SLEEP_MOCI as an input of a microcontroller who is responsible for the battery management and who needs to know whether the SOM is in sleep state.
The main thing that needs to be considered is the sleep and wake up sequences.
Do you have a custom kernel module associated with this microcontroller?
If so, the kernel module must be prepared with support for the regulators so they are turned on/off in the correct timing and order during a sleep/resume cycle.
We had to adapt several drivers on our side to make this happen for our carrier boards.
However, if you just want to sense the signal with the microcontroller, this should work without issues.
Please make sure to test this in a recent BSP and check that the behavior is as expected.