search for: scanouts

Thanks for the patch. Tested-by: Yannick Fertr? <yannick.fertre at st.com><mailto:yannick.fertre at st.com> BR Yannick Fertr? On 1/10/20 10:21 AM, Thomas Zimmermann wrote: The new callback get_scanout_position() reads the current location of the scanout process. The operation is currentyl located in struct drm_driver, but really belongs to the CRTC. Drivers will be converted in

The new callback get_scanout_position() reads the current location of the scanout process. The operation is currentyl located in struct drm_driver, but really belongs to the CRTC. Drivers will be converted in separate patches. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/drm_vblank.c | 24 ++++++++---- include/drm/drm_drv.h |

On Fri, 10 Jan 2020, Thomas Zimmermann <tzimmermann at suse.de> wrote: > The new callback get_scanout_position() reads the current location of > the scanout process. The operation is currentyl located in struct > drm_driver, but really belongs to the CRTC. Drivers will be converted > in separate patches. > > Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de>

The new callback get_scanout_position() reads the current location of the scanout process. The operation is currently located in struct drm_driver, but really belongs to the CRTC. Drivers will be converted in separate patches. To help with the conversion, the timestamp calculation has been moved from drm_calc_vbltimestamp_from_scanoutpos() to

The new callback get_scanout_position() reads the current location of the scanout process. The operation is currently located in struct drm_driver, but really belongs to the CRTC. Drivers will be converted in separate patches. To help with the conversion, the timestamp calculation has been moved from drm_calc_vbltimestamp_from_scanoutpos() to

All users of struct drm_driver.get_scanout_position() have been covnerted to the respective CRTC helper function. Remove the callback from struct drm_driver. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de> --- drivers/gpu/drm/drm_vblank.c | 13 ++------- include/drm/drm_drv.h | 52 ------------------------------------ 2 files changed, 2 insertions(+), 63 deletions(-) diff

On Wed, Jan 15, 2020 at 01:16:34PM +0100, Thomas Zimmermann wrote: > The callback get_vblank_timestamp() is currently located in struct > drm_driver, but really belongs into struct drm_crtc_funcs. Add an > equivalent there. Driver will be converted in separate patches. > > The default implementation is drm_calc_vbltimestamp_from_scanoutpos(). > The patch adds

...from, along with a > + rectangle specified by x, y, width and height. What if x, y, width, and height are out-of-range for the given resource? What if width and height exceed the scanout width and height? Is it possible to unset the scanout for a resource? Can a resource be set on multiple scanouts? Does VIRTGPU_CMD_SET_SCANOUT need to be called between every VIRTGPU_CMD_RESOURCE_FLUSH or is does the assignment persist? > +VIRTGPU_CMD_RESOURCE_ATTACH_BACKING: > + Command: struct virtgpu_resource_attach_backing > + > + Assign backing pages to a resource. > + > + This ass...

...from, along with a > + rectangle specified by x, y, width and height. What if x, y, width, and height are out-of-range for the given resource? What if width and height exceed the scanout width and height? Is it possible to unset the scanout for a resource? Can a resource be set on multiple scanouts? Does VIRTGPU_CMD_SET_SCANOUT need to be called between every VIRTGPU_CMD_RESOURCE_FLUSH or is does the assignment persist? > +VIRTGPU_CMD_RESOURCE_ATTACH_BACKING: > + Command: struct virtgpu_resource_attach_backing > + > + Assign backing pages to a resource. > + > + This ass...

The callback get_vblank_timestamp() is currently located in struct drm_driver, but really belongs into struct drm_crtc_funcs. Add an equivalent there. Driver will be converted in separate patches. The default implementation is drm_calc_vbltimestamp_from_scanoutpos(). The patch adds drm_crtc_vblank_helper_get_vblank_timestamp(), which is an implementation for the CRTC callback. v2: * rename

I'm pleased to announce the 7.8.0 release of xf86-video-ati, the Xorg driver for ATI/AMD Radeon GPUs supported by the radeon kernel driver. This release supports xserver versions 1.10-1.19. Highlights: * Significant 2D compositing performance increase, in particular with glamor enabled. * Option "TearFree" can now prevent tearing in all possible display configurations (with

On Fri, 10 Jan 2020, Thomas Zimmermann <tzimmermann at suse.de> wrote: > The callback struct drm_driver.get_scanout_position() is deprecated in > favor of struct drm_crtc_helper_funcs.get_scanout_position(). > > i915 doesn't use CRTC helpers. The patch duplicates the caller > drm_calc_vbltimestamp_from_scanoutpos() for i915, such that the callback > function is not

...+{ + struct virtio_gpu_resp_edid *resp = + (struct virtio_gpu_resp_edid *)vbuf->resp_buf; + uint32_t scanout = le32_to_cpu(resp->scanout); + uint32_t size = le32_to_cpu(resp->size); + struct virtio_gpu_output *output; + struct edid *new_edid, *old_edid; + + if (scanout >= vgdev->num_scanouts) + return; + output = vgdev->outputs + scanout; + + if (drm_edid_is_valid((struct edid *)resp->edid)) { + new_edid = kmalloc(size, GFP_KERNEL); + memcpy(new_edid, resp->edid, size); + } else { + new_edid = NULL; + } + + spin_lock(&vgdev->display_info_lock); + old_edid = output-&...

...port. This is useful in > > cases where the guest only needs to use the GPU in a headless mode, or > > (such as in the CrOS usage) window surfaces are proxied to a host > > compositor. > > Why make that a compile time option? There is a config option for the > number of scanouts (aka virtual displays) a device has. Just set that > to zero (and fix the driver to not consider that configuration an > error). The goal is to not advertise DRIVER_MODESET (and DRIVER_ATOMIC).. I guess that could be done based on whether there are any scanouts, but it would mean making the...

Hi Am 15.01.20 um 15:49 schrieb Ville Syrj?l?: > On Wed, Jan 15, 2020 at 01:16:34PM +0100, Thomas Zimmermann wrote: >> The callback get_vblank_timestamp() is currently located in struct >> drm_driver, but really belongs into struct drm_crtc_funcs. Add an >> equivalent there. Driver will be converted in separate patches. >> >> The default implementation is

I'm pleased to announce the 1.2.0 release of xf86-video-amdgpu, the Xorg driver for AMD Radeon GPUs supported by the amdgpu kernel driver. This release supports xserver versions 1.10-1.19. Highlights: * Significant 2D compositing performance increase. * Option "TearFree" can now prevent tearing in all possible display configurations (with current versions of Xorg). Specifically,

...d graphics adapter. It can operate in 2D +mode and in 3D (virgl) mode. 3D mode will offload rendering ops to +the host gpu and therefore requires a gpu with 3D support on the host +machine. + +The initial version will have 2D mode only. It provides support for +ARGB Hardware cursors and multiple scanouts (aka heads). + + +features +-------- + +There are no feature bits (yet). +There will be one in the future for 3D mode support. + + +config space +------------ + +struct virtgpu_config { + uint32_t events_read; + uint32_t events_clear; + uint32_t num_scanouts; + uint32_t...

...esource? You'll get an error. > What if width and height exceed the scanout width and height? Using only a subrectangle of the resource for the scanout is legal. > Is it possible to unset the scanout for a resource? Yes, use resource_id 0. > Can a resource be > set on multiple scanouts? Yes. > Does VIRTGPU_CMD_SET_SCANOUT need to be called between every > VIRTGPU_CMD_RESOURCE_FLUSH or is does the assignment persist? Assignment is persistent. > > + the backing store for a resource. These pages are then used for the > > + transfer operations for that resourc...

On 09/11/2014 09:09 AM, Gerd Hoffmann wrote: > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> > --- > docs/specs/virtio-gpu.txt | 165 ++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 165 insertions(+) > create mode 100644 docs/specs/virtio-gpu.txt > > diff --git a/docs/specs/virtio-gpu.txt b/docs/specs/virtio-gpu.txt > new file mode 100644

On 09/11/2014 09:09 AM, Gerd Hoffmann wrote: > Signed-off-by: Gerd Hoffmann <kraxel at redhat.com> > --- > docs/specs/virtio-gpu.txt | 165 ++++++++++++++++++++++++++++++++++++++++++++++ > 1 file changed, 165 insertions(+) > create mode 100644 docs/specs/virtio-gpu.txt > > diff --git a/docs/specs/virtio-gpu.txt b/docs/specs/virtio-gpu.txt > new file mode 100644