/Linux-v4.19/drivers/video/fbdev/omap2/omapfb/ |
D | omapfb-ioctl.c | 217 struct omap_dss_device *display = fb2display(fbi); in omapfb_setup_mem() local 227 if (display && display->driver->sync) in omapfb_setup_mem() 228 display->driver->sync(display); in omapfb_setup_mem() 292 struct omap_dss_device *display = fb2display(fbi); in omapfb_update_window() local 295 if (!display) in omapfb_update_window() 301 display->driver->get_resolution(display, &dw, &dh); in omapfb_update_window() 306 return display->driver->update(display, x, y, w, h); in omapfb_update_window() 312 struct omap_dss_device *display = fb2display(fbi); in omapfb_set_update_mode() local 318 if (!display) in omapfb_set_update_mode() 326 d = get_display_data(fbdev, display); in omapfb_set_update_mode() [all …]
|
D | omapfb-main.c | 668 struct omap_dss_device *display = fb2display(fbi); in check_fb_var() local 709 if (display && display->driver->get_dimensions) { in check_fb_var() 711 display->driver->get_dimensions(display, &w, &h); in check_fb_var() 721 if (display && display->driver->get_timings) { in check_fb_var() 723 display->driver->get_timings(display, &timings); in check_fb_var() 1232 struct omap_dss_device *display = fb2display(fbi); in omapfb_blank() local 1236 if (!display) in omapfb_blank() 1241 d = get_display_data(fbdev, display); in omapfb_blank() 1245 if (display->state == OMAP_DSS_DISPLAY_ACTIVE) in omapfb_blank() 1248 r = display->driver->enable(display); in omapfb_blank() [all …]
|
/Linux-v4.19/drivers/acpi/acpica/ |
D | utbuffer.c | 34 void acpi_ut_dump_buffer(u8 *buffer, u32 count, u32 display, u32 base_offset) in acpi_ut_dump_buffer() argument 47 display = DB_BYTE_DISPLAY; in acpi_ut_dump_buffer() 65 acpi_os_printf("%*s", ((display * 2) + 1), " "); in acpi_ut_dump_buffer() 66 j += display; in acpi_ut_dump_buffer() 70 switch (display) { in acpi_ut_dump_buffer() 105 j += display; in acpi_ut_dump_buffer() 164 acpi_ut_debug_dump_buffer(u8 *buffer, u32 count, u32 display, u32 component_id) in acpi_ut_debug_dump_buffer() argument 174 acpi_ut_dump_buffer(buffer, count, display, 0); in acpi_ut_debug_dump_buffer() 200 u8 *buffer, u32 count, u32 display, u32 base_offset) in acpi_ut_dump_buffer_to_file() argument 213 display = DB_BYTE_DISPLAY; in acpi_ut_dump_buffer_to_file() [all …]
|
/Linux-v4.19/drivers/staging/fbtft/ |
D | fbtft_device.c | 278 .display = { 298 .display = { 321 .display = { 340 .display = { 360 .display = { 380 .display = { 397 .display = { 419 .display = { 436 .display = { 454 .display = { [all …]
|
D | fbtft-core.c | 650 struct fb_info *fbtft_framebuffer_alloc(struct fbtft_display *display, in fbtft_framebuffer_alloc() argument 663 int txbuflen = display->txbuflen; in fbtft_framebuffer_alloc() 664 unsigned int bpp = display->bpp; in fbtft_framebuffer_alloc() 665 unsigned int fps = display->fps; in fbtft_framebuffer_alloc() 667 const s16 *init_sequence = display->init_sequence; in fbtft_framebuffer_alloc() 668 char *gamma = display->gamma; in fbtft_framebuffer_alloc() 672 if (display->gamma_num * display->gamma_len > in fbtft_framebuffer_alloc() 695 if (pdata->display.init_sequence) in fbtft_framebuffer_alloc() 696 init_sequence = pdata->display.init_sequence; in fbtft_framebuffer_alloc() 699 if (pdata->display.debug) in fbtft_framebuffer_alloc() [all …]
|
/Linux-v4.19/Documentation/devicetree/bindings/display/ |
D | cirrus,clps711x-fb.txt | 8 - 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 { 34 display-timings {
|
D | simple-framebuffer.txt | 4 the bootloader, with the assumption that the display hardware has already 10 If the devicetree contains nodes for the display hardware used by a simplefb, 11 then the simplefb node must contain a property called "display", which 12 contains a phandle pointing to the primary display hw node, so that the OS 17 It is advised to add display# aliases to help the OS determine how to number 18 things. If display# aliases are used, then if the simplefb node contains a 19 "display" property then the /aliases/display# path must point to the display 20 hw node the "display" property points to, otherwise it must point directly 25 primary display hw node, as with display# aliases. If display aliases are 30 enable them. This way if e.g. later on support for more display clocks get [all …]
|
D | mxsfb.txt | 22 lcdif1: display-controller@2220000 { 45 - display: phandle to display node (see below for details) 47 * display node 54 - display-timings: Refer to binding doc display-timing.txt for details. 63 display: display { 67 display-timings {
|
D | repaper.txt | 4 - compatible: "pervasive,e1144cs021" for 1.44" display 5 "pervasive,e1190cs021" for 1.9" display 6 "pervasive,e2200cs021" for 2.0" display 7 "pervasive,e2271cs021" for 2.7" display 32 display { 51 pervasive,thermal-zone = "display";
|
D | atmel,lcdc.txt | 17 - display: a phandle pointing to the display node 20 - display: a display node is required to initialize the lcd panel 22 - default-mode: a videomode within the display with timing parameters 36 display = <&display0>; 66 display0: display { 74 display-timings {
|
/Linux-v4.19/drivers/gpu/drm/nouveau/nvkm/engine/gr/ |
D | nv50.c | 282 nv50_gr_mp_trap(struct nv50_gr *gr, int tpid, int display) in nv50_gr_mp_trap() argument 302 if (display) { in nv50_gr_mp_trap() 319 if (!mps && display) in nv50_gr_mp_trap() 326 u32 ustatus_new, int display, const char *name) in nv50_gr_tp_trap() argument 348 if (display) { in nv50_gr_tp_trap() 365 nv50_gr_mp_trap(gr, i, display); in nv50_gr_tp_trap() 368 if (ustatus && display) { in nv50_gr_tp_trap() 377 if (display) in nv50_gr_tp_trap() 384 if (display) in nv50_gr_tp_trap() 390 if (!tps && display) in nv50_gr_tp_trap() [all …]
|
/Linux-v4.19/Documentation/devicetree/bindings/display/rockchip/ |
D | rockchip-drm.txt | 5 vop devices or other display interface nodes that comprise the 9 - compatible: Should be "rockchip,display-subsystem" 10 - ports: Should contain a list of phandles pointing to display interface port 12 Documentation/devicetree/bindings/display/rockchip/rockchip-vop.txt 16 display-subsystem { 17 compatible = "rockchip,display-subsystem";
|
/Linux-v4.19/Documentation/devicetree/bindings/display/panel/ |
D | ilitek,ili9322.txt | 23 - pixelclk-active: see display/panel/display-timing.txt 24 - de-active: see display/panel/display-timing.txt 25 - hsync-active: see display/panel/display-timing.txt 26 - vsync-active: see display/panel/display-timing.txt 37 panel: display@0 {
|
D | display-timing.txt | 1 display-timing bindings 4 display-timings node 11 - native-mode: The native mode for the display, in case multiple modes are 18 - hactive, vactive: display resolution 19 - hfront-porch, hback-porch, hsync-len: horizontal display timing parameters 21 vfront-porch, vback-porch, vsync-len: vertical display timing parameters in 23 - clock-frequency: display clock in Hz 52 There are different ways of describing the capabilities of a display. The 54 for displays. If a display supports multiple signal timings, the native-mode 83 Note: In addition to being used as subnode(s) of display-timings, the timing [all …]
|
/Linux-v4.19/Documentation/devicetree/bindings/display/imx/ |
D | fsl,imx-fb.txt | 11 - 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>; 44 display-timings {
|
D | fsl-imx-drm.txt | 5 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 …]
|
D | ldb.txt | 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 67 Documentation/devicetree/bindings/display/panel/display-timing.txt. 117 /* Using display-timings and fsl,data-mapping/width instead */ 125 display-timings {
|
/Linux-v4.19/arch/mips/mti-malta/ |
D | malta-display.c | 25 static unsigned int __iomem *display = NULL; in mips_display_message() local 28 if (unlikely(display == NULL)) in mips_display_message() 29 display = ioremap(ASCII_DISPLAY_POS_BASE, 16*sizeof(int)); in mips_display_message() 33 __raw_writel(*str++, display + i); in mips_display_message() 35 __raw_writel(' ', display + i); in mips_display_message()
|
/Linux-v4.19/Documentation/ABI/testing/ |
D | sysfs-platform-asus-laptop | 1 What: /sys/devices/platform/asus_laptop/display 6 This file allows display switching. The value 13 Ex: - 0 (0000b) means no display 29 Some models like the W1N have a LED display that can be 30 used to display several items of information. 31 To control the LED display, use the following : 33 where T control the 3 letters display, and DDD the 3 digits display.
|
/Linux-v4.19/drivers/video/fbdev/ |
D | nuc900fb.c | 95 struct nuc900fb_display *display = NULL; in nuc900fb_check_var() local 107 display = default_display; in nuc900fb_check_var() 113 display = mach_info->displays + i; in nuc900fb_check_var() 117 if (display == NULL) { in nuc900fb_check_var() 124 var->xres_virtual = display->xres; in nuc900fb_check_var() 125 var->yres_virtual = display->yres; in nuc900fb_check_var() 126 var->height = display->height; in nuc900fb_check_var() 127 var->width = display->width; in nuc900fb_check_var() 130 var->pixclock = display->pixclock; in nuc900fb_check_var() 131 var->left_margin = display->left_margin; in nuc900fb_check_var() [all …]
|
/Linux-v4.19/Documentation/devicetree/bindings/auxdisplay/ |
D | hit,hd44780.txt | 4 that can display one or more lines of text. It exposes an M6800 bus interface, 18 - display-height-chars: Height of the display, in character cells, 19 - display-width-chars: Width of the display, in character cells. 28 with 1 or 2 lines, and display-width-chars for displays with more than 2 43 display-height-chars = <2>; 44 display-width-chars = <16>;
|
/Linux-v4.19/Documentation/devicetree/bindings/display/sunxi/ |
D | sun4i-drm.txt | 7 For all connections between components up to the TCONs in the display 74 Documentation/devicetree/bindings/display/bridge/dw_hdmi.txt with the 196 TCON TOPs main purpose is to configure whole display pipeline. It determines 201 It allows display pipeline to be configured in very different ways: 280 The display engine backend exposes layers and sprites to the 285 * allwinner,sun4i-a10-display-backend 286 * allwinner,sun5i-a13-display-backend 287 * allwinner,sun6i-a31-display-backend 288 * allwinner,sun7i-a20-display-backend 289 * allwinner,sun8i-a33-display-backend [all …]
|
/Linux-v4.19/drivers/video/fbdev/mmp/hw/ |
D | Kconfig | 4 bool "mmp display controller hw support" 8 Marvell MMP display hw controller support 13 bool "mmp display controller spi port" 17 Marvell MMP display hw controller spi port support
|
/Linux-v4.19/drivers/thermal/int340x_thermal/ |
D | Kconfig | 33 tristate "ACPI INT3406 display thermal driver" 36 The display thermal device represents the LED/LCD display panel 38 the display thermal device is to allow control of the display 40 power consumed by display device.
|
/Linux-v4.19/Documentation/gpu/ |
D | xen-front.rst | 5 This frontend driver implements Xen para-virtualized display 6 according to the display protocol described at 9 Driver modes of operation in terms of display buffers used 13 :doc: Driver modes of operation in terms of display buffers used
|