This issue is still being worked on, so I guess you still could use it to your “advantage”, even if that’s not the purpose of it. I would suggest you to run some reliability tests to see if on every reboot your get the same behavior. However, the idea is to have this issue solved at some point, possibly in a future image. In that case you’ll have to keep your older image with the issue still running. I’m not sure if your application involves a long term use, but if that’s not the case go ahead and make use of it.
Thanks for your help @Pablo_Intel
I have found that the bug reliably results in no power to the otg on every other reboot.
However, I've also found a way to programmatically ensure no power to the otg (requires reboot) - for the event the bug is fixed. It's somewhat hackish but works. Steps:
mv g_multi.ko g_multi.ok-blah # undo rename to re-enable powering of otg on boot
The above steps also require that I
systemctl disable sshd.socket
Otherwise the boot waits for 2 mins (for hardware that won't appear)
(so no ssh access to board which is ok for my purposes)
I'm still interested in a method to disable power to the OTG while the Edison is still running. However I will follow this up with another thread.