Lines Matching +full:write +full:- +full:back

1 /* SPDX-License-Identifier: GPL-2.0+ */
22 * struct video_osd_ops - driver operations for OSD uclass
24 * The OSD uclass implements support for text-oriented on-screen displays,
26 * text-based overlay over the video output of an associated display.
29 * either a generic form (by specifying a string, a driver-specific color value
31 * driver-specific form (by specifying "raw" driver-specific data to display at
43 * get_info() - Get information about a OSD instance
51 * @return 0 if OK, -ve on error.
56 * set_mem() - Write driver-specific text data to OSD screen
58 * The passed data are device-specific, and it's up to the driver how
60 * driver-specific; most likely the given data will be written to the
61 * OSD count times back-to-back, which is e.g. convenient for filling
68 * will write the device-specific text data "A" to the positions (0, 0)
71 * Device-specific text data may, e.g. be a special encoding of glyphs
74 * @dev: OSD instance to write to.
75 * @col: Horizontal character coordinate to write to.
76 * @row Vertical character coordinate to write to.
77 * @buf: Array containing device-specific data to write to the
80 * @count: Write count many repetitions of the given text data
81 * @return 0 if OK, -ve on error.
87 * set_size() - Set the position and dimension of the OSD's
90 * @dev: OSD instance to write to.
93 * @return 0 if OK, -ve on error.
98 * print() - Print a string in a given color to specified coordinates
101 * @dev: OSD instance to write to.
102 * @col The x-coordinate of the position the string should be
104 * @row The y-coordinate of the position the string should be
108 * driver-specific, and possible values should be defined
111 * @return 0 if OK, -ve on error.
117 #define video_osd_get_ops(dev) ((struct video_osd_ops *)(dev)->driver->ops)
120 * video_osd_get_info() - Get information about a OSD instance
128 * @return 0 if OK, -ve on error.
133 * video_osd_set_mem() - Write text data to OSD memory
135 * The passed data are device-specific, and it's up to the driver how to
137 * driver-specific; most likely the given data will be written to the OSD count
138 * times back-to-back, which is e.g. convenient for filling areas of the OSD
145 * will write the device-specific text data "A" to the positions (0, 0) to (9,
148 * Device-specific text data may, e.g. be a special encoding of glyphs to
151 * @dev: OSD instance to write to.
152 * @col: Horizontal character coordinate to write to.
153 * @row Vertical character coordinate to write to.
154 * @buf: Array containing device-specific data to write to the specified
157 * @count: Write count many repetitions of the given text data
158 * @return 0 if OK, -ve on error.
164 * video_osd_set_size() - Set the position and dimension of the OSD's
167 * @dev: OSD instance to write to.
170 * @return 0 if OK, -ve on error.
175 * video_osd_print() - Print a string in a given color to specified coordinates
178 * @dev: OSD instance to write to.
179 * @col The x-coordinate of the position the string should be written
181 * @row The y-coordinate of the position the string should be written
184 * interpretation of the value is driver-specific, and possible
187 * @return 0 if OK, -ve on error.