| /linux/drivers/clk/ |
| H A D | clk-fixed-rate.c | 165 u32 accuracy = 0; in _of_fixed_clk_setup() local
171 of_property_read_u32(node, "clock-accuracy", &accuracy); in _of_fixed_clk_setup()
176 0, rate, accuracy); in _of_fixed_clk_setup()
|
| H A D | kunit_clk_fixed_rate_test.dtso | 12 clock-accuracy = <TEST_FIXED_ACCURACY>;
|
| H A D | clk.c | 142 unsigned long accuracy; member
641 return core->accuracy; in clk_core_get_accuracy_no_lock()
1934 parent_accuracy = core->parent->accuracy; in __clk_recalc_accuracies()
1937 core->accuracy = core->ops->recalc_accuracy(core->hw, in __clk_recalc_accuracies()
1940 core->accuracy = parent_accuracy; in __clk_recalc_accuracies()
1965 long accuracy; in clk_get_accuracy() local
1971 accuracy = clk_core_get_accuracy_recalc(clk->core); in clk_get_accuracy()
1974 return accuracy; in clk_get_accuracy()
3801 debugfs_create_ulong("clk_accuracy", 0444, root, &core->accuracy); in clk_debug_create_one()
4093 core->accuracy = core->ops->recalc_accuracy(core->hw, in __clk_core_init()
[all …]
|
| /linux/drivers/clk/at91/ |
| H A D | clk-main.c | 40 unsigned long accuracy; member
266 return osc->accuracy; in clk_main_rc_osc_recalc_accuracy()
299 u32 frequency, u32 accuracy) in at91_clk_register_main_rc_osc() argument
322 osc->accuracy = accuracy; in at91_clk_register_main_rc_osc()
|
| H A D | sckc.c | 55 unsigned long accuracy; member
185 return osc->accuracy; in clk_slow_rc_osc_recalc_accuracy()
230 unsigned long accuracy, in at91_clk_register_slow_rc_osc() argument
256 osc->accuracy = accuracy; in at91_clk_register_slow_rc_osc()
|
| /linux/Documentation/hwmon/ |
| H A D | shtc1.rst | 58 2. high or low accuracy. High accuracy is used by default and using it is
|
| H A D | tc74.rst | 18 and +- 2 degrees centigrade accuracy.
|
| H A D | pc87360.rst | 74 readings more range or accuracy. Usually, users have to learn how it works,
81 slowest accuracy highest
94 * accuracy around 3000 RPM: 3000^2/clock
98 RPM as the lowest acceptable accuracy.
|
| H A D | sparx5-temp.rst | 24 The sensor has a range of -40°C to +125°C and an accuracy of +/-5°C.
|
| H A D | aspeed-g6-pwm-tach.rst | 24 The larger divisor, the less rpm accuracy and the less
|
| H A D | adt7410.rst | 51 -55°C to +150°C. It has a high accuracy of +/-0.5°C and can be operated at a
65 a better accuracy (0.25°C instead of 0.50°C.)
|
| H A D | gl518sm.rst | 47 degrees, with a accuracy of +/-3 degrees.
54 give the readings more range or accuracy. Not all RPM values can
|
| H A D | lan966x.rst | 25 its accuracy is +/- 5 degrees Celsius. The fan controller has a
|
| H A D | max6620.rst | 28 range or accuracy, the desired value can be set by a programmable register
|
| H A D | emc2103.rst | 26 the readings more range or accuracy. Not all RPM values can accurately be
|
| H A D | ds620.rst | 25 to +125. Between 0 and 70 degree Celsius, accuracy is 0.5 Kelvin. The value
|
| H A D | w83l786ng.rst | 40 or 128 for fan 1/2) to give the readings more range or accuracy.
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-iio-adc-mt6360 | 12 Indicated MT6360 VBUS ADC with lower accuracy(+-75mA)
20 Indicated MT6360 VBUS ADC with higher accuracy(+-30mA)
|
| H A D | sysfs-bus-iio-light-tsl2583 | 20 It is used in the process of calibrating the device accuracy.
|
| /linux/arch/arm/boot/dts/alphascale/ |
| H A D | alphascale-asm9260.dtsi | 34 clock-accuracy = <30000>;
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| H A D | lpc32xx-mlc.txt | 12 accuracy:)
|
| /linux/arch/arm/boot/dts/intel/pxa/ |
| H A D | pxa300-raumfeld-tuneable-clock.dtsi | 10 clock-accuracy = <100>;
|
| /linux/Documentation/sound/designs/ |
| H A D | timestamping.rst | 76 accuracy. It can also request the delay-to-analog be included in the
92 The audio timestamp accuracy can be returned to user-space, so that
115 The accuracy is reported in nanosecond units (using an unsigned 32-bit
191 shows how compensating for the delay exposes a 1ms accuracy (due to
|
| /linux/Documentation/timers/ |
| H A D | timekeeping.rst | 46 When the wall-clock accuracy of the clock source isn't satisfactory, there
125 between accuracy compared to the clock source, you may sacrifice accuracy
135 jiffy frequency for the architecture. This will affect scheduling accuracy
|
| /linux/drivers/xen/ |
| H A D | efi.c | 58 tc->accuracy = efi_data(op).u.get_time.accuracy; in xen_efi_get_time()
|