Messages in this thread | | | Date | Mon, 30 Nov 2009 13:30:04 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH 0/2] staging/android fixes |
| |
> >> Arve's done a few revisions of the wakelock code with the linux-pm > >> list, and I know he's planning on trying to work through the remaining > >> issues (as I recall there was some discussion on read/write vs ioctl > >> interfaces to userspace) in the near future. > >> > >> This really is the one piece that has the most impact on everything > >> else -- maintaining versions of the various platform hardware drivers > >> with and without wakelock support is messy. > > > > It is really not that bad. Yes, it touches most drivers, but it is few > > lines per driver and easy to remove. > > > > Waiting for wakelocks (1year plus, AFAICT) before merging hw drivers > > seems like very slow way forward. > > I'm not suggesting we hold off on everything until they're in, just > saying it'll simplify things once they are.
That's certainly true :-).
> I'd like to get to a point where we can ship out of the upstream > kernel and that's going to need power management to work. If we can > sort out wakelocks (as it seemed like we were getting close to), > that's one less difference to maintain.
Yes, that would be nice. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
| |