View Single Post
joerg_rw's Avatar
Posts: 2,222 | Thanked: 12,651 times | Joined on Mar 2010 @ SOL 3
#816
Originally Posted by egoshin View Post
It can be because HW still works as B-device but in HOST mode and driver knows this fact.

If so, I would like to use FORCE_HOST mode to switch in A-device state but who knows - it may be impossible without grounded ID pin and we should fix a driver.
No. The PHY chip and the musb in SoC obviously can talk to the hub, otherwise the vendor/product ids were not visible. I *honestly* doubt musb-hw on SoC has a problem like "I decide to cripple parts of data from device in HARDWARE because I'm in the wrong mode". In expression this is a SOFTWARE problem, not a hardware configuration issue.

And seriously - I thought we're thru with ID pin once and for all.

The above details show that driver is NOT in hostmode, but it still operates as a OTG device. We need to fix that - rather than any ID pin detection.

Last edited by joerg_rw; 2010-05-10 at 22:53.
 

The Following 5 Users Say Thank You to joerg_rw For This Useful Post: