| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Telemetry/ |
| H A D | Report.interface.yaml | 21 Indicates how readings should be updated. Possible values are
26 Period of time in milliseconds when readings are updated.
57 description: Defines how readings are updated.
71 Defines period of time in milliseconds when readings are updated.
77 Indicates if readings in report will be updated. This may be set to
117 The type that defines when Readings are updated.
130 The type that defines how Readings are updated.
180 property value is updated.
186 property is updated. Redfish Event Service requires this option
|
| H A D | ReportManager.interface.yaml | 27 Indicates when readings should be updated. Possible values are
32 Indicates how readings should be updated. Possible values are
46 Period of time in milliseconds when Report is updated with new
57 Indicates if readings in report will be updated.
|
| /openbmc/u-boot/arch/x86/include/asm/fsp/ |
| H A D | fsp_support.h | 102 * If the GUID HOB is located, the length will be updated.
116 * If the GUID HOB is located, the length will be updated.
127 * If the GUID HOB is located, the length will be updated.
160 * If the GUID HOB is located, the length will be updated.
174 * If the HOB is located, the length will be updated.
186 * If the HOB is located, the length will be updated.
198 * If the HOB is located, the length will be updated.
|
| /openbmc/phosphor-pid-control/test/ |
| H A D | pid_zone_unittest.cpp | 413 r1.updated = std::chrono::high_resolution_clock::now(); in TEST_F()
418 r2.updated = std::chrono::high_resolution_clock::now(); in TEST_F()
466 r1.updated = std::chrono::high_resolution_clock::now(); in TEST_F()
471 r2.updated = std::chrono::high_resolution_clock::now(); in TEST_F()
484 // On the second updateSensors call, the updated timestamp will be beyond in TEST_F()
520 r1.updated = std::chrono::high_resolution_clock::now(); in TEST_F()
525 r2.updated = std::chrono::high_resolution_clock::now(); in TEST_F()
531 // Ok, so we're not in failsafe mode, so let's set updated to the past. in TEST_F()
532 // sensor1 will have an updated field older than its timeout value, but in TEST_F()
534 r1.updated -= std::chrono::seconds(3); in TEST_F()
[all …]
|
| H A D | sensor_host_unittest.cpp | 68 // Verify that when value is updated, the information matches in TEST()
91 // Value is updated from dbus calls only (normally). in TEST()
116 std::chrono::duration_cast<std::chrono::seconds>(t1 - r.updated) in TEST()
119 // Verify it was updated within the last second. in TEST()
|
| H A D | sensor_pluggable_unittest.cpp | 60 r.updated = std::chrono::high_resolution_clock::now(); in TEST()
67 EXPECT_EQ(r.updated, v.updated); in TEST()
|
| /openbmc/docs/designs/ |
| H A D | psu-firmware-update.md | 40 The PSU firmware shall be updated in the below cases:
68 firmware is updated:
71 - When a new version is updated together with BMC code update;
124 When BMC is updated and a new version of PSU firmware is included, it shall be
125 updated to the PSU. This will be done by the same service described above.
145 updated. This will be done by the same service described above.
152 and firmware version to decide if the firmware needs to be updated.
183 damage if the incorrect PSU firmware is updated.
205 - Verify the PSU code update is performed after a new BMC image is updated
|
| H A D | boot-progress.md | 68 which should be updated with the date and time the `LastState` was last updated.
84 - Ensure the `BootProgress` and `BootProgressLastUpdate` properties are updated
90 updated
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-crypto/libtomcrypt/ |
| H A D | libtomcrypt_1.18.2.bb | 6 # then updated to dual license PD and WTFPL also in 0.18.0-rc1:
8 # and then updated again to Unlicense after the 0.18.2 tag (it's only in develop branch):
12 # and this comment can be removed next time libtomcrypt is updated
|
| /openbmc/openbmc/poky/scripts/lib/devtool/ |
| H A D | build.py | 29 (updated, newlines) = bb.utils.edit_metadata(f, values, varfunc)
32 updated = True
35 if updated:
38 return updated
|
| /openbmc/openbmc/poky/scripts/ |
| H A D | pull-sdpx-licenses.py | 69 updated = 0
92 updated += 1
95 print(f"Updated {updated} licenses")
|
| /openbmc/phosphor-user-manager/phosphor-ldap-config/ |
| H A D | ldap_config.hpp | 111 * @param[in] value - ldapServerURI value to be updated.
117 * @param[in] value - ldapBindDN value to be updated.
123 * @param[in] value - ldapBaseDN value to be updated.
129 * @param[in] value - ldapSearchScope value to be updated.
136 * @param[in] value - ldapType value to be updated.
142 * @param[in] value - ldapServiceEnabled value to be updated.
148 * @param[in] value - userNameAttribute value to be updated.
154 * @param[in] value - groupNameAttribute value to be updated.
160 * @param[in] value - ldapBindDNPassword value to be updated.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
| H A D | ApplyTime.interface.yaml | 2 To implement the apply time of a newly updated software image. The apply
14 The possible values of this property indicate when the newly updated
|
| /openbmc/openbmc/poky/bitbake/lib/layerindexlib/tests/ |
| H A D | layerindexobj.py | 107 self.assertIsNotNone(layerItem.updated)
118 self.assertIsNotNone(layerItem.updated)
127 self.assertIsNotNone(layerBranch.updated)
139 self.assertIsNotNone(layerBranch.updated)
187 self.assertIsNotNone(recipe.updated)
199 self.assertIsNotNone(machine.updated)
210 self.assertIsNotNone(distro.updated)
|
| /openbmc/phosphor-pid-control/ |
| H A D | interfaces.hpp | 14 std::chrono::high_resolution_clock::time_point updated; member
19 return ((this->value == rhs.value) && (this->updated == rhs.updated) && in operator ==()
|
| /openbmc/phosphor-psu-code-mgmt/src/ |
| H A D | activation_listener.hpp | 16 /** @brief Notify a PSU is updated
19 * @param[in] psuInventoryPath - The PSU inventory path that is updated
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | dbus_sensor.hpp | 139 * Return the last time this sensor was updated.
192 * interfaces are updated correctly.
210 * The sensor value will only be updated if the new value differs from
219 * The sensor value will only be updated if the new value is higher than
242 * The sensor value will only be updated if the new value is lower than
292 * Set the last time this sensor was updated.
309 * @return true if value should be updated on D-Bus, false otherwise
352 * Last time this sensor was updated.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/VPD/ |
| H A D | Manager.interface.yaml | 19 Keyword whose value needs to be updated.
23 Value to be updated for the keyword.
28 On success, returns the number of bytes updated. On failure,
53 On success, returns the number of bytes updated. On failure,
76 On success, returns the number of bytes updated. On failure,
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | update_message_registry.hpp | 59 "All the target devices to be updated were determined.",
134 "No target device will be updated with image '%1'.",
158 "The target device '%1' will be updated with image '%2'.",
245 "Indicates that a resource or device was updated.",
246 "Device '%1' successfully updated with image '%2'.",
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/jack/jack/ |
| H A D | 0001-Conceal-imp-warnings-in-Python3.patch | 32 # the following 3 constants are updated on each new release (do not touch)
34 """Constant updated on new releases"""
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | tally_sheet.py | 162 be updated.
164 that is to be updated.
177 be updated.
179 that is to be updated.
192 be updated.
194 that is to be updated.
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/valkey/valkey/ |
| H A D | lua-update-Makefile-to-use-environment-build-setting.patch | 11 Updated to work with 3.0.x
15 updated to work wtih 6.2.1
19 Updated to work with 8.1.x
|
| /openbmc/qemu/tests/qemu-iotests/ |
| H A D | 260.out | 17 check updated bitmap: name=bitmap0 dirty-clusters=3
34 check updated bitmap: name=bitmap0 dirty-clusters=3
52 check updated bitmap: name=bitmap0 dirty-clusters=3
|
| /openbmc/qemu/docs/devel/ |
| H A D | multi-thread-tcg.rst | 69 updated with atomic accesses to ensure consistent results. The fall
133 There are a number of look-up caches that need to be properly updated
150 - ensure lookup caches/hashes are safely updated
154 The direct jump themselves are updated atomically by the TCG
164 The lookup caches are updated atomically and the lookup hash uses QHT
187 When the TLB tables are updated by a vCPU thread other than their own
205 - updated by its own thread when the slow-path is forced
306 following front-ends have been updated to emit fences when required:
|
| /openbmc/openbmc/poky/meta-poky/classes/ |
| H A D | poky-sanity.bbclass | 22 bb.note("Your conf/templateconf.cfg file was updated from meta-yocto to meta-poky")
38 bb.note("Your conf/bblayers.conf has been automatically updated.")
|