Re: Wakeup from USB on i.MX6S

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Peter,

thank you a lot for your answere. This problem gives me headache for about 2 weeks now.
I have to admit that I'm not very experienced in working with embedded devices and it took me about one day to find ways to answere your questions. :)
I hope I've answered them. If not, please let me know. Maybe give some hint then about how to find out what you want to know. :)

On 24 February 2018 4:25 AM, Peter Chen <hzpeterchen@xxxxxxxxx> wrote:
> Ok, your problem is probably some powers are off and affect the USB vbus
> or dp/dm signals, and these powers are only off at mem state. Would you
> please check if LDO_2P5 is here
> -   LDO_2P5, it affects vbus comparator
> -   VBUS: please make sure vbus is there for ci_hdrc.1 port, since I see
>     there is a device on the port, maybe a hub?
     
I think (but am not 100% sure) the VDO_2P5 is here:

find / -name '*2p5*'
/sys/kernel/debug/regulator/20c8000.anatop:regulator-2p5-vdd2p5
/sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-2p5
/sys/firmware/devicetree/base/soc/aips-bus@02000000/anatop@020c8000/regulator-2p5
/sys/bus/platform/devices/20c8000.anatop:regulator-2p5
/sys/bus/platform/drivers/anatop_regulator/20c8000.anatop:regulator-2p5

pwd
/sys/kernel/debug/regulator/20c8000.anatop:regulator-2p5-vdd2p5
ls -l
-r--r--r--    1 root     root             0 Jan  1  1970 bypass_count
-r--r--r--    1 root     root             0 Jan  1  1970 open_count
-r--r--r--    1 root     root             0 Jan  1  1970 use_count
cat *
0
0
0

pwd
/sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-2p5
ls -l
lrwxrwxrwx    1 root     root             0 Feb 26 17:16 driver -> ../../../../../../bus/platform/drivers/anatop_regulator
-rw-r--r--    1 root     root          4096 Feb 26 17:16 driver_override
-r--r--r--    1 root     root          4096 Feb 26 17:16 modalias
lrwxrwxrwx    1 root     root             0 Feb 26 17:16 of_node -> ../../../../../../firmware/devicetree/base/soc/aips-bus@02000000/anatop@020c8000/regulator-2p5
drwxr-xr-x    2 root     root             0 Feb 26 17:16 power
drwxr-xr-x    3 root     root             0 Feb 26 14:16 regulator
lrwxrwxrwx    1 root     root             0 Feb 26 17:16 subsystem -> ../../../../../../bus/platform
-rw-r--r--    1 root     root          4096 Feb 26 14:16 uevent

/sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-2p5/regulator/regulator.3/max_microvolts: 2750000
/sys/devices/soc0/soc/2000000.aips-bus/20c8000.anatop/20c8000.anatop:regulator-2p5/regulator/regulator.3/microvolts: 2400000

And the nice tool devregs returns:
0x020c8130=0x00021073
0x020c8134=0x00021073
0x020c8138=0x00021073
0x020c813c=0x00021073
If I interpret this correct (and LSB is Bit no. 0), I think the register also says that the VDO_2P5 is here:
"0" "ENABLE_LINREG" "Control bit to enable the regulator output." [1, p4525f]
But I'm confused a little because Bit17=1:
"17" "OK_VDD2P5" "Status bit that signals when the regulator output is ok. 1 = regulator output > brownout target"



Now about the VBUS:
I think it is missing because I can only find it in dummy directories for 2184200.
find / -name '*vbus*'
/sys/kernel/debug/regulator/reg-dummy-regulator-dummy/2184200.usb-vbus
/sys/devices/platform/reg-dummy/regulator/regulator.0/2184200.usb-vbus
/sys/devices/soc0/supplies/supplies:otgvbus
/sys/firmware/devicetree/base/soc/aips-bus@02100000/usb@02184000/vbus-supply
/sys/firmware/devicetree/base/supplies/otgvbus
/sys/bus/platform/devices/supplies:otgvbus
/sys/bus/platform/drivers/reg-fixed-voltage/supplies:otgvbus
I hope this is the correct way of checking whether VBUS is here for ci_hdrc.1.



And about the device on the port: 
Plugging in a device creates a folder in /sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1/
called 1-1.1, 1-1.2 or 1-1.3 (for USB-Ports 1, 2 and 3).
I think our board supplier attached an usb hub to the cpu's usb interface located at 2184200.
(And the carrier board's manual confirms this: "All USB Host interfaces are driven by a 4-port USB Hub which is located on the Avari." [2, p13])

Is this a problem for the wakeup? There is a 4th port I've never used, because it's Mini-USB.
 


> Would you please show me your kernel version?
Of course.
uname --all
Linux emtrion-mx6 4.9.7emtrion-mx6 #1 SMP PREEMPT Fri Jan 26 18:33:35 CET 2018 armv7l GNU/Linux


Best regards,
Ralf


[1] i.MX 6Solo/6DualLite Applications Processor Reference Manual, Rev. 3, 09/2017 (IMX6SDLRM.pdf) (https://imxdev.gitlab.io/imxdoc/reference-manual-imx6/)
[2] emCON_Avari, emCON compliant baseboard, Hardware Description, Rev3 / 25.10.2016 (emCON_Avari_HW_v003en.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




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux