How projectceladon/drm-hwcomposer works
Project type and purpose
• drm_hwcomposer is a system‐level service and HAL implementation for Android’s hardware composer, using Linux DRM/KMS to drive displays. It implements both HWC2 (via hwc2_device) and HWC3 (via hwc3-server AIDL service), providing buffer inspection, atomic commits, vsync, hotplug handling, and composition planning on DRM‐capable hardware.
File structure
• Top-level modules:
• backend: core interfaces for managing DRM backends (clients, managers)
• bufferinfo: inspect and map graphic buffers (generic + legacy/platform-specific)
• compositor: plan atomic KMS compositions (DrmKmsPlan)
• drm: wrappers and helpers around DRM/KMS objects (connectors, CRTCs, planes, encoders, modes, atomic state)
• hwc2_device: Android HWC2 HAL entrypoint (implements HWC2 device callbacks)
• hwc3-server: Android HWC3 AIDL service implementation (Composer, ResourceManager, command engine)
• libhwcservice: shared client-side library for service interactions (icontrols, iservice, idiagnostic)
• utils: common utilities (UEvent listener, logging, spinlocks, property helpers)
• tests: unit and integration tests for key functionality
• Build and CI: Android.bp / Android.mk, GitLab CI, GitHub workflows, clang-format/tidy, build_deploy.sh, presubmit.sh.
README for additional insights
• Purpose: “universal HW composer implementation for Android”
• Encourages patches across porting, bugfixes, new features.