Searched full:microsecond (Results 1 – 20 of 20) sorted by relevance
| /Documentation/devicetree/bindings/regulator/ |
| D | richtek,rtmv20-regulator.yaml | 38 load current pulse delay in microsecond after strobe pin pulse high.
45 Load current pulse width in microsecond after strobe pin pulse high.
52 Fsin1 pulse high delay in microsecond after vsync signal pulse high.
59 Fsin1 pulse high width in microsecond after vsync signal pulse high.
66 Fsin2 pulse high delay in microsecond after vsync signal pulse high.
73 Fsin2 pulse high width in microsecond after vsync signal pulse high.
79 description: Eye safety function pulse width limit in microsecond.
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-idle.yaml | 36 The idle duration in microsecond the device should cool down.
40 The exit latency constraint in microsecond for the injected idle state
|
| /Documentation/userspace-api/media/rc/ |
| D | lirc-get-rec-resolution.rst | 36 signals can only be reported in 50 microsecond steps.
|
| /Documentation/ABI/testing/ |
| D | debugfs-hisi-hpre | 126 0: not wait(default), others value: wait dev_timeout * 20 microsecond.
179 0: disable(default), 1: 1 microsecond.
|
| D | debugfs-hisi-zip | 119 0: not wait(default), others value: wait dev_timeout * 20 microsecond.
|
| D | debugfs-hisi-sec | 106 0: not wait(default), others value: wait dev_timeout * 20 microsecond.
|
| /Documentation/devicetree/bindings/gpio/ |
| D | sprd,gpio-eic.yaml | 37 (microsecond resolution) to generate interrupts by level or edge trigger.
|
| /Documentation/trace/ |
| D | hwlat_detector.rst | 22 you are trying to keep event service latencies down in the microsecond range.
|
| D | ftrace.rst | 1071 - '#' - greater than 1000 microsecond
1072 - '!' - greater than 100 microsecond
1073 - '+' - greater than 10 microsecond
1074 - ' ' - less than or equal to 10 microsecond.
1592 Here we traced a 71 microsecond latency. But we also see all the
|
| /Documentation/tools/rtla/ |
| D | rtla-hwnoise.rst | 41 The tool is set to detect any noise higher than *one microsecond*,
|
| /Documentation/dev-tools/ |
| D | kcsan.rst | 186 microsecond delay to stall execution after a watchpoint has been set up.
191 interrupts, the microsecond delay to stall execution after a watchpoint has
|
| /Documentation/power/ |
| D | pm_qos_interface.rst | 14 The latency unit used in the PM QoS framework is the microsecond (usec).
|
| /Documentation/locking/ |
| D | robust-futexes.rst | 69 microsecond on Linux, but with thousands (or tens of thousands) of vmas
|
| /Documentation/usb/ |
| D | usbmon.rst | 131 depends on available clock, and so it can be much worse than a microsecond
|
| /Documentation/crypto/ |
| D | descore-readme.rst | 52 hackers in pursuit of that last microsecond. You will find it more
|
| /Documentation/networking/device_drivers/ethernet/intel/ |
| D | i40e.rst | 571 granularity in 4-microsecond intervals, so adjacent values may result in the
|
| D | ice.rst | 1130 underlying hardware supports granularity in 4-microsecond intervals, so
|
| /Documentation/RCU/Design/Requirements/ |
| D | Requirements.rst | 1030 microsecond, it would take 570 years of runtime to overflow this
2300 In addition, RCU must make do with a sub-100-microsecond real-time
2302 Linux kernel provides sub-20-microsecond real-time latencies for the
2305 surprise, the sub-100-microsecond real-time latency budget `applies to
|
| /Documentation/userspace-api/media/v4l/ |
| D | ext-ctrls-codec.rst | 429 - 50/15 microsecond emphasis
|
| /Documentation/networking/ |
| D | can.rst | 394 The timestamp has a resolution of one microsecond and is set automatically
|