Home
last modified time | relevance | path

Searched full:framebuffer (Results 1 – 25 of 513) sorted by relevance

12345678910>>...21

/linux/drivers/staging/fbtft/
H A DKconfig16 Framebuffer support for the AGM1264K-FL LCD display (two Samsung KS0108 compatible chips)
21 Generic Framebuffer support for BD663474
26 Generic Framebuffer support for HX8340BN
31 Generic Framebuffer support for HX8347D
36 Generic Framebuffer support for HX8353D
41 Generic Framebuffer support for HX8357D
46 Generic Framebuffer support for ILI9163
51 Generic Framebuffer support for ILI9320
56 Generic Framebuffer support for ILI9325
61 Generic Framebuffer support for ILI9340
[all …]
/linux/include/drm/
H A Ddrm_framebuffer.h41 * 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 Ddrm_gem_atomic_helper.h27 * 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/drivers/firmware/
H A Dsysfb.c8 * 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/Documentation/userspace-api/media/v4l/
H A Dvidioc-g-fbuf.rst39 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 Ddev-osd.rst12 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 …]
H A Dvideodev2.h.rst.exceptions248 # V4L2 framebuffer caps and flags
250 replace define V4L2_FBUF_CAP_EXTERNOVERLAY framebuffer-cap
251 replace define V4L2_FBUF_CAP_CHROMAKEY framebuffer-cap
252 replace define V4L2_FBUF_CAP_LIST_CLIPPING framebuffer-cap
253 replace define V4L2_FBUF_CAP_BITMAP_CLIPPING framebuffer-cap
254 replace define V4L2_FBUF_CAP_LOCAL_ALPHA framebuffer-cap
255 replace define V4L2_FBUF_CAP_GLOBAL_ALPHA framebuffer-cap
256 replace define V4L2_FBUF_CAP_LOCAL_INV_ALPHA framebuffer-cap
257 replace define V4L2_FBUF_CAP_SRC_CHROMAKEY framebuffer-cap
259 replace define V4L2_FBUF_FLAG_PRIMARY framebuffer-flags
[all …]
/linux/drivers/video/fbdev/geode/
H A DKconfig3 # 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/Documentation/fb/
H A Dep93xx-fb.rst26 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 Dudlfb.rst8 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 Ddeferred_io.rst10 - 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.
H A Dintel810.rst2 Intel 810/815 Framebuffer driver
17 This is a framebuffer driver for various Intel 810/815 compatible
31 Formula, or a framebuffer specific database to set the video mode
124 framebuffer memory. The intent is to avoid the memory blocks
127 avoid XFree86's usage and allows up to 7 MB/15 MB of framebuffer
143 enable MTRR. This allows data transfers to the framebuffer memory
194 This will initialize the framebuffer to 1024x768 at 8bpp. The framebuffer
254 f. If you want a framebuffer console, enable it under "Console
268 framebuffer driver code made this possible.
H A Dpxafb.rst88 base framebuffer (although under-neath the base is also possible). They
91 behave in a similar way as a framebuffer.
97 framebuffer, which means they have a start (x, y). This information
101 2. overlay framebuffer is allocated dynamically according to specified
134 framebuffer:
152 framebuffer framework, application has to take care of the offsets
153 and lengths of each component within the framebuffer.
/linux/include/xen/interface/io/
H A Dfbif.h21 * 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 Ddss.rst42 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/media/pci/ivtv/
H A DKconfig49 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/video/
H A Daperture.c25 * 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 Dscreen_info_pci.c11 static resource_size_t screen_info_lfb_offset; // framebuffer offset within resource
41 pr_info("Relocating firmware framebuffer to offset %pa[d] within %pr\n", in screen_info_apply_fixups()
44 pr_warn("Invalid relocating, disabling firmware framebuffer\n"); in screen_info_apply_fixups()
93 * for an offset if the framebuffer is behind a PCI host in screen_info_fixup_lfb()
103 * We've found a PCI device with the framebuffer in screen_info_fixup_lfb()
105 * relocation of the framebuffer aperture. in screen_info_fixup_lfb()
131 * screen_info_pci_dev() - Return PCI parent device that contains screen_info's framebuffer
/linux/drivers/gpu/drm/gma500/
H A Dframebuffer.c12 #include "framebuffer.h"
21 * psb_framebuffer_init - initialize a framebuffer
23 * @fb: framebuffer to set up
52 dev_err(dev->dev, "framebuffer init failed: %d\n", ret); in psb_framebuffer_init()
59 * psb_framebuffer_create - create a framebuffer backed by gt
65 * Create a framebuffer object backed by the gt, and fill in the
91 * psb_user_framebuffer_create - create framebuffer
96 * Create a new framebuffer backed by a userspace GEM object
/linux/arch/arm/boot/dts/mediatek/
H A Dmt6572-lenovo-a369i.dts22 framebuffer: framebuffer@9fa00000 { label
23 compatible = "simple-framebuffer";
47 framebuffer_reserved: framebuffer@9fa00000 {
H A Dmt6572-jty-d101.dts22 framebuffer: framebuffer@bf400000 { label
23 compatible = "simple-framebuffer";
52 framebuffer_reserved: framebuffer@bf400000 {
H A Dmt6582-alcatel-yarisxl.dts22 framebuffer: framebuffer@9fa00000 { label
23 compatible = "simple-framebuffer";
52 framebuffer_reserved: framebuffer@9fa00000 {
/linux/include/uapi/linux/
H A Dmatroxfb.h27 /* connect these outputs to this framebuffer */
29 /* which outputs are connected to this framebuffer */
31 /* which outputs are available for this framebuffer */
33 /* which outputs exist on this framebuffer */
/linux/drivers/video/fbdev/
H A Ds3c-fb.c9 * Samsung SoC Framebuffer driver
28 /* This driver will export a number of framebuffer interfaces depending
155 * struct s3c_fb_win - per window private data for each framebuffer.
158 * @fbinfo: Pointer pack to the framebuffer info for this window.
233 * s3c_fb_check_var() - framebuffer layer request to verify a given mode.
235 * @info: The framebuffer device.
237 * Framebuffer layer call to verify the given information and allow us to
449 * @sfb: The main framebuffer state.
462 /* see the note in the framebuffer datasheet about in s3c_fb_enable()
481 * s3c_fb_set_par() - framebuffer request to set new framebuffer state.
[all …]
H A Dgrvga.c3 * Driver for Aeroflex Gaisler SVGACTRL framebuffer device.
43 int fb_alloced; /* = 1 if framebuffer is allocated in main memory */
246 /* Set framebuffer base address */ in grvga_pan_display()
339 /* Expecting: "grvga: modestring, [addr:<framebuffer physical address>], [size:<framebuffer size>] in grvga_probe()
417 /* Got framebuffer base address from argument list */ in grvga_probe()
431 dev_err(&dev->dev, "error mapping framebuffer memory\n"); in grvga_probe()
443 "unable to allocate framebuffer memory (%lu bytes)\n", in grvga_probe()
472 "Aeroflex Gaisler framebuffer device (fb%d), %dx%d-%d, using %luK of video memory @ %p\n", in grvga_probe()
478 dev_err(&dev->dev, "failed to register framebuffer\n"); in grvga_probe()
483 __raw_writel(__raw_readl(&par->regs->status) | 1, /* Enable framebuffer */ in grvga_probe()
[all …]

12345678910>>...21