UNDERSTANDING ANDROID GRAPHICS INTERNALS – GRALLOC AND HWCOMPOSER
gralloc and hwcomposer are hardware abstraction modules compliant to hw_module_t (defined in hardware/libhardware/include/hardware/hardware.h). Vendors mostly overwrite the android release implementation to suite their hardware platforms for optimal performance.
Gralloc’s hardware module ide is GRALLOC_HARDWARE_MODULE_ID and hosts two hw_device_t instances with the name of GRALLOC_HARDWARE_GPU0 and GRALLOC_HARDWARE_FB0 respectively.
The GRALLOC_HARDWARE_GPU0 device provides the APIs to allocate and release graphic buffer memory from ashmem driver; in case GRALLOC_USAGE_HW_FB is set, the buffer memory will be allocated from the frame buffer device, which are physically contiguous. In SurfaceFlinger
FramebufferSurface handles frame buffer allocation. The number of frame buffer to allocate is macro defined in NUM_FRAMEBUFFER_SURFACE_BUFFERS. The default value is 2.
In the framework, a singleton utility class GraphicBufferMapper (defined in frameworks/native/include/ui/GraphicBufferMapper.h) helps the mapping/unmapping of buffer_handle_t instance to virtual memory address, and register/unregister a remote buffer_handle_t
instance allocated out of the process. You may GraphicBuffer has a field to get a per process reference to the singleton class.
The GRALLOC_HARDWARE_FB0 device exposes methods to set frame swap interval and post a frame for rendering; it also exposes typical frame buffer device parameters for querying, which include frame buffer flags, geometrical sizes, resolutions, color scheme etc.
In SurfaceFlinger, the GRALLOC_HARDWARE_FB0 device is managed by HWComposer class; The latter manages the hwcomposer module as well.
The (*prepare)() and (*set)() methods in the abstract device are two methods to determine whether a surface layer shall be rendered through overlay and trigger the frame buffer switch respectively. The (*eventControl)() is for vsync purpose.