Comment 41 for bug 872833

1) At reboot, there is a crash from the usb side.

     Analysis
     ---------
     a) As part of reboot, the composite driver "composite_unbind" function removes the adb usb configuration(android_config_driver).
     b) After this, as part of sysfs close, adb_release, again tries to remove the same config which is already removed

   Fix
   ----
     In the adb_release code flow path, remove the adb usb config only when the composite device is connected.

    Yet to get review and comments from the usb team, on this.

2) The second issue as part of reboot, is there is a warning, from the clock framework, again for usb device as below,

       [ 78.357788] WARNING: at arch/arm/mach-ux500/clock.c:167 clk_disable+0x48/0x50()
       [ 78.374908] usb usb1: USB disconnect, device number 1
       [ 78.382843] musb-hdrc musb-hdrc: USB bus 1 deregistered
       [ 78.391265] Modules linked in: cw1200_core(C) mac80211 gator(O)
       [ 78.397277] [<c001f9cc>] (unwind_backtrace+0x0/0x148) from [<c06933c4>] (dump_stack+0x20/0x24)
       [ 78.409484] Restarting system.
       [ 78.412597] [<c06933c4>] (dump_stack+0x20/0x24) from [<c0036e34>] (warn_slowpath_common+0x64/0x74)
       [ 78.421630] [<c0036e34>] (warn_slowpath_common+0x64/0x74) from [<c0036e70>] (warn_slowpath_null+0x2c/0x34)
       [ 78.431304] [<c0036e70>] (warn_slowpath_null+0x2c/0x34) from [<c002aa88>] (clk_disable+0x48/0x50)
       [ 78.440216] [<c002aa88>] (clk_disable+0x48/0x50) from [<c039b0ac>] (ab8500_usb_phy_disable+0x60/0xc4)
       [ 78.449462] [<c039b0ac>] (ab8500_usb_phy_disable+0x60/0xc4) from [<c039b230>] (ab8500_usb_phy_disable_work+0x3c/0x54)
       [ 78.460266] [<c039b230>] (ab8500_usb_phy_disable_work+0x3c/0x54) from [<c0052504>] (process_one_work+0x138/0x50c)
       [ 78.470581] [<c0052504>] (process_one_work+0x138/0x50c) from [<c0052c90>] (worker_thread+0x1b0/0x488)
       [ 78.479858] [<c0052c90>] (worker_thread+0x1b0/0x488) from [<c005a4f8>] (kthread+0xa4/0xa8)
       [ 78.488189] [<c005a4f8>] (kthread+0xa4/0xa8) from [<c0017a70>] (kernel_thread_exit+0x0/0x8)

     Analysis in progress for this.

3) Finally, as seen from the above logs, there is a indication like "Restarting system", which had triggered a restart. May be because of the prcmu issue, mentioned by Robert Marklund in the above posts is stopping the reboot. Need to check with his workaround for this & will update here.