running android on the mainline graphics stack€¦ · mainline atomic kms abi introduced ... -...

Open First

Running Android on theMainline Graphics StackRobert FossSenior Software Engineer

[email protected]@memcpy_io

mailto:[email protected]

● Android History● Android on Mainline● Current Status● Big Picture

Agenda

Android History

v3.10 v3.14 v3.18 v4.4 v4.90

500000

1000000

1500000

2000000

2500000

3000000

3500000

4000000

Qualcomm diff against mainline, # lines

Android History

Android History

● Android forked the Kernel

Android History

● Android forked the Kernel– Better Graphics stack was needed

Android History

● Android forked the Kernel– Better Graphics stack was needed– Support for low power was lacking

Android History

● Android forked the Kernel– Better Graphics stack was needed– Support for low power was lacking– Support for atomic operations missing

Android History

● Android forked the Kernel● Android Atomic Display Framework created

Android History


– Not extensible or generic

Android History


– Not extensible or generic– Only atomic for plane updates

Android History


– Not extensible or generic– Only atomic for plane updates– Not compatible with current ABI

Android History


– Not extensible or generic– Only atomic for plane updates– Not compatible with current ABI– Not upstreamable

Android History

● Android forked the Kernel● Android Atomic Display Framework created● Mainline Atomic KMS ABI introduced

Android History


– Supports the ADF usecases

Android History


– Supports the ADF usecases– Uses Properties to be generic

Android History


– Supports the ADF usecases– Uses Properties to be generic– Is now replacing ADF in vendor drivers

Android on Mainline

Android Graphics Stack

Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2

Subtitle Karla regular28pt

The Really Good Stuff ™


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


The Really Good Stuff ™ - No really, this is the whole point!


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Interface between applications and hardware


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2



Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Status Bar


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Na

vig

ati

on B

ar

Status Bar


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Na

vig

ati

on B

ar

Status Bar

Background


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


SurfaceFlinger speaks HWC to the Composer

Android Graphics StackWhat does the Hardware Composer do?


Get LayersThrough HWC API


Get LayersThrough HWC API

Optimize Layers forDisplay


Get LayersThroughHWC API

Optimize Layers forDisplay

OutputLayers ToDisplay HW


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


The non-kernel part of the graphics driver


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


The non-kernel part of the graphics driver - Hardware Composer


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


The non-kernel part of the graphics driver - Hardware Composer - OpenGL, Vulkan, memory allocator, etc.


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


The Linux Kernel

Mainline Graphics Stack

● Mainline now has good Graphics ABI


● Mainline now has good Graphics ABI● Google Pixel C shipped using Atomic KMS



– Android requires HWC implementation



– Android requires HWC implementation– Mesa and the Kernel does not implement it



– Android requires HWC implementation– Mesa and the Kernel does not implement it– drm_hwcomposer does!

Mainline Graphics StackWhat is the Hardware Composer?

Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Proprietary}

What is the Hardware Composer?

Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2


Kernel

SurfaceFlinger

Apps

HWC2

???


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2

Mainline Graphics StackWhat is the Hardware Composer?

Kernel

SurfaceFlinger

Apps

HWC2

drm_hwc

Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2

Driver


Kernel

SurfaceFlinger

Apps

HWC2

DRM

drm_hwc

libdrmmesa{


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2

Kernel

SurfaceFlinger

Apps

HWC2

drm_hwc

Driver


Kernel

SurfaceFlinger

Apps

HWC2

DRM

drm_hwc

libdrmmesa {


Kernel

Vendor driver

HWC2

SurfaceFlinger

Apps

HWC2

Kernel

SurfaceFlinger

Apps

HWC2

drm_hwc

Driver

Kernel

SurfaceFlinger

Apps

HWC2

DRM

drm_hwc

mesagralloc libdrm

drm_hwcomposerWhat is HWC2?


● Android added buffer Fence support


● Android added buffer Fence support– Ensures ordering between operations


● Android added buffer Fence support– Ensures ordering between operations– Synchronizes buffer sharing


● Android added buffer Fence support● HWC version 2 is improved using Fences


● Android added buffer Fence support● HWC version 2 is improved using Fences● Mainline received Fence support


● Android added buffer Fence support● HWC version 2 is improved using Fences● Mainline received Fence support● drm_hwcomposer implemented HWC2

drm_hwcomposer

● Previously hosted within ChromiumOS

Project Hosting

drm_hwcomposer

● Previously hosted within ChromiumOS● Now hosted on Freedesktop.org

Project Hosting

drm_hwcomposer

● Previously hosted within ChromiumOS● Now hosted on Freedesktop.org

– Thanks Google:● Sean Paul● Puneet Kumar● Marissa Wall

Project Hosting

drm_hwcomposer

● Previously hosted within ChromiumOS● Now hosted on Freedesktop.org● Contribute at gitlab.freedesktop.org

Project Hosting

Current Status

Current statusTested platforms

Current status

● iMX6– GPU: Vivante GC3000

Tested platforms

Current status

● Dragonboard 410c– GPU: Adreno 306

Tested platforms

Current status

● HiKey 960– GPU: Mali G71

Under Development

Big Picture

Big PictureMerging Android Features


● A new feature is introduced in Android


● A new feature is introduced in Android● Slowly migrated into the kernel


● A new feature is introduced in Android● Slowly migrated into the kernel● This does not to apply to all subsystems

5.00%

6.50%

3.50%

13.40%

11.90%

11.90%

3.30%

7.10%

5.40%

Qualcomm v4.9 Diff

arch/arm64/

arch/

drivers/clk/

drivers/gpu/

drivers/media/

drivers/platform/

drivers/power/

drivers/soc/qcom/

include/



● A new feature is introduced in Android● Slowly migrated into the kernel● This does not to apply to all subsystems● The diff size for drivers seem fairly constant

v3.10 v3.14 v3.18 v4.4 v4.90

500000

1000000

1500000

2000000

2500000

3000000

3500000

4000000

Qualcomm diff against mainline, # lines


Big PicturePush industry towards Open Source


● Increase device development speed


● Increase device development speed● Lower driver development costs


● Increase device development speed● Lower driver development costs● Increase driver quality


● Increase device development speed● Lower driver development costs● Increase driver quality● Push Open Source adoption forward

Thank you!@memcpy_io

running android on the mainline graphics stack€¦ · mainline atomic kms abi introduced ... -...

Documents