Tony Lindgren <tony@xxxxxxxxxxx> writes: > * Kevin Hilman <khilman@xxxxxx> [120504 09:31]: >> Hi Thomas, >> >> Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> writes: >> >> > I have an IGEPv2 revision 6 board, which uses the DM3730 OMAP3. With >> > 3.2 omap2plus_defconfig, the system boots fine and have a working shell >> > on ttyO2. On either 3.3, 3.4-rc5 or arm-soc/for-next from Arnd, the >> > system boots all the way up to showing the shell prompt, but I can't >> > type any character, as if UART RX was broken. >> >> On v3.4-rc, can you see if reverting bce492c04ba8fc66a4ea0a52b181ba255daaaf54 >> has any effect? >> >> That patch had some unfortunate side effects, but I haven't seen the >> problem you see, so I'm not sure if it's related. > > Reverting bce492c04ba8fc66a4ea0a52b181ba255daaaf54 is a broken solution > like you mentioned. But if it helps, then the proper fix is to add muxing > to board-*.c files for the uart pins and use omap_serial_init_port > for each uart instead of omap_serial_init. That should fix the wake-up > issues too. I agree on the final solution, but just wanted to see if the missing mux (and thus disabled runtime PM) is what's causing the problem. Kevin -- 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
