Hi On Tue, 17 Jul 2012, Tero Kristo wrote: > The underlying issue still remains, we have errata i582 which doesn't > have any workarounds in the kernel yet. We should probably resurrect > something like this: > > http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg38834.html > > ... or just pull the part which adds the dynamic wakedep add / remove > for the per domain when attempting per OFF. Yep looks like Kevin had some comments on that patch that no one followed up on. Guess we need to figure out who will have time to revise and update it. A few comments on that patch. 1. Looks to me like the patch needs to be split into several smaller patches. One patch should deal with the serial changes. Another should deal with the pm34xx.c changes. 2. Looks like we also need a patch to run the McBSP2/3 sidetone loopback test. Then the pm34xx.c test code would be something like: if (omap_uart_test_erratum_i582() || omap_mcbsp_test_erratum_i582()) { pr_err("%s: erratum i582 encountered; applying workaround\n", __func__); .. etc. } 3. When the erratum is encountered, shouldn't the code schedule a CORE OFF transition to occur at the earliest possible moment, rather than just emitting a message? 4. The bug is only a problem when the PER serial ports/McBSP sidetone devices are in use, right? So if those devices aren't in use then we can defer the device tests until right before one of those devices is brought into use, no? 5. There needs to be a better way of determining if a device is affected by this than by testing uart->num. Adding a hwmod dev_attr flag would be my first inclination. - Paul -- 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
