On Thu, May 13, 2010 at 4:36 PM, Mark Brown <broonie@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote: > >> I'm not a big fan of suspend blockers myself, but let's face it, _currently_ >> there's no alternative and we need to stop the trend, the sooner the better. > > I don't think this is a major part of the trend - like I say, the fact > that people have been working with an old kernel version is generally > a much more substantial issue than the wakelocks in the code I've seen. Current published trees are based on .32 (used for the coming-soon froyo release that's been in late QA for a while now) and forward development is moving to .34 post final (or in the case of tegra2, tracking .34-rc series as it happens). We've been actively snapping up to track mainline since we started doing this around 2.6.16. We'd *love* to be able to get more stuff sanely upstream instead of maintaining branches and rebasing every other mainline release or so. > The issue was that when I originally noticed the patch series was being > considered for mainline again was that one effect of using it in a > mobile phone with the standard Linux embedded audio subsystem would be > to break use cases such as audio on voice calls, which isn't really > desirable, and that there was no roadmap for how to fix that or any > other subsystems with similar issues. This didn't seem like it would > have been a good situation given that the major user is expected to be > Android, which is mainly for mobile phones. I'd love to have a separate discussion on using standard linux embedded audio for mobile devices -- one of my goals for 2010 is to try to migrate from our "one off" approach on MSM to making use of ALSA and standard interfaces. I have a lot of questions about handing encoded data (mp3/aac/etc) that will be processed by the DSP, how to approach routing control, and how to best interact with the user/kernel interface, etc. Brian -- 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
