| /kernel/linux/linux-4.19/arch/x86/math-emu/ |
| D | README | 72 based upon getting good accuracy with reasonable speed.
225 ----------------------- Accuracy of wm-FPU-emu -----------------------
228 The accuracy of the emulator is in almost all cases equal to or better
237 The following table compares the emulator accuracy for the sqrt(),
240 would be 64 bits. The reduced Turbo C accuracy of cos() and tan() for
243 accurate to 64 bits can result in a relative accuracy in cos() of
260 ** The accuracy for exp() and log() is low because the FPU (emulator)
274 consequence, the accuracy of these functions for large arguments has
276 FPU). There is also now no degradation of accuracy for fcos and fptan
278 definition of accuracy has changed slightly from that used for the
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/math-emu/ |
| D | README | 72 based upon getting good accuracy with reasonable speed.
225 ----------------------- Accuracy of wm-FPU-emu -----------------------
228 The accuracy of the emulator is in almost all cases equal to or better
237 The following table compares the emulator accuracy for the sqrt(),
240 would be 64 bits. The reduced Turbo C accuracy of cos() and tan() for
243 accurate to 64 bits can result in a relative accuracy in cos() of
260 ** The accuracy for exp() and log() is low because the FPU (emulator)
274 consequence, the accuracy of these functions for large arguments has
276 FPU). There is also now no degradation of accuracy for fcos and fptan
278 definition of accuracy has changed slightly from that used for the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/clock/ |
| D | fixed-clock.txt | 13 - clock-accuracy : accuracy of clock in ppb (parts per billion).
22 clock-accuracy = <100>;
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/clock/ |
| D | fixed-clock.yaml | 22 clock-accuracy:
23 description: accuracy of clock in ppb (parts per billion).
42 clock-accuracy = <100>;
|
| /kernel/linux/linux-4.19/drivers/clk/at91/ |
| D | sckc.c | 52 unsigned long accuracy; member
193 return osc->accuracy; in clk_slow_rc_osc_recalc_accuracy()
238 unsigned long accuracy, in at91_clk_register_slow_rc_osc() argument
262 osc->accuracy = accuracy; in at91_clk_register_slow_rc_osc()
280 u32 accuracy = 0; in of_at91sam9x5_clk_slow_rc_osc_setup() local
286 of_property_read_u32(np, "clock-accuracy", &accuracy); in of_at91sam9x5_clk_slow_rc_osc_setup()
289 hw = at91_clk_register_slow_rc_osc(sckcr, name, frequency, accuracy, in of_at91sam9x5_clk_slow_rc_osc_setup()
|
| D | clk-main.c | 45 unsigned long accuracy; member
271 return osc->accuracy; in clk_main_rc_osc_recalc_accuracy()
285 u32 frequency, u32 accuracy) in at91_clk_register_main_rc_osc() argument
308 osc->accuracy = accuracy; in at91_clk_register_main_rc_osc()
324 u32 accuracy = 0; in of_at91sam9x5_clk_main_rc_osc_setup() local
330 of_property_read_u32(np, "clock-accuracy", &accuracy); in of_at91sam9x5_clk_main_rc_osc_setup()
336 hw = at91_clk_register_main_rc_osc(regmap, name, frequency, accuracy); in of_at91sam9x5_clk_main_rc_osc_setup()
|
| /kernel/linux/linux-5.10/drivers/clk/ |
| D | clk-fixed-rate.c | 145 u32 accuracy = 0; in _of_fixed_clk_setup() local
151 of_property_read_u32(node, "clock-accuracy", &accuracy); in _of_fixed_clk_setup()
156 0, rate, accuracy); in _of_fixed_clk_setup()
|
| /kernel/linux/linux-5.10/drivers/iio/temperature/ |
| D | Kconfig | 23 high accuracy digital temperature measurement system.
68 tristate "MLX90632 contact-less infrared sensor with medical accuracy"
73 MLX90632 contact-less infrared sensor with medical accuracy
|
| /kernel/linux/linux-4.19/drivers/clk/ |
| D | clk-fixed-rate.c | 166 u32 accuracy = 0; in _of_fixed_clk_setup() local
172 of_property_read_u32(node, "clock-accuracy", &accuracy); in _of_fixed_clk_setup()
177 0, rate, accuracy); in _of_fixed_clk_setup()
|
| /kernel/linux/linux-4.19/Documentation/hwmon/ |
| D | shtc1 | 36 2. high or low accuracy. High accuracy is used by default and using it is
|
| D | pc87360 | 65 readings more range or accuracy. Usually, users have to learn how it works,
71 slowest accuracy highest
81 * accuracy around 3000 RPM: 3000^2/clock
84 RPM as the lowest acceptable accuracy.
|
| D | sht3x | 32 2. high or low accuracy. High accuracy is used by default and using it is
|
| D | adt7410 | 32 -55°C to +150°C. It has a high accuracy of +/-0.5°C and can be operated at a
46 a better accuracy (0.25°C instead of 0.50°C.)
|
| D | gl518sm | 40 degrees, with a accuracy of +/-3 degrees.
47 give the readings more range or accuracy. Not all RPM values can
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | shtc1.rst | 58 2. high or low accuracy. High accuracy is used by default and using it is
|
| 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.
|
| D | gl518sm.rst | 47 degrees, with a accuracy of +/-3 degrees.
54 give the readings more range or accuracy. Not all RPM values can
|
| /kernel/linux/linux-4.19/arch/arm64/boot/dts/xilinx/ |
| D | zynqmp-clk.dtsi | 51 clock-accuracy = <100>;
58 clock-accuracy = <100>;
71 clock-accuracy = <0x64>;
|
| /kernel/linux/linux-5.10/drivers/clk/at91/ |
| D | clk-main.c | 39 unsigned long accuracy; member
240 return osc->accuracy; in clk_main_rc_osc_recalc_accuracy()
254 u32 frequency, u32 accuracy) in at91_clk_register_main_rc_osc() argument
277 osc->accuracy = accuracy; in at91_clk_register_main_rc_osc()
|
| /kernel/linux/linux-4.19/drivers/iio/temperature/ |
| D | Kconfig | 47 tristate "MLX90632 contact-less infrared sensor with medical accuracy"
52 MLX90632 contact-less infrared sensor with medical accuracy
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| 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
|
| /kernel/linux/linux-4.19/Documentation/timers/ |
| D | timekeeping.txt | 45 When the wall-clock accuracy of the clock source isn't satisfactory, there
124 between accuracy compared to the clock source, you may sacrifice accuracy
134 jiffy frequency for the architecture. This will affect scheduling accuracy
|
| /kernel/linux/linux-5.10/Documentation/sound/designs/ |
| 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
|
| /kernel/linux/linux-4.19/Documentation/sound/designs/ |
| 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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | tc_police.sh | 143 …cted rate $(humanize $er), got $(humanize $nr), which is $nr_pct% off. Required accuracy is +-10%."
193 …cted rate $(humanize $er), got $(humanize $nr), which is $nr_pct% off. Required accuracy is +-10%."
263 …cted rate $(humanize $er), got $(humanize $nr), which is $nr_pct% off. Required accuracy is +-10%."
273 …cted rate $(humanize $er), got $(humanize $nr), which is $nr_pct% off. Required accuracy is +-10%."
|