Gap between Atomic Modesetting / KMS and ADF

Session information has not yet been published for this event.


One Line Summary

Looking at the KMS atomic modesetting API and examining the feature gap to Android's ADF


With the 4.2 kernel, the DRM/KMS atomic modesetting API is finally enabled by default, allowing userspace to submit whole configurations across a number of display elements, rather than the previous incremental approach. This session will look at the remaining feature and implementation work to be done on AMS, including the feature gap to Android’s Atomic Display Framework (ADF), and how to enable easy porting of Android drivers and userspace.

For a design over of atomic mode setting please read and


drm, kms, graphics, android, modesetting, atomic modesetting, ams, atomic display framework, adf, display


  • Rob Clark

    Red Hat


    Rob works in the (too small) intersection of open source graphics and ARM, writing open src gallium driver for snapdragon/adreno 2xx and 3xx GPUs, and EXA 2d support for z180. And currently writing his 3rd drm/kms driver.

  • Bw


    Daniel Vetter is the maintainer of the Intel drm/i915 graphics driver since a few years. Besides the usual maintainer duties and feature work he spends a sizeable amount of time in trying to rectify past mistakes in the drm subsystem. Of which there are a lot, and a lot of these mistakes are in the form of bad userspace API which can’t be removed anytime soon. He is working at the Intel Open Source Technology Center.