Upstreaming Android driver wakelock usage using wakeup_sources
This covers the usptreaming of Android driver wakelock usage, utilizing the upstreamed wakeup_source infrastructure.
Blueprint information
- Status:
- Not started
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- None
- Direction:
- Needs approval
- Assignee:
- Zoran Markovic
- Definition:
- New
- Series goal:
- None
- Implementation:
- Unknown
- Milestone target:
- backlog
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Work covers trying to upstream any existing wakelock enablement in drivers from common.git using the upstream wakeup_source interfaces.
Work Items
Work items:
Review 3.9 based branch of common.git looking at wakelock additions to already upstream code: TODO
Review wakelock additions to mmc code: DONE
Rework mmc wakelock enablement to use wakeup_sources: DONE
Send out initial RFC of mmc wakeup_source patch to lkml (6/13): DONE
Review wakelock additions to evdev code (doesn't make sense to upstream): DONE
Ping Android and evdev/input maintainers to make sure upstreaming makes sense (Arve replied, doesn't make sense to upstream, instead userland should migrate to EPOLLWAKEUP): DONE
Review AOSP hardware kernel trees to see if there are any hardware specific wakelock patches that affect upstream drivers: TODO
Dependency tree
* Blueprints in grey have been implemented.