Searched refs:millisecond (Results 1 – 21 of 21) sorted by relevance
/linux-6.6.21/Documentation/hwmon/ |
D | ina3221.rst | 62 update_interval Data conversion time in millisecond, following: 68 * BC: bus-voltage conversion time in millisecond 69 * SC: shunt-voltage conversion time in millisecond
|
D | fam15h_power.rst | 119 This driver provides PwrCPUave and interval(default is 10 millisecond
|
/linux-6.6.21/Documentation/devicetree/bindings/net/ |
D | arc_emac.txt | 14 will have the duration be 1 millisecond. Numbers greater than 1000 are 15 invalid and 1 millisecond will be used instead.
|
D | fsl,fec.yaml | 207 duration be 1 millisecond. Numbers greater than 1000 are invalid 208 and 1 millisecond will be used instead.
|
/linux-6.6.21/arch/arm/boot/dts/rockchip/ |
D | rk3036-evb.dts | 19 phy-reset-duration = <10>; /* millisecond */
|
D | rk3036-kylin.dts | 84 phy-reset-duration = <10>; /* millisecond */
|
/linux-6.6.21/Documentation/trace/ |
D | hwlat_detector.rst | 60 The minimum sleep time between periods is 1 millisecond. Even if width 61 is less than 1 millisecond apart from window, to allow the system to not
|
D | events-nmi.rst | 30 really hogging a lot of CPU time, like a millisecond at a time.
|
D | osnoise-tracer.rst | 167 it took place one millisecond before.
|
D | ftrace.rst | 1033 - '@' - greater than 100 millisecond 1034 - '*' - greater than 10 millisecond
|
/linux-6.6.21/Documentation/devicetree/bindings/gpio/ |
D | sprd,gpio-eic.yaml | 25 stable status (millisecond resolution) and a single-trigger mechanism
|
/linux-6.6.21/Documentation/driver-api/ |
D | pps.rst | 39 sub-millisecond synchronisation to UTC.
|
/linux-6.6.21/Documentation/locking/ |
D | robust-futexes.rst | 70 every pthread_exit() takes a millisecond or more, also totally
|
/linux-6.6.21/Documentation/power/ |
D | freezing-of-tasks.rst | 245 millisecond. The default value is 20000, with range of unsigned integer.
|
/linux-6.6.21/Documentation/ABI/testing/ |
D | sysfs-class-hwmon | 23 Unit: millisecond
|
/linux-6.6.21/Documentation/RCU/ |
D | checklist.rst | 273 synchronize_rcu()'s multi-millisecond latency. So please take
|
D | RTFP.txt | 1064 …rg/conference/2004-usenix-annual-technical-conference/making-rcu-safe-deep-sub-millisecond-response
|
/linux-6.6.21/Documentation/ABI/stable/ |
D | sysfs-block | 593 millisecond. blk-throttle makes decision based on the
|
/linux-6.6.21/Documentation/RCU/Design/Requirements/ |
D | Requirements.rst | 1221 …onference/2004-usenix-annual-technical-conference/making-rcu-safe-deep-sub-millisecond-response>`__ 1227 In some cases, the multi-millisecond synchronize_rcu() latencies are 2397 of fine distinction. For example, suppose that a three-millisecond-long
|
/linux-6.6.21/Documentation/driver-api/usb/ |
D | usb.rst | 800 (millisecond) is in use. It reflects only periodic transfers, which
|
/linux-6.6.21/drivers/net/ethernet/broadcom/bnxt/ |
D | bnxt_hsi.h | 8562 __le16 millisecond; member
|