| /linux/drivers/staging/fbtft/ |
| H A D | Kconfig | 19 Framebuffer support for the AGM1264K-FL LCD display (two Samsung KS0108 compatible chips)
24 Generic Framebuffer support for BD663474
29 Generic Framebuffer support for HX8340BN
34 Generic Framebuffer support for HX8347D
39 Generic Framebuffer support for HX8353D
44 Generic Framebuffer support for HX8357D
49 Generic Framebuffer support for ILI9163
54 Generic Framebuffer support for ILI9320
59 Generic Framebuffer support for ILI9325
64 Generic Framebuffer support for ILI9340
[all …]
|
| /linux/include/drm/ |
| H A D | drm_framebuffer.h | 41 * struct drm_framebuffer_funcs - framebuffer hooks
47 * Clean up framebuffer resources, specifically also unreference the
49 * framebuffer successfully created by calling
52 * framebuffer.
54 void (*destroy)(struct drm_framebuffer *framebuffer);
83 * framebuffer has changed and should be flushed to the display
98 int (*dirty)(struct drm_framebuffer *framebuffer,
122 * @dev: DRM device this framebuffer belongs to
142 * @format: framebuffer format information
146 * @funcs: framebuffer vfunc table
[all …]
|
| H A D | drm_gem_atomic_helper.h | 27 * For drivers with shadow planes, the maximum width of the framebuffer is
36 * For drivers with shadow planes, the maximum height of the framebuffer is
65 * @map: Mappings of the plane's framebuffer BOs in to kernel address space
73 * @data: Address of each framebuffer BO's data
106 * Drivers may use GEM BOs as shadow buffers over the framebuffer memory. This
121 * Drivers may use GEM BOs as shadow buffers over the framebuffer memory. This
143 * Drivers may use GEM BOs as shadow buffers over the framebuffer memory. This
|
| /linux/Documentation/devicetree/bindings/display/ |
| H A D | simple-framebuffer.yaml | 4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
7 title: Simple Framebuffer
20 framebuffer@<address>.
47 framebuffer nodes, so that the firmware only needs to update the
52 If pre-filled framebuffer nodes are used, the firmware may need
62 - apple,simple-framebuffer
63 - allwinner,simple-framebuffer
64 - amlogic,simple-framebuffer
65 - const: simple-framebuffer
66 - const: simple-framebuffer
[all …]
|
| /linux/drivers/firmware/ |
| H A 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
59 * This disables the registration of system framebuffer devices that match the
[all …]
|
| /linux/drivers/gpu/drm/ |
| H A D | drm_gem_framebuffer_helper.c | 3 * drm gem framebuffer helper functions
44 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
45 * @fb: Framebuffer
52 * Pointer to &drm_gem_object for the given framebuffer and plane index or NULL
87 drm_err(dev, "Failed to init framebuffer: %d\n", ret); in drm_gem_fb_init()
93 * drm_gem_fb_destroy - Free GEM backed framebuffer
94 * @fb: Framebuffer
96 * Frees a GEM backed framebuffer with its backing buffer(s) and the structure
113 * drm_gem_fb_create_handle - Create handle for GEM backed framebuffer
114 * @fb: Framebuffer
[all …]
|
| H A D | drm_format_helper.c | 123 * drm_fb_clip_offset - Returns the clipping rectangles byte-offset in a framebuffer
124 * @pitch: Framebuffer line pitch in byte
125 * @format: Framebuffer format
129 * The byte offset of the clip rectangle's top-left corner within the framebuffer.
402 * @fb: DRM framebuffer
405 * This function copies parts of a framebuffer to display memory. Destination and
406 * framebuffer formats must match. No conversion takes place. The parameters @dst,
476 * @fb: DRM framebuffer
481 * This function copies parts of a framebuffer to display memory and swaps per-pixel
482 * bytes during the process. Destination and framebuffer formats must match. The
[all …]
|
| H A D | drm_fb_dma_helper.c | 26 * DOC: framebuffer dma helper functions
28 * Provides helper functions for creating a DMA-contiguous framebuffer.
37 * callback function to create a DMA-contiguous framebuffer.
41 * drm_fb_dma_get_gem_obj() - Get DMA GEM object for framebuffer
42 * @fb: The framebuffer
45 * Return the DMA GEM object for given framebuffer.
63 * drm_fb_dma_get_gem_addr() - Get DMA (bus) address for framebuffer, for pixel
66 * @fb: The framebuffer
69 * Return the DMA GEM address for given framebuffer.
|
| H A 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
162 drm_dbg_kms(dev, "bad framebuffer width %u\n", r->width); in framebuffer_check()
167 drm_dbg_kms(dev, "bad framebuffer height %u\n", r->height); in framebuffer_check()
270 drm_dbg_kms(dev, "bad framebuffer flags 0x%08x\n", r->flags); in drm_internal_framebuffer_create()
275 drm_dbg_kms(dev, "bad framebuffer width %d, should be >= %d && <= %d\n", in drm_internal_framebuffer_create()
280 drm_dbg_kms(dev, "bad framebuffer height %d, should be >= %d && <= %d\n", in drm_internal_framebuffer_create()
293 drm_dbg_kms(dev, "bad framebuffer format %p4cc\n", in drm_internal_framebuffer_create()
[all …]
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-fbuf.rst | 39 to get and set the framebuffer parameters for a
62 :c:type:`v4l2_framebuffer`. Since the framebuffer is
66 framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>` does, or it returns an error
72 the overlay and returns the framebuffer parameters as :ref:`VIDIOC_G_FBUF <VIDIOC_G_FBUF>`
90 :ref:`framebuffer-cap`.
95 :ref:`framebuffer-flags`
99 - Physical base address of the framebuffer, that is the address of
100 the pixel in the top left corner of the framebuffer.
105 find the corresponding Linux framebuffer device (see
123 - The pixel format of the framebuffer.
[all …]
|
| H A D | dev-osd.rst | 12 Some video output devices can overlay a framebuffer image onto the
36 Framebuffer chapter
39 Contrary to the *Video Overlay* interface the framebuffer is normally
41 accessible as a framebuffer device (``/dev/fbN``). Given a V4L2 device,
42 applications can find the corresponding framebuffer device by calling
44 other information, the physical address of the framebuffer in the
46 The framebuffer device ioctl ``FBIOGET_FSCREENINFO`` returns the same
52 The width and height of the framebuffer depends on the current video
54 (or any other ioctl which would imply a framebuffer size change) with an
55 ``EBUSY`` error code until all applications closed the framebuffer device.
[all …]
|
| /linux/Documentation/fb/ |
| H A 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
44 A common bug report is enabling the framebuffer without enabling the
[all …]
|
| H A 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
67 The physical address of the framebuffer can be controlled using the
71 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
74 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
76 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
78 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
84 The EP93xx framebuffer driver supports three optional platform
86 are called when the framebuffer driver is installed and removed
99 /* Board specific framebuffer setup */
[all …]
|
| H A 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 …]
|
| H A 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.
|
| /linux/drivers/video/fbdev/geode/ |
| H A D | Kconfig | 3 # Geode family framebuffer configuration
6 bool "AMD Geode family framebuffer support"
10 Say 'Y' here to allow you to select framebuffer drivers for
14 tristate "AMD Geode LX framebuffer support"
18 Framebuffer driver for the display controller integrated into the
27 tristate "AMD Geode GX framebuffer support"
31 Framebuffer driver for the display controller integrated into the
40 tristate "AMD Geode GX1 framebuffer support"
44 Framebuffer driver for the display controller integrated into the
|
| /linux/drivers/video/fbdev/ |
| H A D | Kconfig | 28 buffer devices. Please read <file:Documentation/fb/framebuffer.rst>
29 and the Framebuffer-HOWTO at
30 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
65 tristate "Aeroflex Gaisler framebuffer support"
69 This enables support for the SVGACTRL framebuffer in the GRLIB IP library from Aeroflex Gaisler.
134 Say Y to enable the Framebuffer driver for the Cirrus Logic
142 This is a framebuffer device for the SA-1100 LCD Controller.
143 See <http://www.linux-fbdev.org/> for information on framebuffer
360 Enabling this option will implement the linux framebuffer device
363 If you enable this option, you will get a planar framebuffer device
[all …]
|
| /linux/drivers/video/console/ |
| H A D | Kconfig | 74 bool "Framebuffer Console support"
81 Low-level framebuffer-based console driver.
89 This option enables the fbcon (framebuffer text-based) hardware
108 If this option is selected, the framebuffer console will
110 supports this feature). Otherwise, the framebuffer console will
111 always select the first framebuffer driver that is loaded. The latter
120 bool "Framebuffer Console Rotation"
123 Enable display rotation for the framebuffer console. This is done
126 such that other users of the framebuffer will remain normally
130 bool "Framebuffer Console Deferred Takeover"
[all …]
|
| /linux/drivers/firmware/google/ |
| H A D | framebuffer-coreboot.c | 3 * framebuffer-coreboot.c
5 * Memory based framebuffer accessed through coreboot table.
30 struct lb_framebuffer *fb = &dev->framebuffer; in framebuffer_probe()
43 * not pass a framebuffer information to the Linux kernel. in framebuffer_probe()
48 * that can scan-out using the system provided framebuffer. in framebuffer_probe()
71 res.name = "Coreboot Framebuffer"; in framebuffer_probe()
79 "simple-framebuffer", 0, in framebuffer_probe()
83 pr_warn("coreboot: could not register framebuffer\n"); in framebuffer_probe()
107 .name = "framebuffer",
114 MODULE_DESCRIPTION("Memory based framebuffer accessed through coreboot table");
|
| /linux/include/xen/interface/io/ |
| H A 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/Documentation/arch/arm/omap/ |
| H A 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/drivers/video/ |
| H A 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 * driver is 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 …]
|
| H A D | screen_info_pci.c | 12 static resource_size_t screen_info_lfb_offset; // framebuffer offset within resource
42 pr_info("Relocating firmware framebuffer to offset %pa[d] within %pr\n", in screen_info_apply_fixups()
45 pr_warn("Invalid relocating, disabling firmware framebuffer\n"); in screen_info_apply_fixups()
94 * for an offset if the framebuffer is behind a PCI host in screen_info_fixup_lfb()
104 * We've found a PCI device with the framebuffer in screen_info_fixup_lfb()
106 * relocation of the framebuffer aperture. in screen_info_fixup_lfb()
132 * screen_info_pci_dev() - Return PCI parent device that contains screen_info's framebuffer
|
| /linux/drivers/media/pci/ivtv/ |
| H A D | Kconfig | 49 tristate "Conexant cx23415 framebuffer support"
53 This is a framebuffer driver for the Conexant cx23415 MPEG
62 bool "force cx23415 framebuffer init with x86 PAT enabled"
65 With PAT enabled, the cx23415 framebuffer driver does not
66 utilize write-combined caching on the framebuffer memory.
75 With this setting enabled, the framebuffer will initialize on
76 PAT-enabled systems but the framebuffer memory will be uncached.
|
| /linux/drivers/gpu/drm/tegra/ |
| H A D | fb.c | 21 struct tegra_bo *tegra_fb_get_plane(struct drm_framebuffer *framebuffer, in tegra_fb_get_plane() argument
24 return to_tegra_bo(drm_gem_fb_get_obj(framebuffer, index)); in tegra_fb_get_plane()
27 bool tegra_fb_is_bottom_up(struct drm_framebuffer *framebuffer) in tegra_fb_is_bottom_up() argument
29 struct tegra_bo *bo = tegra_fb_get_plane(framebuffer, 0); in tegra_fb_is_bottom_up()
37 int tegra_fb_get_tiling(struct drm_framebuffer *framebuffer, in tegra_fb_get_tiling() argument
40 uint64_t modifier = framebuffer->modifier; in tegra_fb_get_tiling()
126 dev_err(drm->dev, "failed to initialize framebuffer: %d\n", in tegra_fb_alloc()
|