On Saturday 09 July 2011 03:08:10 Mark Brown wrote: > I've got a few ideas but nothing comprehensive right now; the main thing > I can think we're missing at the minute is more fine grained hooks > around stream start in order to allow things to clock off the audio > stream. Equally well none of the systems I've had to deal with have had > a particularly pressing problem here. Yeah, this is the first system if this kind I've seen as well. Anyway, we have these constraints, and these might come back in other designs in the future. We will be looking for better/cleaner way to handle this. > If the machine driver controls the system integration (as we're doing > for everything else) it's at least clear what's going on for this > particular system. My main concern here is making the code actually say > what's going on. Fair enough. > Could we split the rewrite out from the delay thing so we can review it > separately? This'd also be good from the point of view of documentation > of what's going on as the changelogs would provide a bit more details. Just to avoid confusion (in my part): if I split this patch to one big + several small incremental patches, which eventually lead to the current situation is what you were asking for? With the patches I can document the reasoning behind the non standard workarounds. Probably if we see them spread out, we might be able to find better ways for them... -- Péter -- 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
