| /Linux-v6.1/drivers/staging/fbtft/ |
| D | Kconfig | 17 Framebuffer support for the AGM1264K-FL LCD display (two Samsung KS0108 compatible chips)
23 Generic Framebuffer support for BD663474
29 Generic Framebuffer support for HX8340BN
35 Generic Framebuffer support for HX8347D
41 Generic Framebuffer support for HX8353D
47 Generic Framebuffer support for HX8357D
53 Generic Framebuffer support for ILI9163
59 Generic Framebuffer support for ILI9320
65 Generic Framebuffer support for ILI9325
71 Generic Framebuffer support for ILI9340
[all …]
|
| /Linux-v6.1/drivers/firmware/ |
| D | sysfb.c | 8 * Simple-Framebuffer support
9 * Create a platform-device for any available boot framebuffer. The
10 * simple-framebuffer platform device is already available on DT systems, so
12 * platform device compatible with the "simple-framebuffer" DT object. If
13 * the framebuffer is incompatible, we instead create a legacy
14 * "vesa-framebuffer", "efi-framebuffer" or "platform-framebuffer" device and
16 * to pick these devices up without messing with simple-framebuffer drivers.
19 * If CONFIG_SYSFB_SIMPLEFB is not selected, never register "simple-framebuffer"
20 * platform devices, but only use legacy framebuffer devices for
55 * This disables the registration of system framebuffer devices that match the
[all …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
7 title: Simple Framebuffer
20 framebuffer@<address>.
42 framebuffer nodes, so that the firmware only needs to update the
47 If pre-filled framebuffer nodes are used, the firmware may need
57 - apple,simple-framebuffer
58 - allwinner,simple-framebuffer
59 - amlogic,simple-framebuffer
60 - const: simple-framebuffer
61 - const: simple-framebuffer
[all …]
|
| /Linux-v6.1/include/drm/ |
| D | drm_framebuffer.h | 40 * struct drm_framebuffer_funcs - framebuffer hooks
46 * Clean up framebuffer resources, specifically also unreference the
48 * framebuffer successfully created by calling
51 * framebuffer.
53 void (*destroy)(struct drm_framebuffer *framebuffer);
82 * framebuffer has changed and should be flushed to the display
97 int (*dirty)(struct drm_framebuffer *framebuffer,
119 * @dev: DRM device this framebuffer belongs to
139 * @format: framebuffer format information
143 * @funcs: framebuffer vfunc table
[all …]
|
| D | drm_gem_atomic_helper.h | 28 * For drivers with shadow planes, the maximum width of the framebuffer is
37 * For drivers with shadow planes, the maximum height of the framebuffer is
57 * @map: Mappings of the plane's framebuffer BOs in to kernel address space
65 * @data: Address of each framebuffer BO's data
98 * Drivers may use GEM BOs as shadow buffers over the framebuffer memory. This
113 * Drivers may use GEM BOs as shadow buffers over the framebuffer memory. This
135 * Drivers may use GEM BOs as shadow buffers over the framebuffer memory. This
|
| /Linux-v6.1/drivers/gpu/drm/ |
| D | drm_gem_framebuffer_helper.c | 3 * drm gem framebuffer helper functions
42 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
43 * @fb: Framebuffer
50 * Pointer to &drm_gem_object for the given framebuffer and plane index or NULL
84 drm_err(dev, "Failed to init framebuffer: %d\n", ret); in drm_gem_fb_init()
90 * drm_gem_fb_destroy - Free GEM backed framebuffer
91 * @fb: Framebuffer
93 * Frees a GEM backed framebuffer with its backing buffer(s) and the structure
110 * drm_gem_fb_create_handle - Create handle for GEM backed framebuffer
111 * @fb: Framebuffer
[all …]
|
| D | drm_aperture.c | 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
68 * framebuffer apertures automatically. Device drivers without knowledge of
69 * the framebuffer's location shall call drm_aperture_remove_framebuffers(),
70 * which removes all drivers for known framebuffer.
74 * given framebuffer memory. Ownership of the framebuffer memory is achieved
76 * is the owner of the framebuffer range. The function fails if the
77 * framebuffer is already owned by another driver. See below for an example.
103 * // ... and acquire ownership of the framebuffer.
[all …]
|
| D | drm_fb_dma_helper.c | 23 * DOC: framebuffer dma helper functions
25 * Provides helper functions for creating a DMA-contiguous framebuffer.
34 * callback function to create a DMA-contiguous framebuffer.
38 * drm_fb_dma_get_gem_obj() - Get DMA GEM object for framebuffer
39 * @fb: The framebuffer
42 * Return the DMA GEM object for given framebuffer.
60 * drm_fb_dma_get_gem_addr() - Get DMA (bus) address for framebuffer, for pixel
63 * @fb: The framebuffer
66 * Return the DMA GEM address for given framebuffer.
|
| D | drm_format_helper.c | 29 * drm_fb_clip_offset - Returns the clipping rectangles byte-offset in a framebuffer
30 * @pitch: Framebuffer line pitch in byte
31 * @format: Framebuffer format
35 * The byte offset of the clip rectangle's top-left corner within the framebuffer.
161 * @fb: DRM framebuffer
164 * This function copies parts of a framebuffer to display memory. Destination and
165 * framebuffer formats must match. No conversion takes place. The parameters @dst,
235 * @fb: DRM framebuffer
239 * This function copies parts of a framebuffer to display memory and swaps per-pixel
240 * bytes during the process. Destination and framebuffer formats must match. The
[all …]
|
| D | drm_framebuffer.c | 61 * and access the framebuffer object. The helper function
65 * The lifetime of a drm framebuffer is controlled with a reference count,
68 * which the last reference is never dropped (e.g. for the fbdev framebuffer
70 * struct) drivers can manually clean up a framebuffer at module unload time
180 drm_dbg_kms(dev, "bad framebuffer format %p4cc\n", in framebuffer_check()
186 drm_dbg_kms(dev, "bad framebuffer width %u\n", r->width); in framebuffer_check()
191 drm_dbg_kms(dev, "bad framebuffer height %u\n", r->height); in framebuffer_check()
296 drm_dbg_kms(dev, "bad framebuffer flags 0x%08x\n", r->flags); in drm_internal_framebuffer_create()
301 drm_dbg_kms(dev, "bad framebuffer width %d, should be >= %d && <= %d\n", in drm_internal_framebuffer_create()
306 drm_dbg_kms(dev, "bad framebuffer height %d, should be >= %d && <= %d\n", in drm_internal_framebuffer_create()
[all …]
|
| /Linux-v6.1/Documentation/userspace-api/media/v4l/ |
| D | vidioc-g-fbuf.rst | 39 to get and set the framebuffer parameters for a
59 :c:type:`v4l2_framebuffer`. Since the framebuffer is
63 framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` does, or it returns an error
69 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
93 :ref:`framebuffer-cap`.
98 :ref:`framebuffer-flags`
102 - Physical base address of the framebuffer, that is the address of
103 the pixel in the top left corner of the framebuffer. [#f1]_
112 find the corresponding Linux framebuffer device (see
129 - The pixel format of the framebuffer.
[all …]
|
| D | dev-osd.rst | 11 Some video output devices can overlay a framebuffer image onto the
35 Framebuffer section in Video Output Overlay Interface
38 Contrary to the *Video Overlay* interface the framebuffer is normally
40 accessible as a framebuffer device (``/dev/fbN``). Given a V4L2 device,
41 applications can find the corresponding framebuffer device by calling
43 other information, the physical address of the framebuffer in the
45 The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same
51 The width and height of the framebuffer depends on the current video
53 (or any other ioctl which would imply a framebuffer size change) with an
54 ``EBUSY`` error code until all applications closed the framebuffer device.
[all …]
|
| /Linux-v6.1/Documentation/fb/ |
| D | fbcon.rst | 2 The Framebuffer Console
5 The framebuffer console (fbcon), as its name implies, is a text
6 console running on top of the framebuffer device. It has the functionality of
8 features that can be attributed to the graphical nature of the framebuffer.
10 In the x86 architecture, the framebuffer console is optional, and
14 What are the features of fbcon? The framebuffer console supports
22 The framebuffer console can be enabled by using your favorite kernel
24 Console display driver support->Framebuffer Console Support.
28 In order for fbcon to activate, at least one framebuffer driver is
42 GOTCHA: A common bug report is enabling the framebuffer without enabling the
[all …]
|
| D | ep93xx-fb.rst | 26 are in pixel clocks. See Documentation/fb/framebuffer.rst for further
39 The framebuffer device can be registered by adding the following to
68 The physical address of the framebuffer can be controlled using the
72 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
75 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
77 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
79 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
86 The EP93xx framebuffer driver supports three optional platform
88 are called when the framebuffer driver is installed and removed
101 /* Board specific framebuffer setup */
[all …]
|
| D | deferred_io.rst | 10 - userspace app like Xfbdev mmaps framebuffer
20 completes the work associated with updating the framebuffer. this is
25 As can be seen from above, one benefit is roughly to allow bursty framebuffer
27 have gone quiet, we go and really update the framebuffer which would be
38 Another one may be if one has a device framebuffer that is in an usual format,
40 apps to pretend to have a normal framebuffer but reswizzle for the device
41 framebuffer at vsync time based on the touched pagelist.
45 No changes needed. mmap the framebuffer like normal and just use it.
|
| D | udlfb.rst | 8 pairing that with a hardware framebuffer (16MB) on the other end of the
9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
13 result with a local shadow of the remote hardware framebuffer to identify
32 Advantages of supporting DisplayLink chips with kernel framebuffer interface:
44 * Fbdev's mmap interface assumes a real hardware framebuffer is mapped.
51 * Fbdev does not arbitrate client ownership of the framebuffer well.
52 * Fbcon assumes the first framebuffer it finds should be consumed for console.
67 to open and begin writing to the framebuffer of the DisplayLink device using
76 code. They write to the standard framebuffer interface and rely on udlfb
112 module to track changed areas of the framebuffer by page faults.
[all …]
|
| /Linux-v6.1/drivers/video/fbdev/geode/ |
| D | Kconfig | 3 # Geode family framebuffer configuration
6 bool "AMD Geode family framebuffer support"
9 Say 'Y' here to allow you to select framebuffer drivers for
13 tristate "AMD Geode LX framebuffer support"
19 Framebuffer driver for the display controller integrated into the
28 tristate "AMD Geode GX framebuffer support"
34 Framebuffer driver for the display controller integrated into the
43 tristate "AMD Geode GX1 framebuffer support"
49 Framebuffer driver for the display controller integrated into the
|
| /Linux-v6.1/drivers/video/console/ |
| D | Kconfig | 74 bool "Framebuffer Console support"
80 Low-level framebuffer-based console driver.
88 This option enables the fbcon (framebuffer text-based) hardware
107 If this option is selected, the framebuffer console will
109 supports this feature). Otherwise, the framebuffer console will
110 always select the first framebuffer driver that is loaded. The latter
119 bool "Framebuffer Console Rotation"
122 Enable display rotation for the framebuffer console. This is done
125 such that other users of the framebuffer will remain normally
129 bool "Framebuffer Console Deferred Takeover"
[all …]
|
| /Linux-v6.1/drivers/video/fbdev/ |
| D | Kconfig | 34 buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
35 and the Framebuffer-HOWTO at
36 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
107 (accelerated) version and the framebuffer is in system RAM.
115 version and the framebuffer is in system RAM.
123 (accelerated) version and the framebuffer is in system RAM.
133 bool "Framebuffer foreign endianness support"
137 non-native endianness (e.g. Little-Endian framebuffer on a
216 tristate "Aeroflex Gaisler framebuffer support"
222 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
[all …]
|
| /Linux-v6.1/include/xen/interface/io/ |
| D | fbif.h | 21 * Framebuffer update notification event
36 * Framebuffer resize notification event
47 int32_t offset; /* start offset within framebuffer */
95 int32_t width; /* width of the framebuffer (in pixels) */
96 int32_t height; /* height of the framebuffer (in pixels) */
98 uint32_t mem_length; /* length of the framebuffer (in bytes) */
102 * Framebuffer page directory
105 * framebuffer pages, and can thus map up to PAGE_SIZE *
109 * Meg framebuffer with a max resolution of 12,800x10,240.
|
| /Linux-v6.1/drivers/media/pci/ivtv/ |
| D | Kconfig | 49 tristate "Conexant cx23415 framebuffer support"
55 This is a framebuffer driver for the Conexant cx23415 MPEG
64 bool "force cx23415 framebuffer init with x86 PAT enabled"
67 With PAT enabled, the cx23415 framebuffer driver does not
68 utilize write-combined caching on the framebuffer memory.
77 With this setting enabled, the framebuffer will initialize on
78 PAT-enabled systems but the framebuffer memory will be uncached.
|
| /Linux-v6.1/Documentation/arm/omap/ |
| D | dss.rst | 42 The DSS driver does not itself have any support for Linux framebuffer, V4L or
121 From omapdss point of view the V4L2 drivers should be similar to framebuffer
129 - Framebuffer is a memory area inside OMAP's SRAM/SDRAM that contains the
130 pixel data for the image. Framebuffer has width and height and color
133 screen. The overlay may be smaller than framebuffer, thus displaying only
134 part of the framebuffer. The position of the overlay may be changed if
140 A framebuffer can be connected to multiple overlays to show the same pixel data
143 framebuffer can be connected to any overlay.
169 overlays List of overlay numbers to which framebuffer pixels go
170 phys_addr Physical address of the framebuffer
[all …]
|
| /Linux-v6.1/Documentation/userspace-api/media/ |
| D | videodev2.h.rst.exceptions | 236 # V4L2 framebuffer caps and flags
238 replace define V4L2_FBUF_CAP_EXTERNOVERLAY framebuffer-cap
239 replace define V4L2_FBUF_CAP_CHROMAKEY framebuffer-cap
240 replace define V4L2_FBUF_CAP_LIST_CLIPPING framebuffer-cap
241 replace define V4L2_FBUF_CAP_BITMAP_CLIPPING framebuffer-cap
242 replace define V4L2_FBUF_CAP_LOCAL_ALPHA framebuffer-cap
243 replace define V4L2_FBUF_CAP_GLOBAL_ALPHA framebuffer-cap
244 replace define V4L2_FBUF_CAP_LOCAL_INV_ALPHA framebuffer-cap
245 replace define V4L2_FBUF_CAP_SRC_CHROMAKEY framebuffer-cap
247 replace define V4L2_FBUF_FLAG_PRIMARY framebuffer-flags
[all …]
|
| /Linux-v6.1/drivers/video/ |
| D | aperture.c | 25 * ownership of framebuffer memory and hand-over between drivers.
29 * driver that is currently associated with the given framebuffer memory.
62 * device instance. An active framebuffer will be located within this range.
65 * output on the framebuffer. If successful, the new driver can take over
69 * with every bus that has an addressable framebuffer. In the case of PCI,
72 * knowledge of the framebuffer's location can call
77 * framebuffer apertures. Ownership of the framebuffer memory is achieved
79 * driveris the owner of the framebuffer range. The function fails if the
80 * framebuffer is already owned by another driver. See below for an example.
120 * of the framebuffer memory from its probe function. This will fail if the
[all …]
|
| /Linux-v6.1/drivers/firmware/google/ |
| D | framebuffer-coreboot.c | 3 * framebuffer-coreboot.c
5 * Memory based framebuffer accessed through coreboot table.
29 struct lb_framebuffer *fb = &dev->framebuffer; in framebuffer_probe()
56 res.name = "Coreboot Framebuffer"; in framebuffer_probe()
64 "simple-framebuffer", 0, in framebuffer_probe()
68 pr_warn("coreboot: could not register framebuffer\n"); in framebuffer_probe()
86 .name = "framebuffer",
|
