search for: scanout

Displaying 20 results from an estimated 217 matches for "scanout".

2020 Jan 14
1
[PATCH 01/23] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
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 separate patches. Signed-off-by: Thomas Zimmermann <tzimmermann at suse.de><mailto:tzimmermann at suse.de>...
2020 Jan 10
0
[PATCH 01/23] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
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...
2020 Jan 10
0
[PATCH 01/23] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
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> > --- &gt...
2020 Jan 20
0
[PATCH v3 02/22] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
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_fro...
2020 Jan 23
0
[PATCH v4 02/22] drm: Add get_scanout_position() to struct drm_crtc_helper_funcs
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_fro...
2020 Jan 10
0
[PATCH 09/23] drm: Remove struct drm_driver.get_scanout_position()
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 -----------------------------------...
2020 Jan 15
2
[Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...s 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 drm_crtc_vblank_helper_get_vblank_timestamp(), which is > an implementation for the CRTC callback. > > v2: > * rename helper to drm_crtc_vblank_helper_get_vblank_timestamp() > * replace drm_calc_vbltimestamp_from_scanoutpos() with > drm_crtc_vblank_...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...2D resource on the host. > + > + This creates a 2D resource on the host with the specified width, > + height and format. Only a small subset of formats are support. The > + resource ids are generated by the guest. Can the host refuse due to lack of resources? > +VIRTGPU_CMD_SET_SCANOUT: > + Command: struct virtgpu_set_scanout > + > + Set the scanout parameters for a single output. > + > + This sets the scanout parameters for a single scanout. The > + resource_id is the resource to be scanned out from, along with a > + rectangle specified by x, y, width a...
2014 Sep 12
2
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...2D resource on the host. > + > + This creates a 2D resource on the host with the specified width, > + height and format. Only a small subset of formats are support. The > + resource ids are generated by the guest. Can the host refuse due to lack of resources? > +VIRTGPU_CMD_SET_SCANOUT: > + Command: struct virtgpu_set_scanout > + > + Set the scanout parameters for a single output. > + > + This sets the scanout parameters for a single scanout. The > + resource_id is the resource to be scanned out from, along with a > + rectangle specified by x, y, width a...
2020 Jan 15
0
[PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
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 helper to drm_crtc_vblank_helper_get_vblank_timestamp() * replace drm_calc_vbltimestamp_from_scanoutpos() with drm_crtc_vblank_helper_get_vblank_timestamp() in do...
2016 Nov 17
0
[ANNOUNCE] xf86-video-ati 7.8.0
...RI3 by default when building for Xorg >= 1.18.3 Explicitly set the fbcon pixmap pitch again Add .editorconfig file Adapt to XF86_CRTC_VERSION 7 Only use RandR APIs if RandR is enabled Add explicit RADEON_DRM_QUEUE_ERROR define Don't enable micro-tiling for scanout buffers on pre-R600 Don't enable DRI3 by default with EXA Use EventCallback to avoid flushing every time in the FlushCallback Wait for pending flips to complete before turning off an output or CRTC Keep track of damage event related flushes per-client v2 Use drmmod...
2020 Jan 10
2
[PATCH 03/23] drm/i915: Don't use struct drm_driver.get_scanout_position()
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 needed. > > Signed-off...
2018 Sep 13
0
[PATCH 3/3] drm/virtio: add edid support
..._cb(struct virtio_gpu_device *vgdev, wake_up(&vgdev->resp_wq); } +static void virtio_gpu_cmd_get_edid_cb(struct virtio_gpu_device *vgdev, + struct virtio_gpu_vbuffer *vbuf) +{ + 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->e...
2023 Feb 27
2
[PATCH] drm/virtio: Add option to disable KMS support
...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 th...
2020 Jan 16
0
[Intel-gfx] [PATCH v2 03/21] drm: Add get_vblank_timestamp() to struct drm_crtc_funcs
...>> 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 helper to drm_crtc_vblank_helper_get_vblank_timestamp() >> * replace drm_calc_vbltimestamp_from_scanoutpos() with &...
2016 Nov 17
0
[ANNOUNCE] xf86-video-amdgpu 1.2.0
...of pixmap private when replacing BO Free priv in amdgpu_set_pixmap_bo also if priv->bo == NULL Adapt to XF86_CRTC_VERSION 7 Call amdgpu_glamor_create_screen_resources after ModifyPixmapHeader Simplify drmmode_set_mode_major error handling Make sure drmmode_crtc->scanout[] are destroyed when not needed present: Don't allow flipping when using a dedicated scanout buffer dri2: Don't allow flipping when using a dedicated scanout buffer present: Separate checks for flips vs unflips v2 Remove drmmode_load_palette Destroy all dedicat...
2014 Sep 11
0
[PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...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...
2014 Sep 12
0
[virtio-dev] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
..._ctrl_hdr.type in the response will be set to VIRTGPU_RESP_ERR_* then. Current implementation does that only on malloc() failure, there is no accounting (yet) to limit the amout of memory the guest is allowed to allocate. /me notes to write a section on error handling. > > +VIRTGPU_CMD_SET_SCANOUT: > > + Command: struct virtgpu_set_scanout > > + > > + Set the scanout parameters for a single output. > > + > > + This sets the scanout parameters for a single scanout. The > > + resource_id is the resource to be scanned out from, along with a > > + r...
2014 Sep 11
1
[Qemu-devel] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...o support for DMA transfers from s/unaccelerated/unaccelerated mode/ > + This creates a 2D resource on the host with the specified width, > + height and format. Only a small subset of formats are support. The s/support/supported/ and can you delineate that subset? > + This sets the scanout parameters for a single scanout. The > + resource_id is the resource to be scanned out from, along with a > + rectangle specified by x, y, width and height. Is it worth a mention here or generically up front where 0,0 is in relation to the screen, and in which direction positive numbers mo...
2014 Sep 11
1
[Qemu-devel] [PATCH 2/2] virtio-gpu/2d: add docs/specs/virtio-gpu.txt
...o support for DMA transfers from s/unaccelerated/unaccelerated mode/ > + This creates a 2D resource on the host with the specified width, > + height and format. Only a small subset of formats are support. The s/support/supported/ and can you delineate that subset? > + This sets the scanout parameters for a single scanout. The > + resource_id is the resource to be scanned out from, along with a > + rectangle specified by x, y, width and height. Is it worth a mention here or generically up front where 0,0 is in relation to the screen, and in which direction positive numbers mo...