• State
  • Locked Locked
  • Replies 9 replies
  • Subscribers 98 subscribers
  • Views 815 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

AM3354: USB HID suspend issue

Daisuke Maeda
Guru 20315 points
Part Number: AM3354


Our customer has the issue that the USB device sometimes does not work after their product with AM335x is left unattended for a while. It uses Linux kernel 4.9.69 and the kernel logs are as follows:

Jan 14 07:29:25 stretch-smarin kernel: [11469896.598117] usb 1-1: USB disconnect, device number 2
Jan 14 07:29:26 stretch-smarin kernel: [11469897.571492] usb 1-1: new full-speed USB device number 3 using musb-hdrc
Jan 14 07:29:27 stretch-smarin kernel: [11469897.767817] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0002/input/input2
Jan 14 07:29:27 stretch-smarin kernel: [11469897.786561] hid-multitouch 0003:06D3:6402.0002: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:29:44 stretch-smarin kernel: [11469915.304808] usb 1-1: USB disconnect, device number 3
Jan 14 07:29:45 stretch-smarin kernel: [11469916.271469] usb 1-1: new full-speed USB device number 4 using musb-hdrc
Jan 14 07:29:45 stretch-smarin kernel: [11469916.467437] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0003/input/input4
Jan 14 07:29:45 stretch-smarin kernel: [11469916.485783] hid-multitouch 0003:06D3:6402.0003: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:30:17 stretch-smarin kernel: [11469947.857416] usb 1-1: USB disconnect, device number 4
Jan 14 07:30:18 stretch-smarin kernel: [11469948.831476] usb 1-1: new full-speed USB device number 5 using musb-hdrc
Jan 14 07:30:18 stretch-smarin kernel: [11469949.027539] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0004/input/input6
Jan 14 07:30:18 stretch-smarin kernel: [11469949.046056] hid-multitouch 0003:06D3:6402.0004: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:30:22 stretch-smarin kernel: [11469953.658874] usb 1-1: USB disconnect, device number 5
Jan 14 07:30:25 stretch-smarin kernel: [11469956.101441] usb 1-1: new full-speed USB device number 6 using musb-hdrc
Jan 14 07:30:25 stretch-smarin kernel: [11469956.296645] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0005/input/input8
Jan 14 07:30:25 stretch-smarin kernel: [11469956.316077] hid-multitouch 0003:06D3:6402.0005: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:37:11 stretch-smarin kernel: [11470361.732397] usb 1-1: USB disconnect, device number 6
Jan 14 07:37:12 stretch-smarin kernel: [11470362.701445] usb 1-1: new full-speed USB device number 7 using musb-hdrc
Jan 14 07:37:12 stretch-smarin kernel: [11470362.896543] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0006/input/input10
Jan 14 07:37:12 stretch-smarin kernel: [11470362.915898] hid-multitouch 0003:06D3:6402.0006: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:37:17 stretch-smarin kernel: [11470367.813916] usb 1-1: USB disconnect, device number 7
Jan 14 07:37:18 stretch-smarin kernel: [11470368.781456] usb 1-1: new full-speed USB device number 8 using musb-hdrc
Jan 14 07:37:18 stretch-smarin kernel: [11470368.977396] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0007/input/input12
Jan 14 07:37:18 stretch-smarin kernel: [11470368.996096] hid-multitouch 0003:06D3:6402.0007: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:37:26 stretch-smarin kernel: [11470377.160245] usb 1-1: USB disconnect, device number 8
Jan 14 07:37:27 stretch-smarin kernel: [11470378.131496] usb 1-1: new full-speed USB device number 9 using musb-hdrc
Jan 14 07:37:27 stretch-smarin kernel: [11470378.327793] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0008/input/input14
Jan 14 07:37:27 stretch-smarin kernel: [11470378.346426] hid-multitouch 0003:06D3:6402.0008: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:42:40 stretch-smarin kernel: [11470690.943115] usb 1-1: USB disconnect, device number 9
Jan 14 07:42:42 stretch-smarin kernel: [11470693.381486] usb 1-1: new full-speed USB device number 10 using musb-hdrc
Jan 14 07:42:42 stretch-smarin kernel: [11470693.577271] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0009/input/input16
Jan 14 07:42:42 stretch-smarin kernel: [11470693.595969] hid-multitouch 0003:06D3:6402.0009: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:47:24 stretch-smarin kernel: [11470975.253861] usb 1-1: USB disconnect, device number 10
Jan 14 07:47:25 stretch-smarin kernel: [11470976.221458] usb 1-1: new full-speed USB device number 11 using musb-hdrc
Jan 14 07:47:25 stretch-smarin kernel: [11470976.417145] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.000A/input/input18
Jan 14 07:47:25 stretch-smarin kernel: [11470976.435816] hid-multitouch 0003:06D3:6402.000A: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:47:30 stretch-smarin kernel: [11470981.448828] usb 1-1: USB disconnect, device number 11
Jan 14 07:47:31 stretch-smarin kernel: [11470982.421451] usb 1-1: new full-speed USB device number 12 using musb-hdrc
Jan 14 07:47:31 stretch-smarin kernel: [11470982.617342] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.000B/input/input20
Jan 14 07:47:31 stretch-smarin kernel: [11470982.635996] hid-multitouch 0003:06D3:6402.000B: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:47:37 stretch-smarin kernel: [11470988.042223] usb 1-1: USB disconnect, device number 12
Jan 14 07:47:38 stretch-smarin kernel: [11470989.011466] usb 1-1: new full-speed USB device number 13 using musb-hdrc
Jan 14 07:47:38 stretch-smarin kernel: [11470989.207331] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.000C/input/input22
Jan 14 07:47:38 stretch-smarin kernel: [11470989.226016] hid-multitouch 0003:06D3:6402.000C: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 07:53:16 stretch-smarin kernel: [11471327.521958] usb 1-1: USB disconnect, device number 13
Jan 14 07:53:19 stretch-smarin kernel: [11471329.941473] usb 1-1: new full-speed USB device number 14 using musb-hdrc
Jan 14 07:53:19 stretch-smarin kernel: [11471330.136979] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.000D/input/input24
Jan 14 07:53:19 stretch-smarin kernel: [11471330.156284] hid-multitouch 0003:06D3:6402.000D: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:06:14 stretch-smarin kernel: [11472105.574324] usb 1-1: USB disconnect, device number 14
Jan 14 08:06:15 stretch-smarin kernel: [11472106.541446] usb 1-1: new full-speed USB device number 15 using musb-hdrc
Jan 14 08:06:16 stretch-smarin kernel: [11472106.737250] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.000E/input/input26
Jan 14 08:06:16 stretch-smarin kernel: [11472106.756487] hid-multitouch 0003:06D3:6402.000E: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:06:20 stretch-smarin kernel: [11472111.373929] usb 1-1: USB disconnect, device number 15
Jan 14 08:06:21 stretch-smarin kernel: [11472112.341448] usb 1-1: new full-speed USB device number 16 using musb-hdrc
Jan 14 08:06:21 stretch-smarin kernel: [11472112.537225] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.000F/input/input28
Jan 14 08:06:21 stretch-smarin kernel: [11472112.556609] hid-multitouch 0003:06D3:6402.000F: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:19:57 stretch-smarin kernel: [11472928.160003] usb 1-1: USB disconnect, device number 16
Jan 14 08:19:58 stretch-smarin kernel: [11472929.131547] usb 1-1: new full-speed USB device number 17 using musb-hdrc
Jan 14 08:19:58 stretch-smarin kernel: [11472929.327815] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0010/input/input30
Jan 14 08:19:58 stretch-smarin kernel: [11472929.346485] hid-multitouch 0003:06D3:6402.0010: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:20:03 stretch-smarin kernel: [11472933.969337] usb 1-1: USB disconnect, device number 17
Jan 14 08:20:05 stretch-smarin kernel: [11472936.421450] usb 1-1: new full-speed USB device number 18 using musb-hdrc
Jan 14 08:20:05 stretch-smarin kernel: [11472936.617073] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0011/input/input32
Jan 14 08:20:05 stretch-smarin kernel: [11472936.635809] hid-multitouch 0003:06D3:6402.0011: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:28:53 stretch-smarin kernel: [11473464.218175] usb 1-1: USB disconnect, device number 18
Jan 14 08:28:54 stretch-smarin kernel: [11473465.191495] usb 1-1: new full-speed USB device number 19 using musb-hdrc
Jan 14 08:28:54 stretch-smarin kernel: [11473465.387465] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0012/input/input34
Jan 14 08:28:54 stretch-smarin kernel: [11473465.406485] hid-multitouch 0003:06D3:6402.0012: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:40:05 stretch-smarin kernel: [11474136.460726] usb 1-1: USB disconnect, device number 19
Jan 14 08:40:06 stretch-smarin kernel: [11474137.431444] usb 1-1: new full-speed USB device number 20 using musb-hdrc
Jan 14 08:40:06 stretch-smarin kernel: [11474137.627746] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0013/input/input36
Jan 14 08:40:06 stretch-smarin kernel: [11474137.646287] hid-multitouch 0003:06D3:6402.0013: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:40:11 stretch-smarin kernel: [11474142.313146] usb 1-1: USB disconnect, device number 20
Jan 14 08:40:12 stretch-smarin kernel: [11474143.281428] usb 1-1: new full-speed USB device number 21 using musb-hdrc
Jan 14 08:40:12 stretch-smarin kernel: [11474143.476954] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0014/input/input38
Jan 14 08:40:12 stretch-smarin kernel: [11474143.495445] hid-multitouch 0003:06D3:6402.0014: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:41:54 stretch-smarin kernel: [11474245.111671] usb 1-1: USB disconnect, device number 21
Jan 14 08:41:56 stretch-smarin kernel: [11474247.541438] usb 1-1: new full-speed USB device number 22 using musb-hdrc
Jan 14 08:41:57 stretch-smarin kernel: [11474247.737238] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0015/input/input40
Jan 14 08:41:57 stretch-smarin kernel: [11474247.756530] hid-multitouch 0003:06D3:6402.0015: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 08:42:17 stretch-smarin kernel: [11474268.349413] usb 1-1: USB disconnect, device number 22
Jan 14 08:42:18 stretch-smarin kernel: [11474269.321460] usb 1-1: new full-speed USB device number 23 using musb-hdrc
Jan 14 08:42:18 stretch-smarin kernel: [11474269.517251] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0016/input/input42
Jan 14 08:42:18 stretch-smarin kernel: [11474269.536389] hid-multitouch 0003:06D3:6402.0016: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:05:59 stretch-smarin kernel: [11475689.970522] usb 1-1: USB disconnect, device number 23
Jan 14 09:06:00 stretch-smarin kernel: [11475690.941432] usb 1-1: new full-speed USB device number 24 using musb-hdrc
Jan 14 09:06:00 stretch-smarin kernel: [11475691.137171] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0017/input/input44
Jan 14 09:06:00 stretch-smarin kernel: [11475691.156416] hid-multitouch 0003:06D3:6402.0017: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:50:57 stretch-smarin kernel: [11478387.721630] usb 1-1: USB disconnect, device number 24
Jan 14 09:50:57 stretch-smarin kernel: [11478388.691440] usb 1-1: new full-speed USB device number 25 using musb-hdrc
Jan 14 09:50:58 stretch-smarin kernel: [11478388.886913] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0018/input/input46
Jan 14 09:50:58 stretch-smarin kernel: [11478388.906479] hid-multitouch 0003:06D3:6402.0018: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:51:04 stretch-smarin kernel: [11478395.391058] usb 1-1: USB disconnect, device number 25
Jan 14 09:51:07 stretch-smarin kernel: [11478397.781421] usb 1-1: new full-speed USB device number 26 using musb-hdrc
Jan 14 09:51:07 stretch-smarin kernel: [11478397.978083] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.0019/input/input48
Jan 14 09:51:07 stretch-smarin kernel: [11478397.996734] hid-multitouch 0003:06D3:6402.0019: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:56:10 stretch-smarin kernel: [11478701.069286] usb 1-1: USB disconnect, device number 26
Jan 14 09:56:11 stretch-smarin kernel: [11478702.041426] usb 1-1: new full-speed USB device number 27 using musb-hdrc
Jan 14 09:56:11 stretch-smarin kernel: [11478702.237220] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.001A/input/input50
Jan 14 09:56:11 stretch-smarin kernel: [11478702.255890] hid-multitouch 0003:06D3:6402.001A: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:57:43 stretch-smarin kernel: [11478794.440432] usb 1-1: USB disconnect, device number 27
Jan 14 09:57:44 stretch-smarin kernel: [11478795.411428] usb 1-1: new full-speed USB device number 28 using musb-hdrc
Jan 14 09:57:44 stretch-smarin kernel: [11478795.607402] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.001B/input/input52
Jan 14 09:57:44 stretch-smarin kernel: [11478795.626097] hid-multitouch 0003:06D3:6402.001B: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:58:11 stretch-smarin kernel: [11478822.665918] usb 1-1: USB disconnect, device number 28
Jan 14 09:58:12 stretch-smarin kernel: [11478823.631423] usb 1-1: new full-speed USB device number 29 using musb-hdrc
Jan 14 09:58:13 stretch-smarin kernel: [11478823.827645] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.001C/input/input54
Jan 14 09:58:13 stretch-smarin kernel: [11478823.846075] hid-multitouch 0003:06D3:6402.001C: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:58:22 stretch-smarin kernel: [11478832.749291] usb 1-1: USB disconnect, device number 29
Jan 14 09:58:24 stretch-smarin kernel: [11478835.141429] usb 1-1: new full-speed USB device number 30 using musb-hdrc
Jan 14 09:58:24 stretch-smarin kernel: [11478835.337087] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.001D/input/input56
Jan 14 09:58:24 stretch-smarin kernel: [11478835.356400] hid-multitouch 0003:06D3:6402.001D: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0
Jan 14 09:58:40 stretch-smarin kernel: [11478851.340695] usb 1-1: USB disconnect, device number 30
Jan 14 09:58:41 stretch-smarin kernel: [11478852.311462] usb 1-1: new full-speed USB device number 31 using musb-hdrc
Jan 14 09:58:41 stretch-smarin kernel: [11478852.507731] input: MITSUBISHI ELECTRIC USB Touch as /devices/platform/ocp/47400000.usb/47401400.usb/musb-hdrc.0/usb1/1-1/1-1:1.0/0003:06D3:6402.001E/input/input58
Jan 14 09:58:41 stretch-smarin kernel: [11478852.526316] hid-multitouch 0003:06D3:6402.001E: input: USB HID v1.11 Mouse [MITSUBISHI ELECTRIC USB Touch] on usb-musb-hdrc.0-1/input0

Older kernels have the issue with USB autosuspend.

e2e.ti.com/.../linux-am335x-issue-with-usb-hub

Does kernel 4.9.69 have the issue with USB autosuspend?

Best regards,

Daisuke

  • 0
    TI__Guru**** 173901 points

    Hi Daisuke,

    The log shows the USB device got disconnected in a few seconds to a few minutes.

    - Have you tried to disable USB autosuspend to see if the issue still happens?

    - Have you tried the USB HID device on AM335x EVM to see if the issue also happens?

  • 0 in reply to Bin Liu
    Guru 20315 points

    Hi Bin-san,

    Thank you for your reply.

    Our customer has not tried either of your suggestions.

    You mentioned the patch for the issue with USB autosuspend in the related thread, but the wiki page below you pointed to no longer exists.

    processors.wiki.ti.com/.../Sitara_Linux_MUSB_Issues

    Can I see a copy of this wiki page?

    I will check if kernel 4.9.69 already has the patch.

    Best regards,

    Daisuke

  • 0 in reply to Daisuke Maeda
    TI__Guru**** 173901 points

    Hi Daisuke-san,

    The kernel patches mentioned in the wiki are related to kernel v3.12 or v3.14. They should be already in kernel v4.9. I could convert the wiki to pdf and send to you, but I am afraid the links to the patches will be lost during the format conversion, so the document won't help you to find the detail of the patches.

    Please ask your customer to do the two simple tested I mentioned above, then we will debug from there.

  • 0 in reply to Bin Liu
    Guru 20315 points

    Hi Bin-san,

    Thank you for your reply.

    Our customer has tried it on EVM, but the issue cannot be reproduced. On the other hand, our customer has not yet tried to disable the USB autosuspend on a failed board because it is used by an enduser in the field.

    I have some questions that may be related to the issue.

     - Can VBUS be enabled (held at 5V) during the system suspend (suspend/resume)?

    I confirmed that VBUS is 0V during the system suspend (suspend/resume) on EVM.

     - Can it be check that the USB autosuspend is running?

     - Is VBUS enabled (held at 5V) during the USB autosuspend?

     - Can it be check that the CPUIdle is running?

     - Is VBUS enabled (held at 5V) during the CPUIdle?

    Best regards,

    Daisuke

  • 0 in reply to Daisuke Maeda
    TI__Guru**** 173901 points

    Hi Daisuke-san,

    Daisuke Maeda said:
     - Can VBUS be enabled (held at 5V) during the system suspend (suspend/resume)?

    I will try to modify the kernel to see if this is possible.

    Daisuke Maeda said:
     - Can it be check that the USB autosuspend is running?

    I will check how to do so in linux sysfs. Please note by default autosuspend is enabled.

    Daisuke Maeda said:
     - Is VBUS enabled (held at 5V) during the USB autosuspend?

    Yes.

    Daisuke Maeda said:
     - Can it be check that the CPUIdle is running?

    You can check it in kernel config:

    # zcat /proc/config.gz |grep CPUIDLE

    Daisuke Maeda said:
     - Is VBUS enabled (held at 5V) during the CPUIdle?

    Yes.

  • 0 in reply to Bin Liu
    Guru 20315 points

    Hi Bin-san,

    Thank you for your reply.

    The issue has not yet been reproduced on other boards.

    Should the usbx_drvvbus be configured as GPIO instead to avoid the VBUS to be 0V during the system suspend (suspend/resume)? If so, how to configure it?

    Does the increase in a value in the files listed below indicate that the CPUIdle was running?

    /sys/devices/system/cpu/cpu0/cpuidle/state0/residency
    /sys/devices/system/cpu/cpu0/cpuidle/state0/time
    /sys/devices/system/cpu/cpu0/cpuidle/state1/residency
    /sys/devices/system/cpu/cpu0/cpuidle/state1/time
    /sys/devices/system/cpu/cpu0/cpuidle/state1/s2idle/time

    # ls -l /sys/devices/system/cpu/cpu0/cpuidle/state0/
    -r--r--r-- 1 root root 4096 Apr 19 02:39 desc
    -rw-r--r-- 1 root root 4096 Apr 19 02:39 disable
    -r--r--r-- 1 root root 4096 Apr 19 02:39 latency
    -r--r--r-- 1 root root 4096 Apr 19 02:39 name
    -r--r--r-- 1 root root 4096 Apr 19 02:39 power
    -r--r--r-- 1 root root 4096 Apr 19 02:39 residency
    -r--r--r-- 1 root root 4096 Apr 19 02:39 time
    -r--r--r-- 1 root root 4096 Apr 19 02:39 usage
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/desc
    ARM WFI
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/disable
    0
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/latency
    1
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/name
    WFI
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/power
    4294967295
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/residency
    1
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/time
    34821129
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state0/usage
    32000

    # ls -l /sys/devices/system/cpu/cpu0/cpuidle/state1
    -r--r--r-- 1 root root 4096 Apr 19 02:41 desc
    -rw-r--r-- 1 root root 4096 Apr 19 02:41 disable
    -r--r--r-- 1 root root 4096 Apr 19 02:47 latency
    -r--r--r-- 1 root root 4096 Apr 19 02:47 name
    -r--r--r-- 1 root root 4096 Apr 19 02:47 power
    -r--r--r-- 1 root root 4096 Apr 19 02:47 residency
    drwxr-xr-x 2 root root 0 Apr 19 02:47 s2idle
    -r--r--r-- 1 root root 4096 Apr 19 02:47 time
    -r--r--r-- 1 root root 4096 Apr 19 02:47 usage
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/desc
    mpu_gate
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/disable
    0
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/latency
    130
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/name
    mpu_gate
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/power
    0
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/residency
    300
    # ls -l /sys/devices/system/cpu/cpu0/cpuidle/state1/s2idle/
    -r--r--r-- 1 root root 4096 Apr 19 02:49 time
    -r--r--r-- 1 root root 4096 Apr 19 02:49 usage
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/s2idle/time
    0
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/s2idle/usage
    0
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/time
    2176752017
    # cat /sys/devices/system/cpu/cpu0/cpuidle/state1/usage
    292466

    Our customer is trying to capture the suspend state on USB bus by protocol analyzer to see if the USB autosuspend occurs, but it has not yet.

    Does this situation indicate that the USB autosuspend is not working?

    Best regards,

    Daisuke

  • 0 in reply to Daisuke Maeda
    TI__Guru**** 173901 points

    Hi Daisuke-san,

    Daisuke Maeda said:
    The issue has not yet been reproduced on other boards.

    What are the "other boards"? Are they the same custom boards (which means the issue doesn't happen on all the custom boards?) or EVM?

    Daisuke Maeda said:
    Does this situation indicate that the USB autosuspend is not working?

    Please confirm whether the customer has disabled USB autosuspend to test this issue?

  • 0 in reply to Bin Liu
    Guru 20315 points

    Hi Bin-san,

    Thank you for your reply. Sorry for the late reply.

    > What are the "other boards"? Are they the same custom boards (which means the issue doesn't happen on all the custom boards?) or EVM?

    The issue occurs on some of the same custom boards, but not on the rest of them.

    > Please confirm whether the customer has disabled USB autosuspend to test this issue?

    Our customer tried to capture the suspended state on USB bus with USB autosuspend enabled to make sure that it is working.

    They did not load the firmware for power management running on Cortex-M3 core, so they load it and check if the issue reappears.

    Best regards,

    Daisuke

  • 0 in reply to Daisuke Maeda
    TI__Guru**** 173901 points

    Hi Daisuke-san,

    Daisuke Maeda said:

    > Please confirm whether the customer has disabled USB autosuspend to test this issue?

    Our customer tried to capture the suspended state on USB bus with USB autosuspend enabled to make sure that it is working.

    Please do the following:

    - add "usbcore.autosuspend=-1" to UBoot bootargs. You can add it in UBoot uEnv.txt if it exists; or you can do "setenv usbcore.autosuspend -1" on UBoot prompt;

    - run command "cat /proc/cmdline" after Linux is booted to ensure usbcore.autosuspend parameter is set correctly;

    This will ensure usb autosuspend is disabled.

    Daisuke Maeda said:
    They did not load the firmware for power management running on Cortex-M3 core, so they load it and check if the issue reappears.

    Does loading the CM3 firmware affect the issue? I guess probably not.