Define a buffer object sharing API
One of the outcomes of the memory management mini-summit is the need for a mechanism to enable sharing of buffer objects between device drivers. This mechanism needs to support tracking of buffer metadata as well as metadata for multiple mappings (as the devices may all have a mapping simultaneously.
Blueprint information
- Status:
- Complete
- Approver:
- Jesse Barker
- Priority:
- High
- Drafter:
- Sumit Semwal
- Direction:
- Approved
- Assignee:
- Sumit Semwal
- Definition:
- Drafting
- Series goal:
- Accepted for 2011.11
- Implementation:
- Implemented
- Milestone target:
- backlog
- Started by
- Jesse Barker
- Completed by
- Ilias Biris
Related branches
Related bugs
Sprints
Whiteboard
Work items (11.06):
Understand requirements from various subsystems about buffer sharing: DONE
Study code of V4L2 and fbdev for their buffer object definitions: DONE
Study code of ALSA, user-space for their buffer object definitions: DONE
Study code of DSP / DVB for their buffer object definitions: DONE
NOTE: do we need to define a userspace API, ie. some common ioctls for things like finding offset of different color planes (to not have to constrain ourselves to packed-planar formats)
Work Items
Dependency tree
* Blueprints in grey have been implemented.