Lines Matching full:framebuffer
19 * ownership of DRM framebuffer memory and hand-over between drivers.
23 * driver that is currently associated with the given framebuffer memory.
24 * If the framebuffer is located at PCI BAR 0, the rsp code looks as in the
64 * framebuffer apertures automatically. Device drivers without knowledge of
65 * the framebuffer's location shall call drm_aperture_remove_framebuffers(),
66 * which removes all drivers for known framebuffer.
70 * given framebuffer memory. Ownership of the framebuffer memory is achieved
72 * is the owner of the framebuffer range. The function fails if the
73 * framebuffer is already owned by another driver. See below for an example.
99 * // ... and acquire ownership of the framebuffer.
112 * for the registered framebuffer range, the aperture helpers call
114 * may not access the device's registers, framebuffer memory, ROM, etc
119 * devm_aperture_acquire_from_firmware - Acquires ownership of a firmware framebuffer
121 * @dev: the DRM device to own the framebuffer memory
122 * @base: the framebuffer's byte offset in physical memory
123 * @size: the framebuffer size in bytes
125 * Installs the given device as the new owner of the framebuffer. The function
126 * expects the framebuffer to be provided by a platform device that has been
129 * framebuffer range, the firmware state gets lost. Aperture helpers will then
133 * The function fails if the framebuffer range, or parts of it, is currently