Documentation/gpu/komeda-kms.rst

15 architecture. A display pipeline is made up of multiple individual and
16 functional pipeline stages called components, and every component has some
17 specific capabilities that can give the flowed pipeline pixel data a
24 Layer is the first pipeline stage, which prepares the pixel data for the next
58 Final stage of display pipeline, Timing controller is not for the pixel
76 Possible D71 Pipeline usage
94 Single pipeline data flow
98    :alt: Single pipeline digraph
99    :caption: Single pipeline data flow
140 Dual pipeline with Slave enabled
144    :alt: Slave pipeline digraph
145    :caption: Slave pipeline enabled data flow
215 A complete display pipeline can be easily divided into three sub-pipelines
218 Layer(input) pipeline
239    :caption: Layer Split pipeline
250 Writeback(output) pipeline
282 Display output pipeline
305 a similar architecture: Pipeline/Component to describe the HW features and
321 Pipeline and component are used to describe how to handle the pixel data. We
353 Komeda abstracts resources by pipeline/component, but DRM-KMS uses
361 So, one KMS-Obj represents a sub-pipeline of komeda resources.
363 -   Plane: `Layer(input) pipeline`_
364 -   Wb_connector: `Writeback(output) pipeline`_
365 -   Crtc: `Display output pipeline`_
367 So, for komeda, we treat KMS crtc/plane/connector as users of pipeline and
368 component, and at any one time a pipeline/component only can be used by one
369 user. And pipeline/component will be treated as private object of DRM-KMS; the
372 How to map plane to Layer(input) pipeline
376 -   `Single pipeline data flow`_
377 -   `Dual pipeline with Slave enabled`_
379 The easiest way is binding a plane to a fixed Layer pipeline, but consider the
382 -   Layer Split, See `Layer(input) pipeline`_
391 -   Slave pipeline, See `Dual pipeline with Slave enabled`_
393     Since the compiz component doesn't output alpha value, the slave pipeline
398 So for komeda, the KMS-plane doesn't represent a fixed komeda layer pipeline,
402 Make component/pipeline to be drm_private_obj