Home
last modified time | relevance | path

Searched full:microseconds (Results 1 – 25 of 896) sorted by relevance

12345678910>>...36

/kernel/linux/linux-4.19/Documentation/media/uapi/rc/
Dlirc-get-rec-resolution.rst12 LIRC_GET_REC_RESOLUTION - Obtain the value of receive resolution, in microseconds.
17 .. c:function:: int ioctl( int fd, LIRC_GET_REC_RESOLUTION, __u32 *microseconds)
26 ``microseconds``
27 Resolution, in microseconds.
Dlirc-dev-intro.rst92 Signifies the presence of IR in microseconds.
96 Signifies absence of IR in microseconds.
109 this packet will be sent, with the number of microseconds with
119 The values are alternating pulse and space lengths, in microseconds. The
/kernel/linux/linux-5.10/Documentation/userspace-api/media/rc/
Dlirc-get-rec-resolution.rst13 LIRC_GET_REC_RESOLUTION - Obtain the value of receive resolution, in microseconds.
20 ``int ioctl(int fd, LIRC_GET_REC_RESOLUTION, __u32 *microseconds)``
28 ``microseconds``
29 Resolution, in microseconds.
Dlirc-dev-intro.rst106 Signifies the presence of IR in microseconds.
110 Signifies absence of IR in microseconds.
123 this packet will be sent, with the number of microseconds with
133 The values are alternating pulse and space lengths, in microseconds. The
/kernel/liteos_m/kernel/include/
Dlos_tick.h134 * Number of microseconds in one second.
378 * @param UINT64 [IN] delay times, microseconds.
385 extern VOID LOS_UDelay(UINT64 microseconds);
469 * Number of microseconds in one second.
509 * @retval #LOS_OK 0: Cycles are successfully converted to microseconds.
518 * @brief Convert cycles to microseconds.
521 * This API is used to convert cycles to microseconds.
528 * @param usHi [OUT] Upper 32 bits of the number of microseconds.
529 * @param usLo [OUT] Lower 32 bits of the number of microseconds.
532 * @retval #LOS_OK 0: Cycles are successfully converted to microseconds.
[all …]
/kernel/linux/linux-4.19/Documentation/ABI/testing/
Dsysfs-module21 microframe to be 80%, that is 100 microseconds out of 125
22 microseconds (full microframe).
26 microseconds of isochronous bandwidth per microframe to work
31 microseconds of periodic bandwidth per microframe.
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-module22 microframe to be 80%, that is 100 microseconds out of 125
23 microseconds (full microframe).
27 microseconds of isochronous bandwidth per microframe to work
32 microseconds of periodic bandwidth per microframe.
Ddebugfs-hyperv14 microseconds (inclusive).
21 Description: Fuzz testing message delay value between 0 - 1000 microseconds
/kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/
Dpixfmt-meta-d4xx.rst57 - Exposure time (in microseconds) used to capture the frame
91 - Time in microseconds from the beginning of a frame till its middle
93 - Time, used to read out a frame in microseconds
95 - Frame exposure time in microseconds
97 - In microseconds = 1000000 / framerate
99 - Time in microseconds from start of frame to data in USB buffer
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/power/
Ddomain-idle-state.txt17 microseconds required to enter the idle state.
25 in microseconds required to exit the idle state.
31 in microseconds after which the idle state will yield
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dmax77620.txt91 -maxim,shutdown-fps-time-period-us: u32, FPS time period in microseconds
95 -maxim,suspend-fps-time-period-us: u32, FPS time period in microseconds
111 Here supported time periods by device in microseconds are as follows:
112 MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microseconds.
113 MAX20024 supports 20, 40, 80, 160, 320, 640, 1280 and 2540 microseconds.
114 MAX77663 supports 20, 40, 80, 160, 320, 640, 1280 and 2540 microseconds.
/kernel/linux/linux-4.19/arch/arm/mach-omap2/
Dcm.h17 * MAX_MODULE_READY_TIME: max duration in microseconds to wait for the
20 * In the case of OMAP4 this is the max duration in microseconds for the
36 * MAX_MODULE_DISABLE_TIME: max duration in microseconds to wait for
39 * in microseconds for the module to reach the inactive state from
/kernel/linux/linux-5.10/arch/arm/mach-omap2/
Dcm.h14 * MAX_MODULE_READY_TIME: max duration in microseconds to wait for the
17 * In the case of OMAP4 this is the max duration in microseconds for the
33 * MAX_MODULE_DISABLE_TIME: max duration in microseconds to wait for
36 * in microseconds for the module to reach the inactive state from
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/
Dmdio.yaml38 RESET pulse width in microseconds. It applies to all MDIO devices
44 Delay after reset deassert in microseconds. It applies to all MDIO
92 Delay after the reset was asserted in microseconds. If this
97 Delay after the reset was deasserted in microseconds. If
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt34 microseconds).
50 - slew-delay-us: microseconds to wait for a GPIO to go high. Default is 10 us.
51 - wait-retry-us: we'll attempt another claim after this many microseconds.
53 - wait-free-us: we'll give up after this many microseconds. Default is 50000 us.
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt34 microseconds).
50 - slew-delay-us: microseconds to wait for a GPIO to go high. Default is 10 us.
51 - wait-retry-us: we'll attempt another claim after this many microseconds.
53 - wait-free-us: we'll give up after this many microseconds. Default is 50000 us.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Ddomain-idle-state.yaml32 The worst case latency in microseconds required to enter the idle
38 The worst case latency in microseconds required to exit the idle
43 The minimum residency duration in microseconds after which the idle
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/
Dmax77620.txt85 -maxim,shutdown-fps-time-period-us: u32, FPS time period in microseconds
89 -maxim,suspend-fps-time-period-us: u32, FPS time period in microseconds
105 Here supported time periods by device in microseconds are as follows:
106 MAX77620 supports 40, 80, 160, 320, 640, 1280, 2560 and 5120 microseconds.
107 MAX20024 supports 20, 40, 80, 160, 320, 640, 1280 and 2540 microseconds.
/kernel/linux/linux-5.10/drivers/gpu/drm/amd/display/dmub/
Ddmub_srv.h492 * @timeout_us: the maximum number of microseconds to wait
495 * wait time is given in microseconds to prevent spinning forever.
511 * @timeout_us: the maximum number of microseconds to wait
514 * wait time is given in microseconds to prevent spinning forever.
530 * @timeout_us: the maximum number of microseconds to wait
534 * microseconds to prevent spinning forever.
549 * @timeout_us: the maximum number of microseconds to wait
552 * Waits for the number of microseconds specified by timeout_us
/kernel/linux/linux-4.19/include/linux/input/
Dlm8333.h14 /* Active timeout before enter HALT mode in microseconds */
16 /* Debounce interval in microseconds */
/kernel/linux/linux-5.10/include/linux/input/
Dlm8333.h14 /* Active timeout before enter HALT mode in microseconds */
16 /* Debounce interval in microseconds */
/kernel/liteos_a/kernel/base/include/
Dlos_sys_pri.h52 * Number of microseconds in one second.
64 * Number of microseconds in one milliseconds.
94 * Number of microseconds in one tick.
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/regulator/
Dregulator.txt19 - regulator-enable-ramp-delay: The time taken, in microseconds, for the supply
24 - regulator-settling-time-us: Settling time, in microseconds, for voltage
27 - regulator-settling-time-up-us: Settling time, in microseconds, for voltage
31 - regulator-settling-time-down-us: Settling time, in microseconds, for voltage
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/regulator/
Dregulator.yaml64 description: The time taken, in microseconds, for the supply rail to
73 description: Settling time, in microseconds, for voltage change if regulator
78 description: Settling time, in microseconds, for voltage increase if
84 description: Settling time, in microseconds, for voltage decrease if
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/net/
Dmdio.txt8 - reset-delay-us: RESET pulse width in microseconds.
13 The 'reset-delay-us' indicates the RESET signal pulse width in microseconds and

12345678910>>...36