Home
last modified time | relevance | path

Searched full:screen (Results 1 – 25 of 582) sorted by relevance

12345678910>>...24

/linux/drivers/gpu/drm/
H A Ddrm_privacy_screen.c25 * register a privacy-screen device, which the KMS drivers can then use
26 * to implement the standard privacy-screen properties, see
29 * KMS drivers using a privacy-screen class device are advised to use the
46 * drm_privacy_screen_lookup_add - add an entry to the static privacy-screen
50 * Add an entry to the static privacy-screen lookup list. Note the
52 * gets added to a list owned by the privacy-screen core. So the passed in
66 * privacy-screen lookup list
70 * from the static privacy-screen lookup list.
103 * drm_privacy_screen_get - get a privacy-screen provider
104 * @dev: consumer-device for which to get a privacy-screen provider
[all …]
H A DKconfig70 hex "Drm panic screen foreground color, in RGB"
75 hex "Drm panic screen background color, in RGB"
89 string "Panic screen formatter"
102 bool "Add a panic screen with a QR code"
106 This option adds a QR code generator, and a panic screen with a QR
110 To use this panic screen, also set DRM_PANIC_SCREEN to "qr_code"
113 string "Base URL of the QR code in the panic screen"
/linux/include/drm/
H A Ddrm_privacy_screen_driver.h22 * Defines the operations which the privacy-screen class code may call.
23 * These functions should be implemented by the privacy-screen driver.
27 * @set_sw_state: Called to request a change of the privacy-screen
28 * state. The privacy-screen class code contains a check to avoid this
37 * privacy-screen state from the hardware and then updates sw_state and
39 * the privacy-screen is registered in sysfs.
45 * struct drm_privacy_screen - central privacy-screen structure
47 * Central privacy-screen structure, this contains the struct device used
48 * to register the screen in sysfs, the screen's state, ops, etc.
51 /** @dev: device used to register the privacy-screen in sysfs. */
[all …]
H A Ddrm_privacy_screen_machine.h15 * struct drm_privacy_screen_lookup - static privacy-screen lookup list entry
17 * Used for the static lookup-list for mapping privacy-screen consumer
18 * dev-connector pairs to a privacy-screen provider.
/linux/drivers/platform/chrome/
H A Dchromeos_privacy_screen.c4 * ChromeOS Privacy Screen support
8 * This is the Chromeos privacy screen provider, present on certain chromebooks,
11 * the privacy-screen.
19 * the firmware team, on how to control privacy screen using ACPI methods.
22 #define PRIV_SCRN_DSM_FN_GET_STATUS 1 /* Get privacy screen status */
23 #define PRIV_SCRN_DSM_FN_ENABLE 2 /* Enable privacy screen */
24 #define PRIV_SCRN_DSM_FN_DISABLE 3 /* Disable privacy screen */
45 "_DSM failed to get privacy-screen state\n"); in chromeos_privacy_screen_get_hw_state()
51 "Bad _DSM to get privacy-screen state\n"); in chromeos_privacy_screen_get_hw_state()
86 "Bad attempt to set privacy-screen status to %u\n", in chromeos_privacy_screen_set_sw_state()
[all …]
/linux/drivers/accessibility/speakup/
H A DDefaultKeyAssignments12 InsKeyPad-8 say from top of screen to reading cursor.
25 KeyPad-plus Say Entire Screen
26 InsKeyPad-plus Say from reading cursor line to bottom of screen.
31 InsKeyPad-9 Move reading cursor to top of screen (insert pgup)
32 InsKeyPad-3 Move reading cursor to bottom of screen (insert pgdn)
33 InsKeyPad-7 Move reading cursor to left edge of screen (insert home)
34 InsKeyPad-1 Move reading cursor to right edge of screen (insert end)
39 allowed value for the row or column for your current screen.
40 KeyPad-/ Mark and Cut screen region.
41 InsKeyPad-/ Paste screen region into any console.
/linux/tools/kvm/kvm_stat/
H A Dkvm_stat1062 self.screen = None
1071 self.screen = curses.initscr()
1096 if self.screen:
1097 self.screen.keypad(0)
1123 self.screen.addstr(row, 2, '%8s %-60s' %
1130 self.screen.addstr(row, 2, '%8s %-60s' % (line[0], line[1]))
1132 if row >= self.screen.getmaxyx()[0]:
1135 self.screen.addstr(row + 1, 2, 'Not available')
1186 self.screen.addstr(4, 1, 'Updating pid filter...')
1187 self.screen.refresh()
[all …]
/linux/drivers/gpu/drm/imagination/
H A Dpvr_rogue_cr_defs_client.h102 * In order to perform the tiling operation and generate the display list the maximum screen size
110 * Maximum Y tile address visible on screen, 32 pixel tile height, 16Kx16K max screen size
115 * Maximum X tile address visible on screen, 32 pixel tile width, 16Kx16K max screen size
121 * In order to perform the tiling operation and generate the display list the maximum screen size
129 * Screen height in pixels. (16K x 16K max screen size)
134 * Screen width in pixels.(16K x 16K max screen size)
/linux/Documentation/fb/
H A Dapi.rst24 Device and driver capabilities are reported in the fixed screen information
51 additional information, which are stored in the variable screen information
65 screen information line_length field.
83 belonging to different planes, is stored in the fixed screen information
89 stored in the variable screen information grayscale field.
94 specified by the variable screen information bpp field.
105 specified by the variable screen information bpp field.
119 Each component is stored in a macropixel according to the variable screen
129 screen information bits_per_pixel field.
136 Each component is stored in a macropixel according to the variable screen
[all …]
H A Dframebuffer.rst45 read and write their contents. You can, for example, make a screen snapshot by::
83 organization of the screen memory (planes, packed pixels, ...) and address
84 and length of the screen memory.
103 application programs is the screen organization (bitplanes or chunky pixels
158 A monitor draws an image on the screen by using an electron beam (3 electron
160 the screen is covered by a pattern of colored phosphors (pixels). If a phosphor
164 from the top to the bottom of the screen. By modifying the intensity of the
168 screen and to the next line: this is called the horizontal retrace. After the
169 whole screen (frame) was painted, the beam moves back to the upper left corner:
179 If the screen resolution is 640x480, it will take::
[all …]
/linux/Documentation/devicetree/bindings/iio/
H A Dmount-matrix.txt25 For example a device with some kind of screen, where the user is supposed to
27 mounted on the same chassis as this screen, will likely take the screen as
29 screen and (z) being depth, the axis perpendicular to the screen.
31 For a screen you probably want (x) coordinates to go from negative on the left
33 and (z) depth to be negative under the screen and positive in front of it,
55 9.81 m/s^2 upwards along the (z) axis, i.e. out of the screen when the device
56 is held with its screen flat on the planets surface and 0 on the other axes,
132 device with a screen lying flat on a table), you should get a negative value
/linux/drivers/gpu/drm/vmwgfx/
H A Dvmwgfx_stdu.c74 * @buf: buffer object when DMA-ing between buffer and screen targets.
75 * @sid: Surface ID when copying between surface and screen targets.
141 * Screen Target Display Unit CRTC Functions
155 * vmw_stdu_define_st - Defines a Screen Target
158 * @stdu: display unit to create a Screen Target for
160 * @crtc_x: X coordinate of screen target relative to framebuffer origin.
161 * @crtc_y: Y coordinate of screen target relative to framebuffer origin.
209 * vmw_stdu_bind_st - Binds a surface to a Screen Target
213 * @res: Buffer to bind to the screen target. Set to NULL to blank screen.
215 * Binding a surface to a Screen Target the same as flipping
[all …]
H A Dvmwgfx_scrn.c48 * blit surface to screen command.
90 * Display unit using screen objects.
108 * Screen Object Display Unit CRTC functions
117 * Send the fifo command to create a screen.
165 * Send the fifo command to destroy a screen.
206 * vmw_sou_crtc_mode_set_nofb - Create new screen
208 * @crtc: CRTC associated with the new screen
210 * This function creates/destroys a screen. This function cannot fail, so if
234 DRM_ERROR("Failed to destroy Screen Object\n"); in vmw_sou_crtc_mode_set_nofb()
254 DRM_ERROR("Failed to define Screen Object %dx%d\n", in vmw_sou_crtc_mode_set_nofb()
[all …]
/linux/drivers/gpu/drm/vboxvideo/
H A Dvbva_base.c108 struct gen_pool *ctx, s32 screen, bool enable) in vbva_inform_host() argument
120 if (screen >= 0) { in vbva_inform_host()
122 p->screen_id = screen; in vbva_inform_host()
138 struct vbva_buffer *vbva, s32 screen) in vbva_enable() argument
147 ret = vbva_inform_host(vbva_ctx, ctx, screen, true); in vbva_enable()
149 vbva_disable(vbva_ctx, ctx, screen); in vbva_enable()
155 s32 screen) in vbva_disable() argument
161 vbva_inform_host(vbva_ctx, ctx, screen, false); in vbva_disable()
H A Dmodesetting.c17 * @display: The screen number.
19 * @origin_y: The vertical displacement relative to the first screen.
59 * resize event for any screen, at which time it is
64 * @origin_x: Upper left X co-ordinate relative to the first screen.
65 * @origin_y: Upper left Y co-ordinate relative to the first screen.
/linux/drivers/s390/char/
H A Dcon3270.c76 * 1) describe line orientation & lines list concept against screen
77 * 2) describe conversion of screen to lines
95 /* Current tty screen. */
100 struct tty3270_line *screen; member
133 #define TTY_UPDATE_LINES 0x4 /* Update visible screen lines */
134 #define TTY_UPDATE_ALL 0x7 /* Recreate screen. */
194 return tp->screen + tty3270_line_increment(tp, tp->line_write_start, num); in tty3270_get_write_line()
199 return tp->screen + tty3270_line_increment(tp, tp->line_view_start, num - tp->nr_up); in tty3270_get_view_line()
215 * The input line are the two last lines of the screen.
250 * The status line is the last line of the screen. It shows the string
[all …]
/linux/tools/perf/ui/gtk/
H A Dbrowser.c19 GdkScreen *screen; in perf_gtk__resize_window() local
24 screen = gtk_widget_get_screen(window); in perf_gtk__resize_window()
26 monitor = gdk_screen_get_monitor_at_window(screen, window->window); in perf_gtk__resize_window()
28 gdk_screen_get_monitor_geometry(screen, monitor, &rect); in perf_gtk__resize_window()
/linux/Documentation/devicetree/bindings/leds/
H A Dleds-el15203000.txt12 Screen light tube LED which surrounds vending machine screen and
56 /* screen frame */
59 function = "screen";
/linux/fs/nls/
H A DKconfig285 correctly on the screen, you need to include the appropriate
294 correctly on the screen, you need to include the appropriate
324 correctly on the screen, you need to include the appropriate
336 correctly on the screen, you need to include the appropriate
347 correctly on the screen, you need to include the appropriate
357 correctly on the screen, you need to include the appropriate
367 correctly on the screen, you need to include the appropriate
378 correctly on the screen, you need to include the appropriate
387 correctly on the screen, you need to include the appropriate
396 correctly on the screen, you need to include the appropriate
[all …]
/linux/include/linux/mfd/
H A Dmxs-lradc.h123 * CH2 -- Touch screen XPUL
124 * CH3 -- Touch screen YPLL
125 * CH4 -- Touch screen XNUL
126 * CH5 -- Touch screen YNLR
127 * CH6 -- Touch screen WIPER (5-wire only)
/linux/include/uapi/linux/
H A Dvt.h58 __u16 v_vlin; /* number of pixel rows on screen */
60 __u16 v_vcol; /* number of pixel columns on screen */
71 #define VT_EVENT_BLANK 0x0002 /* Screen blank */
72 #define VT_EVENT_UNBLANK 0x0004 /* Screen unblank */
/linux/drivers/video/fbdev/
H A Dsm501fb.c107 struct sm501_mem screen; member
210 end = par->screen.k_addr ? par->screen.sm_addr : inf->fbmem_len; in sm501_alloc_mem()
226 end = par->screen.sm_addr; in sm501_alloc_mem()
490 if (sm501_alloc_mem(fbi, &par->screen, mem_type, smem_len, smem_len)) { in sm501fb_set_par_common()
496 info->fix.smem_start = fbi->fbmem_res->start + par->screen.sm_addr; in sm501fb_set_par_common()
500 info->screen_base = fbi->fbmem + par->screen.sm_addr; in sm501fb_set_par_common()
503 /* set start of framebuffer to the screen */ in sm501fb_set_par_common()
505 smc501_writel(par->screen.sm_addr | SM501_ADDR_FLIP, in sm501fb_set_par_common()
602 reg = (par->screen.sm_addr + xoffs + in sm501fb_pan_crt()
672 sm501_alloc_mem(fbi, &par->screen, SM501_MEMF_CRT, 0, in sm501fb_set_par_crt()
[all …]
/linux/Documentation/arch/s390/
H A D3270.rst78 3. You should immediately see a Linux login screen.
155 The screen you should now see contains a VM logo with input
201 The driver defines three areas on the 3270 screen: the log area, the
204 The log area takes up all but the bottom two lines of the screen. The
208 screen clears and more output is written, from the top down.
210 The input area extends from the beginning of the second-to-last screen
217 nothing. If you do nothing, the screen will clear in (default) 5 sec
H A D3270.ChangeLog7 screen height to omit the two rows used for input area, in
11 * Oversize 3270 screen widths may exceed GEOM_MAXINPLEN columns,
40 tubttybld.c and tubttyscl.c, for screen-building code and
/linux/Documentation/devicetree/bindings/display/panel/
H A Dolimex,lcd-olinuxino.yaml22 - AR1021 resistive touch screen controller (optional)
23 - FT5x6 capacitive touch screen controller (optional)
24 - GT911/GT928 capacitive touch screen controller (optional)

12345678910>>...24