Lines Matching full:writeback

25  * Writeback connectors are used to expose hardware which can write the output
29  * * Writeback connectors don't provide a way to output visually to the user.
31  * * Writeback connectors are visible to userspace only when the client sets
34  * * Writeback connectors don't have EDID.
36  * A framebuffer may only be attached to a writeback connector when the
41  * Unlike with planes, when a writeback framebuffer is removed by userspace DRM
43  * because no method is provided to abort a writeback operation, and in any
44  * case making a new commit whilst a writeback is ongoing is undefined (see
45  * WRITEBACK_OUT_FENCE_PTR below). As soon as the current writeback is finished,
51  * Writeback connectors have some additional properties, which userspace
56  *	framebuffer to be written by the writeback connector. This property is
66  *	by the connector's writeback engine.
71  *	writeback is finished. The value should be the address of a 32-bit
77  *	applications making use of writeback connectors *always* retrieve an
148  * drm_writeback_connector_init - Initialize a writeback connector and its properties
150  * @wb_connector: Writeback connector to initialize
153  * @formats: Array of supported pixel formats for the writeback engine
155  * @possible_crtcs: possible crtcs for the internal writeback encoder
157  * This function creates the writeback-connector-specific properties if they
165  * set up writeback connectors.
199  * drm_writeback_connector_init_with_encoder - Initialize a writeback connector with
203  * @wb_connector: Writeback connector to initialize
206  * @formats: Array of supported pixel formats for the writeback engine
209  * This function creates the writeback-connector-specific properties if they
222  * set up writeback connectors if they want to manage themselves the lifetime of the
325  * drm_writeback_queue_job - Queue a writeback job for later signalling
326  * @wb_connector: The writeback connector to queue a job on
330  * writeback connector. It takes ownership of the writeback job and sets the
334  * Drivers must ensure that for a given writeback connector, jobs are queued in
378  * @cleanup_work: deferred cleanup of a writeback job
394  * drm_writeback_signal_completion - Signal the completion of a writeback job
395  * @wb_connector: The writeback connector whose job is complete
396  * @status: Status code to set in the writeback out_fence (0 for success)
399  * writeback job. It should be called as soon as possible after the hardware
402  * hardware completes writeback jobs in the same order as they are queued.