Lines Matching full:framebuffer

26  * ownership of DRM framebuffer memory and hand-over between drivers.
30  * driver that is currently associated with the given framebuffer memory.
31  * If the framebuffer is located at PCI BAR 0, the rsp code looks as in the
75  * framebuffer apertures automatically. Device drivers without knowledge of
76  * the framebuffer's location shall call drm_aperture_remove_framebuffers(),
77  * which removes all drivers for known framebuffer.
81  * given framebuffer memory. Ownership of the framebuffer memory is achieved
83  * is the owner of the framebuffer range. The function fails if the
84  * framebuffer is already by another driver. See below for an example.
110  *		// ... and acquire ownership of the framebuffer.
123  * for the registered framebuffer range, the aperture helpers call
125  * may not access the device's registers, framebuffer memory, ROM, etc
216  * devm_aperture_acquire_from_firmware - Acquires ownership of a firmware framebuffer
218  * @dev:	the DRM device to own the framebuffer memory
219  * @base:	the framebuffer's byte offset in physical memory
220  * @size:	the framebuffer size in bytes
222  * Installs the given device as the new owner of the framebuffer. The function
223  * expects the framebuffer to be provided by a platform device that has been
226  * framebuffer range, the firmware state gets lost. Aperture helpers will then
230  * The function fails if the framebuffer range, or parts of it, is currently