Home
last modified time | relevance | path

Searched full:display (Results 1 – 25 of 2657) sorted by relevance

12345678910>>...107

/kernel/linux/linux-5.10/drivers/gpu/drm/i915/
DMakefile73 display/intel_display_debugfs.o \
74 display/intel_pipe_crc.o
191 display/intel_atomic.o \
192 display/intel_atomic_plane.o \
193 display/intel_audio.o \
194 display/intel_bios.o \
195 display/intel_bw.o \
196 display/intel_cdclk.o \
197 display/intel_color.o \
198 display/intel_combo_phy.o \
[all …]
Di915_pci.c31 #include "display/intel_fbdev.h"
164 .display.has_overlay = 1, \
165 .display.cursor_needs_physical = 1, \
166 .display.overlay_needs_physical = 1, \
167 .display.has_gmch = 1, \
185 .display.has_overlay = 1, \
186 .display.overlay_needs_physical = 1, \
187 .display.has_gmch = 1, \
214 .display.has_fbc = 1,
220 .display.has_fbc = 1,
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/
Dallwinner,sun4i-a10-display-engine.yaml4 $id: http://devicetree.org/schemas/display/allwinner,sun4i-a10-display-engine.yaml#
7 title: Allwinner A10 Display Engine Pipeline Device Tree Bindings
14 The display engine pipeline (and its entry point, since it can be
18 The Allwinner A10 Display pipeline is composed of several components
22 display pipeline, when there are multiple components of the same
52 - allwinner,sun4i-a10-display-engine
53 - allwinner,sun5i-a10s-display-engine
54 - allwinner,sun5i-a13-display-engine
55 - allwinner,sun6i-a31-display-engine
56 - allwinner,sun6i-a31s-display-engine
[all …]
Dsimple-framebuffer.yaml4 $id: http://devicetree.org/schemas/display/simple-framebuffer.yaml#
15 the bootloader, with the assumption that the display hardware has
23 If the devicetree contains nodes for the display hardware used by a
25 display, which contains a phandle pointing to the primary display
30 It is advised to add display# aliases to help the OS determine how
31 to number things. If display# aliases are used, then if the simplefb
32 node contains a display property then the /aliases/display# path
33 must point to the display hw node the display property points to,
38 to it, or to the primary display hw node, as with display#
39 aliases. If display aliases are used then it should be set to the
[all …]
Dallwinner,sun4i-a10-display-frontend.yaml4 $id: http://devicetree.org/schemas/display/allwinner,sun4i-a10-display-frontend.yaml#
7 title: Allwinner A10 Display Engine Frontend Device Tree Bindings
14 The display engine frontend does formats conversion, scaling,
20 - allwinner,sun4i-a10-display-frontend
21 - allwinner,sun5i-a13-display-frontend
22 - allwinner,sun6i-a31-display-frontend
23 - allwinner,sun7i-a20-display-frontend
24 - allwinner,sun8i-a23-display-frontend
25 - allwinner,sun8i-a33-display-frontend
26 - allwinner,sun9i-a80-display-frontend
[all …]
Dcirrus,clps711x-fb.txt8 - display : phandle to a display node as described in
9 Documentation/devicetree/bindings/display/panel/display-timing.txt.
10 Additionally, the display node has to define properties:
25 display = <&display>;
28 display: display {
33 display-timings {
Dallwinner,sun4i-a10-display-backend.yaml4 $id: http://devicetree.org/schemas/display/allwinner,sun4i-a10-display-backend.yaml#
7 title: Allwinner A10 Display Engine Backend Device Tree Bindings
14 The display engine backend exposes layers and sprites to the system.
19 - allwinner,sun4i-a10-display-backend
20 - allwinner,sun5i-a13-display-backend
21 - allwinner,sun6i-a31-display-backend
22 - allwinner,sun7i-a20-display-backend
23 - allwinner,sun8i-a23-display-backend
24 - allwinner,sun8i-a33-display-backend
25 - allwinner,sun9i-a80-display-backend
[all …]
/kernel/linux/linux-5.10/Documentation/gpu/
Damdgpu-dc.rst2 drm/amd/display - Display Core (DC)
7 Because it is partially shared with other operating systems, the Display Core
10 1. **Display Core (DC)** contains the OS-agnostic components. Things like
12 2. **Display Manager (DM)** contains the OS-dependent components. Hooks to the
24 ``Display Core initialized with <version number here>``
26 AMDgpu Display Manager
29 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
32 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.h
38 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
41 .. kernel-doc:: drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c
[all …]
Di915.rst6 models) integrated GFX chipsets with both Intel display and rendering
13 This section covers core driver infrastructure used by both the display
67 Display Hardware Handling
70 This section covers everything related to the display hardware including
72 display, output probing and related topics.
79 its own tailor-made infrastructure for executing a display configuration
85 .. kernel-doc:: drivers/gpu/drm/i915/display/intel_frontbuffer.c
88 .. kernel-doc:: drivers/gpu/drm/i915/display/intel_frontbuffer.h
91 .. kernel-doc:: drivers/gpu/drm/i915/display/intel_frontbuffer.c
94 Display FIFO Underrun Reporting
[all …]
Dtegra.rst2 drm/tegra NVIDIA Tegra GPU and display driver
5 NVIDIA Tegra SoCs support a set of display, graphics and video functions via
21 - A KMS driver that supports the display controllers as well as a number of
64 The display hardware has remained mostly backwards compatible over the various
68 Display Controllers
71 Tegra SoCs have two display controllers, each of which can be associated with
72 zero or more outputs. Outputs can also share a single display controller, but
73 only if they run with compatible display timings. Two display controllers can
75 on two outputs don't match. A display controller is modelled as a CRTC in KMS
78 On Tegra186, the number of display controllers has been increased to three. A
[all …]
/kernel/linux/linux-5.10/drivers/media/platform/vsp1/
Dvsp1_dl.c3 * vsp1_dl.c -- R-Car VSP1 Display List
41 * struct vsp1_dl_ext_header - Extended display list header
45 * @pre_ext_dl_plist: start address of pre-extended display list bodies
47 * @post_ext_dl_plist: start address of post-extended display list bodies
79 * struct vsp1_pre_ext_dl_body - Pre Extended Display List Body
80 * @opcode: Extended display list command operation code
93 * struct vsp1_dl_body - Display list body
94 * @list: entry in the display list list of bodies
121 * struct vsp1_dl_body_pool - display list body pool
145 * struct vsp1_cmd_pool - Display List commands pool
[all …]
/kernel/linux/linux-5.10/drivers/video/fbdev/omap2/omapfb/
Domapfb-ioctl.c206 struct omap_dss_device *display = fb2display(fbi); in omapfb_setup_mem() local
216 if (display && display->driver->sync) in omapfb_setup_mem()
217 display->driver->sync(display); in omapfb_setup_mem()
281 struct omap_dss_device *display = fb2display(fbi); in omapfb_update_window() local
284 if (!display) in omapfb_update_window()
290 display->driver->get_resolution(display, &dw, &dh); in omapfb_update_window()
295 return display->driver->update(display, x, y, w, h); in omapfb_update_window()
301 struct omap_dss_device *display = fb2display(fbi); in omapfb_set_update_mode() local
307 if (!display) in omapfb_set_update_mode()
315 d = get_display_data(fbdev, display); in omapfb_set_update_mode()
[all …]
/kernel/linux/linux-5.10/drivers/staging/fbtft/
Dfbtft-core.c252 "%s: start_line=%u is larger than end_line=%u. Shouldn't happen, will do full display update\n", in fbtft_update_display()
260 …"%s: start_line=%u or end_line=%u is larger than max=%d. Shouldn't happen, will do full display up… in fbtft_update_display()
279 "%s: write_vmem failed to update display buffer\n", in fbtft_update_display()
296 "Display update: %ld kB/s, fps=%ld\n", in fbtft_update_display()
313 /* Mark display lines/area as dirty */ in fbtft_mkdirty()
321 /* Schedule deferred_io to update display (no-op if already on queue)*/ in fbtft_mkdirty()
337 /* set display line markers as clean */ in fbtft_deferred_io()
342 /* Mark display lines as dirty */ in fbtft_deferred_io()
520 * @display: pointer to structure describing the display
522 * @pdata: platform data for the display in use
[all …]
/kernel/linux/linux-5.10/drivers/acpi/acpica/
Dutbuffer.c22 * display - BYTE, WORD, DWORD, or QWORD display:
27 * base_offset - Beginning buffer offset (display only)
34 void acpi_ut_dump_buffer(u8 *buffer, u32 count, u32 display, u32 base_offset) in acpi_ut_dump_buffer() argument
40 u32 display_data_only = display & DB_DISPLAY_DATA_ONLY; in acpi_ut_dump_buffer()
42 display &= ~DB_DISPLAY_DATA_ONLY; in acpi_ut_dump_buffer()
49 display = DB_BYTE_DISPLAY; in acpi_ut_dump_buffer()
69 acpi_os_printf("%*s", ((display * 2) + 1), " "); in acpi_ut_dump_buffer()
70 j += display; in acpi_ut_dump_buffer()
74 switch (display) { in acpi_ut_dump_buffer()
76 default: /* Default is BYTE display */ in acpi_ut_dump_buffer()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/
Dpanel-simple.yaml4 $id: http://devicetree.org/schemas/display/panel/panel-simple.yaml#
17 The panel may use an OF graph binding for the association to the display,
18 or it may be a direct child node of the display.
104 # DLC Display Co. DLC1010GIG 10.1" WXGA TFT LCD Panel
106 # Emerging Display Technology Corp. 3.5" QVGA TFT LCD panel
108 # Emerging Display Technology Corp. 480x272 TFT Display with capacitive touch
110 # Emerging Display Technology Corp. 480x272 TFT Display
112 # Emerging Display Technology Corp. 5.7" VGA TFT LCD panel
114 # Emerging Display Technology Corp. WVGA TFT Display with capacitive touch
116 # Emerging Display Technology Corp. WVGA TFT Display with capacitive touch
[all …]
Ddisplay-timings.yaml4 $id: http://devicetree.org/schemas/display/panel/display-timings.yaml#
7 title: display timings bindings
15 A display panel may be able to handle several display timings,
17 The display-timings node makes it possible to specify the timings
18 and to specify the timing that is native for the display.
22 const: display-timings
27 The default display timing is the one specified as native-mode.
47 display-timings {
Dpanel-common.yaml4 $id: http://devicetree.org/schemas/display/panel/panel-common.yaml#
7 title: Common Properties for Display Panels
15 display panels. It doesn't constitue a device tree binding specification by
50 Display rotation in degrees counter clockwise (0,90,180,270)
54 # Display Timings
57 Most display panels are restricted to a single resolution and
58 require specific display timings. The panel-timing subnode expresses those
62 display-timings:
64 Some display panels support several resolutions with different timings.
65 The display-timings bindings supports specifying several timings and
[all …]
/kernel/linux/linux-5.10/include/video/
Ds1d13xxxfb.h44 #define S1DREG_LCD_DISP_HWIDTH 0x0032 /* LCD Horizontal Display Width Register: ((val)+1)*8)=pix/l…
45 #define S1DREG_LCD_NDISP_HPER 0x0034 /* LCD Horizontal Non-Display Period Register: ((val)+1)*8)=N…
48 #define S1DREG_LCD_DISP_VHEIGHT0 0x0038 /* LCD Vertical Display Height Register 0 */
49 #define S1DREG_LCD_DISP_VHEIGHT1 0x0039 /* LCD Vertical Display Height Register 1 */
50 #define S1DREG_LCD_NDISP_VPER 0x003A /* LCD Vertical Non-Display Period Register: (val)+1=NDlines …
53 #define S1DREG_LCD_DISP_MODE 0x0040 /* LCD Display Mode Register */
55 #define S1DREG_LCD_DISP_START0 0x0042 /* LCD Display Start Address Register 0 */
56 #define S1DREG_LCD_DISP_START1 0x0043 /* LCD Display Start Address Register 1 */
57 #define S1DREG_LCD_DISP_START2 0x0044 /* LCD Display Start Address Register 2 */
61 #define S1DREG_LCD_DISP_FIFO_HTC 0x004A /* LCD Display FIFO High Threshold Control Register */
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/imx/
Dldb.txt1 Device-Tree bindings for LVDS Display Bridge (ldb)
3 LVDS Display Bridge
6 The LVDS Display Bridge device tree node contains up to two lvds-channel
14 multiplexer in the front to select any of the four IPU display
20 the display interface selector clocks, as described in
48 or a display-timings node that describes the video timings for the connected
49 LVDS display as well as the fsl,data-mapping and fsl,data-width properties.
62 display-timings are used instead.
64 Optional properties (required if display-timings are used):
66 - display-timings : A node that describes the display timings as defined in
[all …]
Dfsl-imx-drm.txt5 IPU or other display interface nodes that comprise the graphics subsystem.
8 - compatible: Should be "fsl,imx-display-subsystem"
9 - ports: Should contain a list of phandles pointing to display interface ports
14 display-subsystem {
15 compatible = "fsl,display-subsystem";
113 Parallel display support
117 - compatible: Should be "fsl,imx-parallel-display"
119 - interface-pix-fmt: How this display is connected to the
120 display interface. Currently supported types: "rgb24", "rgb565", "bgr666"
122 - edid: verbatim EDID data block describing attached display.
[all …]
Dfsl,imx-fb.txt11 - display: Phandle to a display node as described in
12 Documentation/devicetree/bindings/display/panel/display-timing.txt
13 Additional, the display node has to define properties:
16 A display node may optionally define
34 display = <&display0>;
43 display-timings {
/kernel/linux/linux-5.10/drivers/gpu/drm/sun4i/
Dsun4i_drv.c49 .desc = "Allwinner sun4i Display Engine",
156 return of_device_is_compatible(node, "allwinner,sun4i-a10-display-frontend") || in sun4i_drv_node_is_frontend()
157 of_device_is_compatible(node, "allwinner,sun5i-a13-display-frontend") || in sun4i_drv_node_is_frontend()
158 of_device_is_compatible(node, "allwinner,sun6i-a31-display-frontend") || in sun4i_drv_node_is_frontend()
159 of_device_is_compatible(node, "allwinner,sun7i-a20-display-frontend") || in sun4i_drv_node_is_frontend()
160 of_device_is_compatible(node, "allwinner,sun8i-a23-display-frontend") || in sun4i_drv_node_is_frontend()
161 of_device_is_compatible(node, "allwinner,sun8i-a33-display-frontend") || in sun4i_drv_node_is_frontend()
162 of_device_is_compatible(node, "allwinner,sun9i-a80-display-frontend"); in sun4i_drv_node_is_frontend()
223 * Also, in a dual display pipeline setup, both frontends can feed
417 { .compatible = "allwinner,sun4i-a10-display-engine" },
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/auxdisplay/
Dhit,hd44780.yaml14 LCDs that can display one or more lines of text. It exposes an M6800 bus
51 display-height-chars:
52 description: Height of the display, in character cells,
57 display-width-chars:
58 description: Width of the display, in character cells.
66 display-width-chars for displays with more than 2 lines).
76 - display-height-chars
77 - display-width-chars
94 display-height-chars = <2>;
95 display-width-chars = <16>;
/kernel/linux/linux-5.10/Documentation/arm/omap/
Ddss.rst2 OMAP2/3 Display Subsystem
7 TV-out and multiple display support, but there are lots of small improvements
47 flexible way to enable non-common multi-display configuration. In addition to
49 managers. These can be used when updating a display with CPU or system DMA.
53 There exist several display technologies and standards that support audio as
65 certain configurations audio is not supported (e.g., an HDMI display using a
67 the current configuration of the display supports audio.
70 parameters of the display. In order to make the function independent of any
108 dynamic display architecture.
135 the overlay is smaller than the display.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/rockchip/
Drockchip-drm.yaml4 $id: http://devicetree.org/schemas/display/rockchip/rockchip-drm.yaml#
15 vop devices or other display interface nodes that comprise the
20 const: rockchip,display-subsystem
25 Should contain a list of phandles pointing to display interface port
27 Documentation/devicetree/bindings/display/rockchip/rockchip-vop.yaml
37 display-subsystem {
38 compatible = "rockchip,display-subsystem";

12345678910>>...107