On 05-06-15 10:01, Jeroen Hofstee wrote:
Hello Paul,
On 01-06-15 19:44, Paul Walmsley wrote:
The best way to make this work IMHO would be for us not to accept any
new
feature addition patches as long as there are warnings reported in the
test results. The only real exception that I would foresee is if those
warnings are due to something outside of our control, e.g., a crappy
bootloader, as I suspect the USB_OTG initiator warnings are for the
CM-T3517.
I doubt this is related to the bootloader. I have the suspicion that
is actually
a bug in linux but only triggered depending on whether the ROMcode setup
the USB OTG or not. Here is some data to backup my statement:
Linux booting without USB_OTG error trap
md 480022F0 1
480022f0: 0000032f /...
md 48002580 1
48002580: 0f00b7a2 ....
bit USBOTG_PHY_RESET is 0 -> out of reset
USB_OTG sees memory hole
md 480022F0 1
480022f0: 0000030f ....
md 48002580 1
48002580: 0f00c71e ....
USBOTG_PHY_RESET is 1 -> still in reset when booting linux.
Does that match with how your am3517 boards boot?
ps. the dumped register are CONTROL.CONTROL_STATUS and
CONTROL.CONTROL_DEVCONF2.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
