Home
last modified time | relevance | path

Searched full:accuracy (Results 1 – 25 of 176) sorted by relevance

12345678

/openbmc/sdeventplus/src/sdeventplus/source/
H A Dtime.hpp33 /** @brief Type used to define the accuracy of the time source */
34 using Accuracy = SdEventDuration; typedef in sdeventplus::source::Time
44 * @param[in] accuracy - Optional amount of error tolerable in time source
48 Time(const Event& event, TimePoint time, Accuracy accuracy,
83 /** @brief Gets the accuracy of the time source
86 * @return Accuracy as an std::chrono::duration
88 Accuracy get_accuracy() const;
90 /** @brief Sets the accuracy of the time source
92 * @param[in] accuracy - Accuracy as std::chrono::duration
95 void set_accuracy(Accuracy accuracy) const;
[all …]
H A Dtime.cpp17 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()
56 typename Time<Id>::Accuracy Time<Id>::get_accuracy() const in get_accuracy()
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()
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/
H A DAccuracy.interface.yaml2 Implement to provide accuracy for sensor readings.
5 - name: Accuracy
9 The accuracy range (+/-) of the sensor Value as a percentage, with a
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Sensor/Accuracy/
H A Dmeson.build3 sdbusplus_current_path = 'xyz/openbmc_project/Sensor/Accuracy'
8 '../../../../../yaml/xyz/openbmc_project/Sensor/Accuracy.interface.yaml',
28 'xyz/openbmc_project/Sensor/Accuracy',
/openbmc/phosphor-hwmon/
H A Dsensor.hpp127 * @brief Add Accuracy interface and accuracy property for sensor
128 * @details Accuracy interface is the accuracy range (+/-) of the sensor
132 * @param[in] accuracy - The accuracy value for sensor readings
134 * @return - Shared pointer to the accuracy object
137 double accuracy);
H A Dinterface.hpp7 #include <xyz/openbmc_project/Sensor/Accuracy/server.hpp>
40 sdbusplus::xyz::openbmc_project::Sensor::server::Accuracy;
51 ACCURACY, enumerator
H A Dmainloop.cpp175 std::string accuracy; in getIdentifiers() local
182 accuracy = env::getEnv("ACCURACY", sensor.first.first, id); in getIdentifiers()
186 return std::make_tuple(std::move(id), std::move(label), std::move(accuracy), in getIdentifiers()
244 // Add accuracy interface in getObject()
250 auto accuracy = stod(accuracyStr); in getObject() local
251 sensorObj->addAccuracy(info, accuracy); in getObject()
H A Dsensor.cpp266 double accuracy) in addAccuracy() argument
275 iface->accuracy(accuracy); in addAccuracy()
276 obj[InterfaceType::ACCURACY] = iface; in addAccuracy()
/openbmc/openbmc/poky/meta/files/common-licenses/
H A DNIST-PD13 ACCURACY. NIST does not warrant or make any representations regarding the use
15 correctness, accuracy, reliability or usefulness of this software.
H A DIJG-short2 implied, with respect to this software, its quality, accuracy,
5 quality and accuracy.
H A DNIST-Software14 FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT, AND DATA ACCURACY. NIST
18 THE RESULTS THEREOF, INCLUDING BUT NOT LIMITED TO THE CORRECTNESS, ACCURACY,
H A Dmetamail10 MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
H A Dmpi-permissive10 * responsibility for the accuracy, completeness, or usefulness of any
H A DIJG13accuracy, merchantability, or fitness for a particular purpose. This software is provided "AS IS",…
H A DNCBI-PD11 Although all reasonable efforts have been taken to ensure the accuracy
H A DHPND-Intel18 the software and documentation in terms of correctness, accuracy,
H A Dmpich218 …ss or implied, or assumes any legal liability or responsibility for the accuracy, completeness, or…
/openbmc/phosphor-dbus-interfaces/gen/xyz/openbmc_project/Sensor/
H A Dmeson.build2 subdir('Accuracy') subdir
36 '../../../../yaml/xyz/openbmc_project/Sensor/Accuracy.interface.yaml',
38 output: ['Accuracy.md'],
50 'xyz/openbmc_project/Sensor/Accuracy',
/openbmc/u-boot/arch/arm/dts/
H A Dzynqmp-clk.dtsi53 clock-accuracy = <100>;
60 clock-accuracy = <100>;
73 clock-accuracy = <0x64>;
/openbmc/sdeventplus/src/sdeventplus/utility/
H A Dtimer.cpp17 typename source::Time<Id>::Accuracy accuracy) : in Timer() argument
21 accuracy, nullptr) in Timer()
H A Dtimer.hpp57 * @param[in] accuracy - Optional amount of error tolerable in timer
63 typename source::Time<Id>::Accuracy accuracy =
/openbmc/openbmc/meta-openembedded/meta-oe/licenses/
H A DBellcore10 MAKES NO REPRESENTATIONS ABOUT THE ACCURACY OR SUITABILITY
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/chrony/
H A Dchrony_4.6.1.bb14 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/openbmc/meta-openembedded/meta-networking/recipes-support/htpdate/
H A Dhtpdate_1.3.7.bb8 Htpdate works through proxy servers. Accuracy of htpdate will be usually\
/openbmc/sdbusplus/src/
H A Devent.cpp150 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()

12345678