- 03 11月, 2015 2 次提交
-
-
由 Thierry Reding 提交于
There's no use building the individual drivers as separate modules because they are all only useful if combined into a single DRM/KMS device. Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org> Cc: Vincent Abriou <vincent.abriou@st.com> Signed-off-by: NThierry Reding <treding@nvidia.com> Reviewed-by: NVincent Abriou <vincent.abriou@st.com>
-
由 Thierry Reding 提交于
Non-legacy drivers should only use this API to allow per-CRTC data to be eventually moved into struct drm_crtc. Cc: Benjamin Gaignard <benjamin.gaignard@linaro.org> Cc: Vincent Abriou <vincent.abriou@st.com> Signed-off-by: NThierry Reding <treding@nvidia.com> Reviewed-by: NVincent Abriou <vincent.abriou@st.com>
-
- 03 8月, 2015 3 次提交
-
-
由 Vincent Abriou 提交于
Better fit STI hardware structure. Planes are no more responsible of updating mixer information such as z-order and status. It is now up to the CRTC atomic flush to do it. Plane actions (enable or disable) are performed atomically. Disabling of a plane is synchronize with the vsync event. Signed-off-by: NVincent Abriou <vincent.abriou@st.com> Reviewed-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org>
-
由 Vincent Abriou 提交于
replace all "sti_drm_" occurences by "sti_" Signed-off-by: NVincent Abriou <vincent.abriou@st.com> Reviewed-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org>
-
由 Vincent Abriou 提交于
Purpose is to simplify the STI driver: - remove layer structure - consider video subdev as part of the compositor (like mixer subdev) - remove useless STI_VID0 and STI_VID1 enum Signed-off-by: NVincent Abriou <vincent.abriou@st.com> Reviewed-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org>
-
- 05 2月, 2015 1 次提交
-
-
由 Jassi Brar 提交于
copy-paste wasn't followed by editing, do it. Signed-off-by: NJassi Brar <jaswinder.singh@linaro.org>
-
- 15 12月, 2014 1 次提交
-
-
When compiling in module some symbol aren't missing, export them correctly. Signed-off-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org> Signed-off-by: NDave Airlie <airlied@redhat.com>
-
- 11 12月, 2014 1 次提交
-
-
由 Benjamin Gaignard 提交于
High Quality Video Data Plane is hardware IP dedicated to video rendering. Compare to GPD (graphic planes) it have better scaler capabilities. HQVDP use VID layer to push data into hardware compositor without going into DDR. From data flow point of view HQVDP and VID are nested so HQVPD update/disable VID. Signed-off-by: NBenjamin Gaignard <benjamin.gaignard@linaro.org>
-