Lines Matching full:writeback

24  * Writeback connectors are used to expose hardware which can write the output
28  * * Writeback connectors don't provide a way to output visually to the user.
30  * * Writeback connectors are visible to userspace only when the client sets
33  * * Writeback connectors don't have EDID.
35  * A framebuffer may only be attached to a writeback connector when the
40  * Unlike with planes, when a writeback framebuffer is removed by userspace DRM
42  * because no method is provided to abort a writeback operation, and in any
43  * case making a new commit whilst a writeback is ongoing is undefined (see
44  * WRITEBACK_OUT_FENCE_PTR below). As soon as the current writeback is finished,
50  * Writeback connectors have some additional properties, which userspace
55  *	framebuffer to be written by the writeback connector. This property is
65  *	by the connector's writeback engine.
70  *	writeback is finished. The value should be the address of a 32-bit
76  *	applications making use of writeback connectors *always* retrieve an
153  * drm_writeback_connector_init - Initialize a writeback connector and its properties
155  * @wb_connector: Writeback connector to initialize
158  * @formats: Array of supported pixel formats for the writeback engine
161  * This function creates the writeback-connector-specific properties if they
169  * set up writeback connectors.
281  * drm_writeback_queue_job - Queue a writeback job for later signalling
282  * @wb_connector: The writeback connector to queue a job on
286  * writeback connector. It takes ownership of the writeback job and sets the
290  * Drivers must ensure that for a given writeback connector, jobs are queued in
334  * @cleanup_work: deferred cleanup of a writeback job
350  * drm_writeback_signal_completion - Signal the completion of a writeback job
351  * @wb_connector: The writeback connector whose job is complete
352  * @status: Status code to set in the writeback out_fence (0 for success)
355  * writeback job. It should be called as soon as possible after the hardware
358  * hardware completes writeback jobs in the same order as they are queued.