| /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-6.6/drivers/staging/fbtft/ |
| D | Kconfig | 18 Framebuffer support for the AGM1264K-FL LCD display (two Samsung KS0108 compatible chips)
24 Generic Framebuffer support for BD663474
30 Generic Framebuffer support for HX8340BN
36 Generic Framebuffer support for HX8347D
42 Generic Framebuffer support for HX8353D
48 Generic Framebuffer support for HX8357D
54 Generic Framebuffer support for ILI9163
60 Generic Framebuffer support for ILI9320
66 Generic Framebuffer support for ILI9325
72 Generic Framebuffer support for ILI9340
[all …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /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-6.6/include/drm/ |
| 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 …]
|
| /kernel/linux/linux-6.6/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>.
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 …]
|
| /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-6.6/drivers/gpu/drm/ |
| 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
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.
[all …]
|
| 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 …]
|
| /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-6.6/Documentation/devicetree/bindings/reserved-memory/ |
| D | framebuffer.yaml | 4 $id: http://devicetree.org/schemas/reserved-memory/framebuffer.yaml#
7 title: /reserved-memory framebuffer node
17 const: framebuffer
19 This indicates a region of memory meant to be used as a framebuffer for
21 the framebuffer from being overwritten and use it as the backing memory
22 for a display device (such as simple-framebuffer).
35 framebuffer {
36 compatible = "simple-framebuffer";
46 fb: framebuffer@80000000 {
47 compatible = "framebuffer";
|
| /kernel/linux/linux-6.6/Documentation/userspace-api/media/v4l/ |
| 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 …]
|
| 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/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-6.6/drivers/video/fbdev/geode/ |
| 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"
19 Framebuffer driver for the display controller integrated into the
28 tristate "AMD Geode GX framebuffer support"
33 Framebuffer driver for the display controller integrated into the
42 tristate "AMD Geode GX1 framebuffer support"
47 Framebuffer driver for the display controller integrated into the
|
| /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-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-6.6/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/drivers/video/console/ |
| D | Kconfig | 73 bool "Framebuffer Console support"
79 Low-level framebuffer-based console driver.
87 This option enables the fbcon (framebuffer text-based) hardware
106 If this option is selected, the framebuffer console will
108 supports this feature). Otherwise, the framebuffer console will
109 always select the first framebuffer driver that is loaded. The latter
118 bool "Framebuffer Console Rotation"
121 Enable display rotation for the framebuffer console. This is done
124 such that other users of the framebuffer will remain normally
128 bool "Framebuffer Console Deferred Takeover"
[all …]
|
| /kernel/linux/linux-6.6/drivers/video/console/ |
| 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 …]
|
| /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 …]
|
| /kernel/linux/linux-6.6/drivers/video/fbdev/ |
| 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.
128 This framebuffer device driver is for the ARM PrimeCell PL110
156 Say Y to enable the Framebuffer driver for the Cirrus Logic
166 This is a framebuffer device for the SA-1100 LCD Controller.
167 See <http://www.linux-fbdev.org/> for information on framebuffer
389 Enabling this option will implement the linux framebuffer device
[all …]
|