search for: vc4_plane

On Fri, May 11, 2018 at 04:59:17PM +0200, Boris Brezillon wrote: > Applying an underscan setup is just a matter of scaling all planes > appropriately and adjusting the CRTC X/Y offset to account for the > horizontal and vertical border. > > Create an vc4_plane_underscan_adj() function doing that and call it from > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > underscan properties to the HDMI connector. > > Signed-off-by: Boris Brezillon <boris.brezillon at bootlin.com> > --- > Changes in v2: > - Take...

...018 at 04:59:17PM +0200, Boris Brezillon wrote: > > > Applying an underscan setup is just a matter of scaling all planes > > > appropriately and adjusting the CRTC X/Y offset to account for the > > > horizontal and vertical border. > > > > > > Create an vc4_plane_underscan_adj() function doing that and call it from > > > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > > > underscan properties to the HDMI connector. > > > > > > Signed-off-by: Boris Brezillon <boris.brezillon at bootlin.com> &...

...t; > > > > Applying an underscan setup is just a matter of scaling all planes > > > > > appropriately and adjusting the CRTC X/Y offset to account for the > > > > > horizontal and vertical border. > > > > > > > > > > Create an vc4_plane_underscan_adj() function doing that and call it from > > > > > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > > > > > underscan properties to the HDMI connector. > > > > > > > > > > Signed-off-by: Boris Brezillon...

Applying an underscan setup is just a matter of scaling all planes appropriately and adjusting the CRTC X/Y offset to account for the horizontal and vertical border. Create an vc4_plane_underscan_adj() function doing that and call it from vc4_plane_setup_clipping_and_scaling() so that we are ready to attach underscan properties to the HDMI connector. Signed-off-by: Boris Brezillon <boris.brezillon at bootlin.com> --- Changes in v2: - Take changes on hborder/vborder meaning...

...: > On Fri, May 11, 2018 at 04:59:17PM +0200, Boris Brezillon wrote: > > Applying an underscan setup is just a matter of scaling all planes > > appropriately and adjusting the CRTC X/Y offset to account for the > > horizontal and vertical border. > > > > Create an vc4_plane_underscan_adj() function doing that and call it from > > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > > underscan properties to the HDMI connector. > > > > Signed-off-by: Boris Brezillon <boris.brezillon at bootlin.com> > > --- > &g...

...scan setup is just a matter of scaling all planes > > > > > > > appropriately and adjusting the CRTC X/Y offset to account for the > > > > > > > horizontal and vertical border. > > > > > > > > > > > > > > Create an vc4_plane_underscan_adj() function doing that and call it from > > > > > > > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > > > > > > > underscan properties to the HDMI connector. > > > > > > > > > > > > &...

...ris Brezillon wrote: > > > > Applying an underscan setup is just a matter of scaling all planes > > > > appropriately and adjusting the CRTC X/Y offset to account for the > > > > horizontal and vertical border. > > > > > > > > Create an vc4_plane_underscan_adj() function doing that and call it from > > > > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > > > > underscan properties to the HDMI connector. > > > > > > > > Signed-off-by: Boris Brezillon <boris.brezillon...

Applying an underscan setup is just a matter of scaling all planes appropriately and adjusting the CRTC X/Y offset to account for the horizontal and vertical border. Create an vc4_plane_underscan_adj() function doing that and call it from vc4_plane_setup_clipping_and_scaling() so that we are ready to attach underscan properties to the HDMI connector. Signed-off-by: Boris Brezillon <boris.brezillon at bootlin.com> --- Changes in v3: - Rebase on top of the "cursor rescal...

...t; Applying an underscan setup is just a matter of scaling all planes > > > > > > appropriately and adjusting the CRTC X/Y offset to account for the > > > > > > horizontal and vertical border. > > > > > > > > > > > > Create an vc4_plane_underscan_adj() function doing that and call it from > > > > > > vc4_plane_setup_clipping_and_scaling() so that we are ready to attach > > > > > > underscan properties to the HDMI connector. > > > > > > > > > > > > Signed-off-...

...-- drivers/gpu/drm/nouveau/nouveau_connector.h | 9 -- drivers/gpu/drm/nouveau/nouveau_display.c | 14 --- drivers/gpu/drm/nouveau/nouveau_display.h | 3 - drivers/gpu/drm/nouveau/nv50_display.c | 17 ++-- drivers/gpu/drm/vc4/vc4_hdmi.c | 25 ++++++ drivers/gpu/drm/vc4/vc4_plane.c | 49 ++++++++++- include/drm/drm_connector.h | 80 ++++++++++++++++++ 10 files changed, 310 insertions(+), 65 deletions(-) -- 2.14.1

...e HDMI connector drivers/gpu/drm/drm_atomic_uapi.c | 12 +++ drivers/gpu/drm/drm_connector.c | 127 ++++++++++++++++++++++++++++++ drivers/gpu/drm/vc4/vc4_crtc.c | 47 +++++++++++ drivers/gpu/drm/vc4/vc4_drv.h | 3 + drivers/gpu/drm/vc4/vc4_hdmi.c | 25 ++++++ drivers/gpu/drm/vc4/vc4_plane.c | 50 ++++++++++++ include/drm/drm_connector.h | 80 +++++++++++++++++++ 7 files changed, 344 insertions(+) -- 2.17.1

...nderscan setup into account when updating planes drm/vc4: Attach underscan props to the HDMI connector drivers/gpu/drm/drm_atomic.c | 12 ++++ drivers/gpu/drm/drm_connector.c | 120 ++++++++++++++++++++++++++++++++++++++++ drivers/gpu/drm/vc4/vc4_hdmi.c | 25 +++++++++ drivers/gpu/drm/vc4/vc4_plane.c | 49 +++++++++++++++- include/drm/drm_connector.h | 78 ++++++++++++++++++++++++++ 5 files changed, 283 insertions(+), 1 deletion(-) -- 2.14.1

.../gpu/drm/drm_atomic_uapi.c | 8 +++++--- > drivers/gpu/drm/i915/display/i9xx_plane.c | 3 +++ > drivers/gpu/drm/nouveau/dispnv04/crtc.c | 4 ++++ > drivers/gpu/drm/nouveau/dispnv50/wndw.c | 4 ++++ > drivers/gpu/drm/vc4/vc4_plane.c | 4 +++- The main question is why only these drivers were updated. > include/drm/drm_plane.h | 5 +++++ > 8 files changed, 29 insertions(+), 4 deletions(-) > > -- > 2.45.2 > -- With best wishes Dmitry

...| 8 +++++--- > >> drivers/gpu/drm/i915/display/i9xx_plane.c | 3 +++ > >> drivers/gpu/drm/nouveau/dispnv04/crtc.c | 4 ++++ > >> drivers/gpu/drm/nouveau/dispnv50/wndw.c | 4 ++++ > >> drivers/gpu/drm/vc4/vc4_plane.c | 4 +++- > > > > The main question is why only these drivers were updated. > > > > According to `git grep async_page_flip`, only those drivers supports > async page flip. The only corner case is radeon, that does supports > async but does...

...| 6 ++---- drivers/gpu/drm/vc4/vc4_dsi.c | 28 ++++++++++++++-------------- drivers/gpu/drm/vc4/vc4_hdmi.c | 30 +++++++++++++++--------------- drivers/gpu/drm/vc4/vc4_hvs.c | 2 +- drivers/gpu/drm/vc4/vc4_kms.c | 12 ++++++------ drivers/gpu/drm/vc4/vc4_plane.c | 9 +++++---- drivers/gpu/drm/vc4/vc4_v3d.c | 6 +++--- drivers/gpu/drm/vgem/Makefile | 1 - drivers/gpu/drm/via/Makefile | 1 - drivers/gpu/drm/virtio/Makefile | 2 -- drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +- drivers/gpu/drm/virt...

...| 6 ++---- drivers/gpu/drm/vc4/vc4_dsi.c | 28 ++++++++++++++-------------- drivers/gpu/drm/vc4/vc4_hdmi.c | 30 +++++++++++++++--------------- drivers/gpu/drm/vc4/vc4_hvs.c | 2 +- drivers/gpu/drm/vc4/vc4_kms.c | 12 ++++++------ drivers/gpu/drm/vc4/vc4_plane.c | 9 +++++---- drivers/gpu/drm/vc4/vc4_v3d.c | 6 +++--- drivers/gpu/drm/vgem/Makefile | 1 - drivers/gpu/drm/via/Makefile | 1 - drivers/gpu/drm/virtio/Makefile | 2 -- drivers/gpu/drm/virtio/virtgpu_debugfs.c | 2 +- drivers/gpu/drm/virt...