Hi Peter, here is an overview of the output voltages of all voltage regulators I could find on that system: for i in $(find / -name microvolts);do echo $i -- $(cat $i);done /sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-3p0/regulator/regulator.2/microvolts -- 3000000 /sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-vddsoc/regulator/regulator.6/microvolts -- 1175000 /sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-1p1/regulator/regulator.1/microvolts -- 1100000 /sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-vddcore/regulator/regulator.4/microvolts -- 1175000 /sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-2p5/regulator/regulator.3/microvolts -- 2400000 /sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-vddpu/regulator/regulator.5/microvolts -- 1175000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.26/microvolts -- 1800000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.16/microvolts -- 1800000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.24/microvolts -- 2500000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.14/microvolts -- 1300000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.22/microvolts -- 2500000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.20/microvolts -- 1200000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.29/microvolts -- 2800000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.19/microvolts -- 1700000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.27/microvolts -- 3300000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.17/microvolts -- 1800000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.25/microvolts -- 2500000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.15/microvolts -- 1500000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.23/microvolts -- 3300000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.13/microvolts -- 1300000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.21/microvolts -- 2500000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.28/microvolts -- 1200000 /sys/devices/soc0/soc/2100000.aips-bus/21a0000.i2c/i2c-0/0-0058/da9063-regulators/regulator/regulator.18/microvolts -- 3300000 /sys/devices/soc0/supplies/supplies:supply@0/regulator/regulator.9/microvolts -- 5000000 /sys/devices/soc0/supplies/supplies:supply@1/regulator/regulator.10/microvolts -- 3300000 /sys/devices/soc0/supplies/supplies:otgvbus/regulator/regulator.12/microvolts -- 5000000 /sys/devices/soc0/supplies/supplies:supply@2/regulator/regulator.11/microvolts -- 1500000 /sys/devices/soc0/regulators/regulators:regulator@1/regulator/regulator.8/microvolts -- 5000000 /sys/devices/soc0/regulators/regulators:regulator@0/regulator/regulator.7/microvolts -- 5000000 On 27 February 2018 2:45 AM, Peter Chen <hzpeterchen@xxxxxxxxx> wrote: > Currently, the wakeup only occurs entering "mem" low power mode, > it means the 2P5 is changed during "entering" process, so you may > need to measure it if 2P5 is here when the system is at "mem" low > power mode. Another way to check if it is vbus wakeup, you can > disable vbus wakeup by not setting MX6\_BM\_VBUS\_WAKEUP at usbmisc\_imx.c (...) > VBUS should be there at runtime due to you can find the HUB. Like the > 2P5, I hope you can measure it too. I've searched the whole board with my multimeter for something that uses the 2P5. According to the emCON-MX6x-Manual [3], there are several connectors that use 2.5V: SATA, PCIE, LVDS, HDMI, MIPI. I've found Pin 32 of the miniPCIe Socket to have ~2.30V. It is called I2C1_SDA. I wonder if this is a proper Pin to test 2P5? I couldn't find any information about what is connected to the 2P5 and what's not. Pin32(I2C_SDA) is powered in standby, indeed. Without enabling any additional wakup sources (after boot, only the wakeup button is enabled). Also the VBUS of the USB Port is on ~5,07V. During mem-standby without enabling additional wakeup sources (only wakeup button (gpio) is enabled) > To check if the wakeup signal is from the HUB, you may not enable wakeup > for below entry: > /sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/power/wakeup Having everything but /sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/power/wakeup enabled still wakes the system immediately. But disabling /sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/power/wakeup or /sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/power/wakeup or /sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/power/wakeup keeps the system in mem-sleep. Can I conclude from this that the hub is sending false plugin-messages to the usb1 in ci_hdrc.1 in 2184200? In a tree of devices, does a wakeup-enabled device need to have parents that are also wakeup-enabled to be able to wake up? Otherwise I don't understand, why I have to disable only one of the 3 entries to keep it in mem-sleep. > > Linux emtrion-mx6 4.9.7emtrion-mx6 #1 SMP PREEMPT Fri Jan 26 18:33:35 CET 2018 armv7l GNU/Linux > I assume this kernel is released by freescale, not upstream, right? Our kernel (and the whole board image) has been compiled/created by emtrion. I honestly have no clue where they obtained their sources from. But due to they are using an i.MX6S, i think they got the kernel sources from freescale/nxp. Do you know a way to find it out? Best regards, Ralf [3] emCON-MX6, Hardware Manual, Rev2 / 13.10.2017 (emCON-MX6x_HW_V002en.pdf) (https://www.emtrion.de/de/details_products-accessoires/emcon-mx6-57.html) -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
