Lines Matching full:component
16 functional pipeline stages called components, and every component has some
301 struct komeda_pipeline/component
305 a similar architecture: Pipeline/Component to describe the HW features and
306 capabilities, and a specific component includes two parts:
309 - Specific component capabilities and features.
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
354 crtc/plane/connector. One KMS-obj cannot represent only one single component,
356 single component, usually that needs multiple components to fit the requirement.
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
393 Since the compiz component doesn't output alpha value, the slave pipeline
402 Make component/pipeline to be drm_private_obj
439 komeda component validation
452 setup 1: check if component is needed, like the scaler is optional depending
455 Setup 2: check user_state with component features and capabilities to see
458 user to component; fail if component has been assigned to another
460 Setup 3: configure the component_state, like set its input component,
461 convert user_state to component specific state.