i.MX8 Low Power Mode:
How do you set the i.MX8 to wakeup from sleep from a USB Plug-in event? I've looked at 6.1 in IMXLUG, Rev. L4.9.88_2.0.0-ga, 05/2018, and it only mentions setting the debug UART as a wakeup source. I'd like to have the device wakeup when the USB-C cable is plugged into a host; is this supported by the NXP BSP? I am using the NXP i.MX BSP
4.9.88_2.0.0-ga release whose manifest I used with following command:
repo init -u https://source.codeaurora.org/external/imx/imx-manifest -b imx-linux-rocko -m imx-4.9.88-2.0.0_ga.xml
My settings used for the bitbake environment were:
MACHINE=imx8mqevk DISTRO=fsl-imx-xwayland ./fsl-setup-release.sh -b bld-xwayland
I built the fsl-image-gui recipe; i have already successfully suspended the device and woke up from debug UART activity.
Regards,
Kevin
Hi Kevin
one can try procedure described in sect.4.10.2.3 USB Wakeup Usage
attached Linux Manual with Demo Images "Linux Binary Demo Files - i.MX 8MQuad EVK"
Best regards
igor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Igor,
I looked at 4.10.2.3, but my issue is that none of the files it references in /sys/bus/platform/devices exist, see
root@imx8mqevk:~# ls /sys/bus/platform/devices
100000.caam-sm 30a40000.i2c gpc_power_domain@10
30010000.sai 30a70000.mipi_csi1 gpc_power_domain@2
30040000.sai 30a90000.csi1_bridge gpc_power_domain@3
30050000.sai 30aa0000.mu gpc_power_domain@4
30200000.gpio 30b40000.usdhc gpc_power_domain@5
30210000.gpio 30b50000.usdhc gpc_power_domain@8
30220000.gpio 30bb0000.qspi gpc_power_domain@9
30230000.gpio 30bd0000.sdma hdmi-audio-codec
30240000.gpio 30be0000.ethernet imx-dcss-crtc.0
30260000.tmu 32c00000.hdmi imx8mq-cpufreq
30280000.wdog 32e00000.dcss imx_ion
302c0000.sdma 32e2d000.irqsteer imx_rpmsg
302d0000.gpt 33000000.dma-apbh modem-reset
30330000.iomuxc 33800000.pcie pmu
30340000.iomuxc-gpr 33c00000.pcie psci
30350000.ocotp-ctrl 38000000.gpu reg-dummy
30360000.anatop 38100000.dwc3 regulators
30370000.caam-snvs 381f0040.phy regulators:regulator-gpio
30370000.snvs 38200000.dwc3 regulators:usdhc2_vmmc
30370000.snvs:snvs-powerkey 382f0040.phy regulatory.0
30370000.snvs:snvs-rtc-lp 38300000.vpu serial8250
30390000.src 3d800000.ddr_pmu snd-soc-dummy
306a0000.system-counter Fixed MDIO bus.0 sound-ak4458
30810000.spdif alarmtimer sound-ak5558
30860000.serial b8000000.rpmsg sound-hdmi
30880000.serial bcmdhd_wlan@0 sound-hdmi-arc
308a0000.spdif busfreq sound-spdif
308b0000.sai caam_secvio sound-wm8524
30900000.caam caam_sm timer
30901000.jr0 display-subsystem usb@38100000
30902000.jr1 dma_cap usb@38200000
30903000.jr2 gpc_power_domain@0 wm8524
30a20000.i2c gpc_power_domain@1 xhci-hcd.0.auto
Is there some setting that needs to be changed in the defconfig for the system to use the ci_hdrc driver mentioned in 4.10.2.3?