omap3530 usb host problems follow-up

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

 



I was following the thread
(http://marc.info/?l=linux-omap&m=123540972404602&w=2) and am confused
by one of the statements.  Felipe, you say the test of the ST_USBTTL
is wrong and suggested changing to test for '0'.  That means the TRM
is wrong?  It says ST_USBTTL = 1 = USB TTL cannot be accessed, but
your saying ST_USBTTL = 0 = USB TTL cannot be accessed.  How did you
determine this?

I was looking into because of problems with accessing the transceiver
from the EHCI host - and was trying to confirm all USB-related clocks
were in place and enabled.  I see the ST_USBTTL bit clearing as
expected (according to the TRM), so your comment and suggested code
change are puzzling.

twebb
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux