| /openbmc/sdeventplus/src/sdeventplus/source/ |
| H A D | time.cpp | 17 Time<Id>::Time(const Event& event, TimePoint time, Accuracy accuracy, in Time() argument
19 Base(event, create_source(event, time, accuracy), std::false_type()) in Time()
66 void Time<Id>::set_accuracy(Accuracy accuracy) const in set_accuracy()
70 get(), SdEventDuration(accuracy).count())); in set_accuracy()
87 Accuracy accuracy) in create_source() argument
95 SdEventDuration(accuracy).count(), timeCallback, nullptr)); in create_source()
|
| H A D | time.hpp | 48 Time(const Event& event, TimePoint time, Accuracy accuracy,
95 void set_accuracy(Accuracy accuracy) const;
119 Accuracy accuracy);
|
| /openbmc/linux/arch/x86/math-emu/ |
| H A D | README | 72 based upon getting good accuracy with reasonable speed.
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
303 Prior to version 1.20 of the emulator, the accuracy of the results for
[all …]
|
| /openbmc/linux/drivers/gpu/drm/ci/xfails/ |
| H A D | rockchip-rk3399-flakes.txt | 16 kms_vblank@pipe-A-accuracy-idle
20 kms_vblank@pipe-B-accuracy-idle
|
| /openbmc/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()
|
| /openbmc/u-boot/arch/arm/dts/ |
| H A D | zynqmp-clk.dtsi | 53 clock-accuracy = <100>;
60 clock-accuracy = <100>;
73 clock-accuracy = <0x64>;
|
| /openbmc/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 | sparx5-temp.rst | 24 The sensor has a range of -40°C to +125°C and an accuracy of +/-5°C.
|
| 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 | 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.)
|
| /openbmc/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 | 53 unsigned long accuracy; member
183 return osc->accuracy; in clk_slow_rc_osc_recalc_accuracy()
228 unsigned long accuracy, in at91_clk_register_slow_rc_osc() argument
254 osc->accuracy = accuracy; in at91_clk_register_slow_rc_osc()
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | IJG-short | 2 implied, with respect to this software, its quality, accuracy,
5 quality and accuracy.
|
| H A D | mpi-permissive | 10 * responsibility for the accuracy, completeness, or usefulness of any
|
| /openbmc/sdbusplus/src/ |
| H A D | event.cpp | 150 time_resolution time, time_resolution accuracy) in add_oneshot_timer() argument
157 eventp, &s.sourcep, CLOCK_BOOTTIME, time.count(), accuracy.count(), in add_oneshot_timer()
|
| /openbmc/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.
|
| /openbmc/phosphor-hwmon/ |
| H A D | sensor.cpp | 266 Sensor::addAccuracy(ObjectInfo& info, double accuracy) in addAccuracy() argument
275 iface->accuracy(accuracy); in addAccuracy()
|
| H A D | mainloop.cpp | 177 std::string accuracy; in getIdentifiers() local
184 accuracy = env::getEnv("ACCURACY", sensor.first.first, id); in getIdentifiers()
188 return std::make_tuple(std::move(id), std::move(label), std::move(accuracy), in getIdentifiers()
252 auto accuracy = stod(accuracyStr); in getObject() local
253 sensorObj->addAccuracy(info, accuracy); in getObject()
|
| /openbmc/sdeventplus/src/sdeventplus/utility/ |
| H A D | timer.cpp | 17 typename source::Time<Id>::Accuracy accuracy) : in Timer() argument
21 accuracy, nullptr) in Timer()
|
| /openbmc/linux/drivers/iio/temperature/ |
| H A 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
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/chrony/ |
| H A D | chrony_4.5.bb | 14 Typical accuracy between two machines on a LAN is in tens, or a few \
15 hundreds, of microseconds; over the Internet, accuracy is typically \
17 sub-microsecond accuracy is possible. \
|
| /openbmc/sdeventplus/src/sdeventplus/internal/ |
| H A D | sdevent.cpp | 39 uint64_t accuracy, sd_event_time_handler_t callback, void* userdata) const in sd_event_add_time() argument
41 return ::sd_event_add_time(event, source, clock, usec, accuracy, callback, in sd_event_add_time()
|