hyprwm
/
wlroots-hyprland
mirror of https://github.com/hyprwm/wlroots-hyprland.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
wlroots-hyprland/include/backend/drm/iface.h

42 lines
1.3 KiB
C
Raw Normal View History

Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
#ifndef BACKEND_DRM_IFACE_H
#define BACKEND_DRM_IFACE_H
#include <stdbool.h>
#include <stdint.h>
backend/drm: clip FB damage The kernel complains when the damage exceeds the FB bounds: [73850.448326] i915 0000:00:02.0: [drm:drm_atomic_check_only] [PLANE:31:plane 1A] invalid damage clip 0 0 2147483647 2147483647 Make the DRM backend behave like the Wayland one and allow compositors to damage (0, 0, INT32_MAX, INT32_MAX) to repaint everything without needing to know the exact buffer size. Closes: https://github.com/swaywm/sway/issues/7632
2023-06-12 12:13:21 +02:00
#include <pixman.h>
Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
#include <xf86drm.h>
#include <xf86drmMode.h>
struct wlr_drm_backend;
Rename wlr_drm_output to wlr_drm_connector
2017-09-30 12:31:08 +02:00
struct wlr_drm_connector;
Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
struct wlr_drm_crtc;
backend/drm: introduce wlr_drm_connector_state Previously, we were copying wlr_output_state on the stack and patching it up to be guaranteed to have a proper drmModeModeInfo stored in it (and not a custom mode). Also, we had a bunch of helpers deriving DRM-specific information from the generic wlr_output_state. Copying the wlr_output_state worked fine so far, but with output layers we'll be getting a wl_list in there. An empty wl_list stores two pointers to itself, copying it on the stack blindly results in infinite loops in wl_list_for_each. To fix this, rework our DRM backend to stop copying wlr_output_state, instead add a new struct wlr_drm_connector_state which holds both the wlr_output_state and additional DRM-specific information.
2021-08-10 18:47:14 +02:00
struct wlr_drm_connector_state;
backend/drm: clip FB damage The kernel complains when the damage exceeds the FB bounds: [73850.448326] i915 0000:00:02.0: [drm:drm_atomic_check_only] [PLANE:31:plane 1A] invalid damage clip 0 0 2147483647 2147483647 Make the DRM backend behave like the Wayland one and allow compositors to damage (0, 0, INT32_MAX, INT32_MAX) to repaint everything without needing to know the exact buffer size. Closes: https://github.com/swaywm/sway/issues/7632
2023-06-12 12:13:21 +02:00
struct wlr_drm_fb;
Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
// Used to provide atomic or legacy DRM functions
struct wlr_drm_interface {
backend/drm: add libliftoff interface
2022-08-18 19:17:33 +02:00
bool (*init)(struct wlr_drm_backend *drm);
void (*finish)(struct wlr_drm_backend *drm);
backend/drm: remove backend arg from wlr_drm_interface.crtc_commit The callee can just get it from the wlr_drm_connector.
2021-07-08 16:31:09 +02:00
// Commit all pending changes on a CRTC.
bool (*crtc_commit)(struct wlr_drm_connector *conn,
backend/drm: introduce wlr_drm_connector_state Previously, we were copying wlr_output_state on the stack and patching it up to be guaranteed to have a proper drmModeModeInfo stored in it (and not a custom mode). Also, we had a bunch of helpers deriving DRM-specific information from the generic wlr_output_state. Copying the wlr_output_state worked fine so far, but with output layers we'll be getting a wl_list in there. An empty wl_list stores two pointers to itself, copying it on the stack blindly results in infinite loops in wl_list_for_each. To fix this, rework our DRM backend to stop copying wlr_output_state, instead add a new struct wlr_drm_connector_state which holds both the wlr_output_state and additional DRM-specific information.
2021-08-10 18:47:14 +02:00
const struct wlr_drm_connector_state *state, uint32_t flags,
bool test_only);
Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
};
Change iface prefix to suffix
2017-10-02 10:44:33 +02:00
extern const struct wlr_drm_interface atomic_iface;
extern const struct wlr_drm_interface legacy_iface;
backend/drm: add libliftoff interface
2022-08-18 19:17:33 +02:00
extern const struct wlr_drm_interface liftoff_iface;
Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
backend/drm: apply gamma LUT on page-flip
2020-05-07 17:50:40 +02:00
bool drm_legacy_crtc_set_gamma(struct wlr_drm_backend *drm,
output: make wlr_output_set_gamma atomic wlr_output_set_gamma is now double-buffered and applies the gamma LUT on the next output commit.
2020-05-14 18:27:02 +02:00
struct wlr_drm_crtc *crtc, size_t size, uint16_t *lut);
backend/drm: apply gamma LUT on page-flip
2020-05-07 17:50:40 +02:00
backend/drm: add libliftoff interface
2022-08-18 19:17:33 +02:00
bool create_mode_blob(struct wlr_drm_backend *drm,
struct wlr_drm_connector *conn,
const struct wlr_drm_connector_state *state, uint32_t *blob_id);
bool create_gamma_lut_blob(struct wlr_drm_backend *drm,
size_t size, const uint16_t *lut, uint32_t *blob_id);
backend/drm: clip FB damage The kernel complains when the damage exceeds the FB bounds: [73850.448326] i915 0000:00:02.0: [drm:drm_atomic_check_only] [PLANE:31:plane 1A] invalid damage clip 0 0 2147483647 2147483647 Make the DRM backend behave like the Wayland one and allow compositors to damage (0, 0, INT32_MAX, INT32_MAX) to repaint everything without needing to know the exact buffer size. Closes: https://github.com/swaywm/sway/issues/7632
2023-06-12 12:13:21 +02:00
bool create_fb_damage_clips_blob(struct wlr_drm_backend *drm,
backend/drm: handle output layer damage
2023-02-21 10:21:37 +01:00
int width, int height, const pixman_region32_t *damage, uint32_t *blob_id);
backend/drm: add libliftoff interface
2022-08-18 19:17:33 +02:00
Split DRM internal interface to its own header
2017-09-30 08:11:41 +02:00
#endif