| /kernel/linux/linux-4.19/drivers/staging/fbtft/ |
| D | Kconfig | 16 Framebuffer support for the AGM1264K-FL LCD display (two Samsung KS0108 compatible chips)
22 Generic Framebuffer support for BD663474
28 Generic Framebuffer support for HX8340BN
34 Generic Framebuffer support for HX8347D
40 Generic Framebuffer support for HX8353D
46 Generic Framebuffer support for HX8357D
52 Generic Framebuffer support for ILI9163
58 Generic Framebuffer support for ILI9320
64 Generic Framebuffer support for ILI9325
70 Generic Framebuffer support for ILI9340
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/include/drm/ |
| D | drm_framebuffer.h | 35 * struct drm_framebuffer_funcs - framebuffer hooks
41 * Clean up framebuffer resources, specifically also unreference the
43 * framebuffer successfully created by calling
46 * framebuffer.
48 void (*destroy)(struct drm_framebuffer *framebuffer);
77 * framebuffer has changed and should be flushed to the display
89 int (*dirty)(struct drm_framebuffer *framebuffer,
111 * @dev: DRM device this framebuffer belongs to
131 * @format: framebuffer format information
135 * @funcs: framebuffer vfunc table
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.yaml | 4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
7 title: Simple Framebuffer Device Tree Bindings
21 framebuffer@<address>.
43 framebuffer nodes, so that the firmware only needs to update the
48 If pre-filled framebuffer nodes are used, the firmware may need
57 - allwinner,simple-framebuffer
58 - amlogic,simple-framebuffer
59 - const: simple-framebuffer
62 description: Location and size of the framebuffer memory
65 description: List of clocks used by the framebuffer.
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/kernel/ |
| D | sysfb.c | 8 * Simple-Framebuffer support for x86 systems
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_X86_SYSFB is not selected, we never register "simple-framebuffer"
20 * platform devices, but only use legacy framebuffer devices for
48 /* try to create a simple-framebuffer device */ in sysfb_init()
[all …]
|
| /kernel/linux/linux-4.19/arch/x86/kernel/ |
| D | sysfb.c | 12 * Simple-Framebuffer support for x86 systems
13 * Create a platform-device for any available boot framebuffer. The
14 * simple-framebuffer platform device is already available on DT systems, so
16 * platform device compatible with the "simple-framebuffer" DT object. If
17 * the framebuffer is incompatible, we instead create a legacy
18 * "vesa-framebuffer", "efi-framebuffer" or "platform-framebuffer" device and
20 * to pick these devices up without messing with simple-framebuffer drivers.
23 * If CONFIG_X86_SYSFB is not selected, we never register "simple-framebuffer"
24 * platform devices, but only use legacy framebuffer devices for
52 /* try to create a simple-framebuffer device */ in sysfb_init()
[all …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/display/ |
| D | simple-framebuffer.txt | 1 Simple Framebuffer
8 the chosen node (*). Simplefb nodes must be named "framebuffer@<address>".
28 It is advised that devicetree files contain pre-filled, disabled framebuffer
34 If pre-filled framebuffer nodes are used, the firmware may need extra
37 see e.g. simple-framebuffer-sunxi.txt .
40 - compatible: "simple-framebuffer"
41 - reg: Should contain the location and size of the framebuffer memory.
42 - width: The width of the framebuffer in pixels.
43 - height: The height of the framebuffer in pixels.
44 - stride: The number of bytes in each line of the framebuffer.
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/ |
| D | drm_gem_framebuffer_helper.c | 3 * drm gem framebuffer helper functions
43 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
44 * @fb: Framebuffer
51 * Pointer to &drm_gem_object for the given framebuffer and plane index or NULL
80 drm_err(dev, "Failed to init framebuffer: %d\n", ret); in drm_gem_fb_init()
86 * drm_gem_fb_destroy - Free GEM backed framebuffer
87 * @fb: Framebuffer
89 * Frees a GEM backed framebuffer with its backing buffer(s) and the structure
106 * drm_gem_fb_create_handle - Create handle for GEM backed framebuffer
107 * @fb: Framebuffer
[all …]
|
| D | drm_fb_cma_helper.c | 21 * DOC: framebuffer cma helper functions
24 * backed framebuffer.
27 * callback function to create a cma backed framebuffer.
31 * drm_fb_cma_get_gem_obj() - Get CMA GEM object for framebuffer
32 * @fb: The framebuffer
35 * Return the CMA GEM object for given framebuffer.
53 * drm_fb_cma_get_gem_addr() - Get physical address for framebuffer, for pixel
56 * @fb: The framebuffer
59 * Return the CMA GEM address for given framebuffer.
|
| /kernel/linux/linux-4.19/drivers/gpu/drm/ |
| D | drm_gem_framebuffer_helper.c | 2 * drm gem framebuffer helper functions
39 * drm_gem_fb_get_obj() - Get GEM object backing the framebuffer
40 * @fb: Framebuffer
47 * Pointer to &drm_gem_object for the given framebuffer and plane index or NULL
80 DRM_DEV_ERROR(dev->dev, "Failed to init framebuffer: %d\n", in drm_gem_fb_alloc()
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 …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-g-fbuf.rst | 39 to get and set the framebuffer parameters for a
59 struct :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>`
94 :ref:`framebuffer-cap`.
99 :ref:`framebuffer-flags`
103 - Physical base address of the framebuffer, that is the address of
104 the pixel in the top left corner of the framebuffer. [#f1]_
113 find the corresponding Linux framebuffer device (see
130 - 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 chapter
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 …]
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/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 chapter
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 …]
|
| /kernel/linux/linux-4.19/drivers/video/fbdev/geode/ |
| D | Kconfig | 2 # Geode family framebuffer configuration
5 bool "AMD Geode family framebuffer support"
8 Say 'Y' here to allow you to select framebuffer drivers for
12 tristate "AMD Geode LX framebuffer support"
18 Framebuffer driver for the display controller integrated into the
27 tristate "AMD Geode GX framebuffer support"
33 Framebuffer driver for the display controller integrated into the
42 tristate "AMD Geode GX1 framebuffer support"
48 Framebuffer driver for the display controller integrated into the
|
| /kernel/linux/linux-4.19/Documentation/fb/ |
| D | 00-INDEX | 25 - intro to and usage guide for the framebuffer console (fbcon).
26 framebuffer.txt
29 - info on the framebuffer driver for AMD Geode GX2 based processors.
31 - documentation for the Intel 810/815 framebuffer driver.
37 - info on the framebuffer driver for AMD Geode LX based processors.
39 - info on the Matrox framebuffer driver for Alpha, Intel and PPC.
53 - info on the SH7760/SH7763 integrated LCDC Framebuffer driver.
55 - info on the framebuffer device driver for various SiS chips.
57 - info on the framebuffer device driver for sm501 videoframebuffer.
63 info on the framebuffer driver for some Trident chip based cards.
[all …]
|
| D | fbcon.txt | 1 The Framebuffer Console
4 The framebuffer console (fbcon), as its name implies, is a text
5 console running on top of the framebuffer device. It has the functionality of
7 features that can be attributed to the graphical nature of the framebuffer.
9 In the x86 architecture, the framebuffer console is optional, and
13 What are the features of fbcon? The framebuffer console supports
20 The framebuffer console can be enabled by using your favorite kernel
22 buffer Devices->Console display driver support->Framebuffer Console Support.
26 In order for fbcon to activate, at least one framebuffer driver is
40 GOTCHA: A common bug report is enabling the framebuffer without enabling the
[all …]
|
| D | ep93xx-fb.txt | 26 are in pixel clocks. See Documentation/fb/framebuffer.txt for further
39 The framebuffer device can be registered by adding the following to
66 The physical address of the framebuffer can be controlled using the
69 EP93XXFB_USE_SDCSN0 Use SDCSn[0] for the framebuffer. This
72 EP93XXFB_USE_SDCSN1 Use SDCSn[1] for the framebuffer.
74 EP93XXFB_USE_SDCSN2 Use SDCSn[2] for the framebuffer.
76 EP93XXFB_USE_SDCSN3 Use SDCSn[3] for the framebuffer.
82 The EP93xx framebuffer driver supports three optional platform
84 are called when the framebuffer driver is installed and removed
97 /* Board specific framebuffer setup */
[all …]
|
| /kernel/linux/linux-5.10/drivers/video/console/ |
| D | Kconfig | 73 bool "Framebuffer Console support"
79 Low-level framebuffer-based console driver.
86 If this option is selected, the framebuffer console will
88 supports this feature). Otherwise, the framebuffer console will
89 always select the first framebuffer driver that is loaded. The latter
98 bool "Framebuffer Console Rotation"
101 Enable display rotation for the framebuffer console. This is done
104 such that other users of the framebuffer will remain normally
108 bool "Framebuffer Console Deferred Takeover"
111 If enabled this defers the framebuffer console taking over the
[all …]
|
| /kernel/linux/linux-4.19/drivers/video/console/ |
| D | Kconfig | 73 bool "Framebuffer Console support"
79 Low-level framebuffer-based console driver.
86 If this option is selected, the framebuffer console will
88 supports this feature). Otherwise, the framebuffer console will
89 always select the first framebuffer driver that is loaded. The latter
98 bool "Framebuffer Console Rotation"
101 Enable display rotation for the framebuffer console. This is done
104 such that other users of the framebuffer will remain normally
108 bool "Framebuffer Console Deferred Takeover"
111 If enabled this defers the framebuffer console taking over the
[all …]
|
| /kernel/linux/linux-4.19/drivers/video/fbdev/ |
| D | Kconfig | 39 buffer devices. Please read <file:Documentation/fb/framebuffer.txt>
40 and the Framebuffer-HOWTO at
41 <http://www.munted.org.uk/programming/Framebuffer-HOWTO-1.3.html> for more
81 If true, at least one selected framebuffer driver can take advantage
127 (accelerated) version and the framebuffer is in system RAM.
136 version and the framebuffer is in system RAM.
145 (accelerated) version and the framebuffer is in system RAM.
156 bool "Framebuffer foreign endianness support"
160 non-native endianness (e.g. Little-Endian framebuffer on a
246 tristate "Aeroflex Gaisler framebuffer support"
[all …]
|
| /kernel/linux/linux-5.10/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
73 If true, at least one selected framebuffer driver can take advantage
114 (accelerated) version and the framebuffer is in system RAM.
122 version and the framebuffer is in system RAM.
130 (accelerated) version and the framebuffer is in system RAM.
140 bool "Framebuffer foreign endianness support"
144 non-native endianness (e.g. Little-Endian framebuffer on a
223 tristate "Aeroflex Gaisler framebuffer support"
[all …]
|