Home
last modified time | relevance | path

Searched refs:corner (Results 1 – 25 of 42) sorted by relevance

12

/Linux-v5.4/drivers/soc/qcom/
Drpmhpd.c44 unsigned int corner; member
138 unsigned int corner, bool sync) in rpmhpd_send_corner() argument
142 .data = corner, in rpmhpd_send_corner()
155 static void to_active_sleep(struct rpmhpd *pd, unsigned int corner, in to_active_sleep() argument
158 *active = corner; in to_active_sleep()
175 static int rpmhpd_aggregate_corner(struct rpmhpd *pd, unsigned int corner) in rpmhpd_aggregate_corner() argument
183 to_active_sleep(pd, corner, &this_active_corner, &this_sleep_corner); in rpmhpd_aggregate_corner()
186 to_active_sleep(peer, peer->corner, &peer_active_corner, in rpmhpd_aggregate_corner()
222 if (pd->corner) in rpmhpd_power_on()
223 ret = rpmhpd_aggregate_corner(pd, pd->corner); in rpmhpd_power_on()
[all …]
Drpmpd.c100 unsigned int corner; member
219 static int rpmpd_send_corner(struct rpmpd *pd, int state, unsigned int corner) in rpmpd_send_corner() argument
224 .value = cpu_to_le32(corner), in rpmpd_send_corner()
231 static void to_active_sleep(struct rpmpd *pd, unsigned int corner, in to_active_sleep() argument
234 *active = corner; in to_active_sleep()
250 to_active_sleep(pd, pd->corner, &this_active_corner, &this_sleep_corner); in rpmpd_aggregate_corner()
253 to_active_sleep(peer, peer->corner, &peer_active_corner, in rpmpd_aggregate_corner()
280 if (pd->corner) in rpmpd_power_on()
316 pd->corner = state; in rpmpd_set_performance()
/Linux-v5.4/Documentation/devicetree/bindings/opp/
Dqcom-opp.txt16 - qcom,opp-fuse-level: A positive value representing the fuse corner/level
18 a certain fuse corner/level. A fuse corner/level contains e.g. ref uV,
/Linux-v5.4/Documentation/media/uapi/v4l/
Dselection-api-configuration.rst37 The range of coordinates of the top left corner, width and height of
40 corner at position ``(0,0)``. The rectangle's coordinates are expressed
43 The top left corner, width and height of the source rectangle, that is
58 coordinates are expressed in pixels. The rectangle's top/left corner
98 All coordinates are expressed in pixels. The top/left corner is always
102 The top left corner, width and height of the source rectangle, that is
124 the driver developers to put the top/left corner at position ``(0,0)``.
Dvidioc-cropcap.rst117 - Horizontal offset of the top, left corner of the rectangle, in
121 - Vertical offset of the top, left corner of the rectangle, in
Ddev-overlay.rst165 Size and position of the window relative to the top, left corner of
197 relative to the top, left corner of the frame buffer. However
263 corner of the frame buffer. Only window pixels *outside* all
278 Horizontal offset of the top, left corner of the rectangle, in
282 Vertical offset of the top, left corner of the rectangle, in pixels.
Dcrop.rst81 For capture devices the coordinates of the top left corner, width and
93 The top left corner, width and height of the source rectangle, that is
Dvidioc-g-fbuf.rst111 the pixel in the top left corner of the framebuffer. [#f1]_
297 relative to the top-left corner of the framebuffer and restricted
/Linux-v5.4/drivers/input/mouse/
Dalps.c398 struct input_mt_pos corner[4]; in alps_process_bitmap() local
430 corner[0].x = in alps_process_bitmap()
433 corner[0].y = in alps_process_bitmap()
438 corner[1].x = in alps_process_bitmap()
441 corner[1].y = in alps_process_bitmap()
446 corner[2].x = in alps_process_bitmap()
449 corner[2].y = in alps_process_bitmap()
454 corner[3].x = in alps_process_bitmap()
457 corner[3].y = in alps_process_bitmap()
464 corner[i].x = priv->x_max - corner[i].x; in alps_process_bitmap()
[all …]
/Linux-v5.4/Documentation/input/devices/
Delantech.rst192 C: 1 = enable corner tap
247 c = 1 when corner tap detected
255 byte 1 = 0xf0 when corner tap detected
275 when corner tap detected:
276 ds0 = 1 when top right corner tapped
277 ds1 = 1 when bottom right corner tapped
278 ds2 = 1 when bottom left corner tapped
279 ds3 = 1 when top left corner tapped
/Linux-v5.4/Documentation/networking/
Dipsec.txt2 Here documents known IPsec corner cases which need to be keep in mind when
Dradiotap-headers.txt12 This document gives an overview and warns on some corner cases.
/Linux-v5.4/Documentation/devicetree/bindings/sound/
Dcs42l56.txt45 …- cirrus,hpf-left-freq, hpf-right-freq : Sets the corner frequency (-3dB point) for the internal H…
/Linux-v5.4/tools/testing/selftests/futex/
DREADME8 odd corner cases, regression tests, and abject abuse and misuse.
/Linux-v5.4/Documentation/vm/
Dovercommit-accounting.rst48 not matter much but it's a corner case if you really really care
/Linux-v5.4/Documentation/ioctl/
Dbotching-up-ioctls.rst89 error handling paths - GPUs will die eventually in the oddmost corner cases
122 * Have testcases for the really tricky corner cases in your error recovery code
163 * Have testcases for corner-cases, especially whether the return values for
/Linux-v5.4/Documentation/devicetree/bindings/usb/
Dmsm-hsusb.txt74 in microvolts or a value corresponding to voltage corner.
/Linux-v5.4/Documentation/gpu/
Dintroduction.rst49 names are "Notes" with information for dangerous or tricky corner cases,
Ddrm-uapi.rst53 them for every possible corner case. This in turn makes it really practically
81 thing. Specifically it needs to handle all the usual error and corner cases.
/Linux-v5.4/Documentation/
Dxz.txt106 There are a couple of corner cases where things have been simplified
Dlzo.txt196 mistakes or that a few corner cases were overlooked. In any case, please
/Linux-v5.4/Documentation/driver-api/pci/
Dp2pdma.rst26 a few corner case gotchas with these pages so developers need to
/Linux-v5.4/Documentation/scheduler/
Dsched-bwc.rst109 The fact that cpu-local slices do not expire results in some interesting corner
/Linux-v5.4/Documentation/ia64/
Daliasing.rst146 There may be corner cases of things that are not in kern_memmap,
/Linux-v5.4/Documentation/x86/
Dpti.rst143 several minutes. These tests frequently uncover corner cases in the

12