/openbmc/dbus-sensors/src/mctp/ |
H A D | MCTPReactor.cpp | 23 dev->describe()); in deferSetup() 36 ep->describe()); in trackEndpoint() 42 "MCTP_ENDPOINT", ep->describe()); in trackEndpoint() 47 "MCTP_ENDPOINT", ep->describe()); in trackEndpoint() 52 "MCTP_ENDPOINT", ep->describe()); in trackEndpoint() 66 "MCTP_ENDPOINT", ep->describe()); in trackEndpoint() 83 "MCTP_ENDPOINT", ep->describe()); in trackEndpoint() 95 "MCTP_DEVICE", dev->describe()); in setupEndpoint() 104 "MCTP_ENDPOINT", ep->describe()); in setupEndpoint() 112 "MCTP_DEVICE", dev->describe(), "ERROR_MESSAGE", ec.message()); in setupEndpoint() [all …]
|
H A D | MCTPEndpoint.hpp | 127 virtual std::string describe() const = 0; 180 virtual std::string describe() const = 0; 220 std::string describe() const override; 278 std::string describe() const override;
|
H A D | MCTPEndpoint.cpp | 130 endpoint->describe()); in endpointRemoved() 142 endpoint->describe()); in remove() 147 std::string MCTPDDevice::describe() const in describe() function in MCTPDDevice 295 "MCTP_ENDPOINT", self->describe()); in remove() 310 std::string MCTPDEndpoint::describe() const in describe() function in MCTPDEndpoint 313 dev->describe()); in describe()
|
H A D | MCTPDeviceRepository.hpp | 43 device->describe())); in add() 55 entry->second->describe())); in remove()
|
/openbmc/dbus-sensors/src/tests/ |
H A D | test_MCTPReactor.cpp | 26 MOCK_METHOD(std::string, describe, (), (const, override)); 40 MOCK_METHOD(std::string, describe, (), (const, override)); 63 EXPECT_CALL(*device, describe()) in SetUp() 69 EXPECT_CALL(*endpoint, describe()) in SetUp() 221 EXPECT_CALL(*endpoint, describe()) in TEST() 233 EXPECT_CALL(*initial, describe()) in TEST() 242 EXPECT_CALL(*replacement, describe()) in TEST()
|
/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-cson/python3-cson/ |
H A D | 0001-setup.py-Do-not-poke-at-git-describe-to-find-version.patch | 4 Subject: [PATCH] setup.py: Do not poke at git describe to find version 6 OE uses git snapshot and git describe --tags will emit a string which is 29 - version_git = subprocess.check_output(["git", "describe", "--tags"]).rstrip()
|
/openbmc/qemu/scripts/qapi/ |
H A D | schema.py | 163 def describe(self) -> str: member in QAPISchemaDefinition 376 def describe(self) -> str: member in QAPISchemaType 513 def describe(self) -> str: member in QAPISchemaArrayType 568 % self.base.describe()) 679 % (v.describe(self.info), v.type.describe())) 697 % (v.describe(self.info), types_seen[qt])) 807 % (v.name, tag_member.type.describe())) 812 % (v.describe(self.info), v.type.describe())) 875 % (self.describe(info), seen[cname].describe(info))) 882 def describe(self, info: Optional[QAPISourceInfo]) -> str: member in QAPISchemaMember [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/i2c/ |
H A D | i2c-fsi.txt | 11 - child nodes : Nodes to describe busses off the I2C 18 - child nodes : Nodes to describe devices on the I2C
|
/openbmc/webui-vue/tests/unit/ |
H A D | AppHeader.spec.js | 5 describe('AppHeader.vue', () => { 69 describe('Created lifecycle hook', () => {
|
/openbmc/linux/Documentation/PCI/ |
H A D | acpi-info.rst | 7 The general rule is that the ACPI namespace should describe everything the 11 host bridges, so the ACPI namespace must describe each host bridge, the 19 devices and read and size their BARs. However, ACPI may describe PCI 22 controllers and a _PRT is needed to describe those connections. 45 describe all the address space they consume. This includes all the windows 49 range below the bridge, window registers that describe the apertures, etc. 64 Consumer/Producer meant there was no way to describe bridge registers in 65 the PNP0A03/PNP0A08 device itself. The workaround was to describe the 76 describe bridge registers this way on those architectures. 92 The MCFG table must describe the ECAM space of non-hot pluggable host
|
/openbmc/linux/Documentation/devicetree/bindings/fsi/ |
H A D | fsi.txt | 11 FSI masters may require their own DT nodes (to describe the master HW itself); 15 Under the masters' nodes, we can describe the bus topology using nodes to 52 Since the master nodes describe the top-level of the FSI topology, they also 116 additional engines, but they don't necessarily need to be describe in the 135 * it's an I2C master controller, so subnodes describe the
|
/openbmc/openbmc/poky/meta/classes/ |
H A D | create-spdx-3.0.bbclass | 56 variable with a suffix to describe to as a suffix to look up more \ 67 # Bitbake variables can be used to describe an SPDX Agent that may be used 98 SPDX_BUILD_HOST[doc] = "The base variable name to describe the build host on \ 103 SPDX_INVOKED_BY[doc] = "The base variable name to describe the Agent that \ 108 SPDX_ON_BEHALF_OF[doc] = "The base variable name to describe the Agent on who's \ 113 SPDX_PACKAGE_SUPPLIER[doc] = "The base variable name to describe the Agent who \
|
/openbmc/openbmc/poky/meta/lib/oe/ |
H A D | buildcfg.py | 55 describe, _ = bb.process.run('git describe --tags --dirty', cwd=path) 58 return describe.strip()
|
/openbmc/openbmc/poky/meta/recipes-connectivity/iw/iw/ |
H A D | 0001-iw-version.sh-don-t-use-git-describe-for-versioning.patch | 1 Subject: [PATCH] iw: version.sh: don't use git describe for versioning 20 - descr=$(git describe --match=v* 2>/dev/null)
|
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/ |
H A D | atmel,at91-pinctrl.txt | 23 - atmel,mux-mask: array of mask (periph per bank) to describe if a pin can be 24 configured in this periph mode. All the periph and bank need to be describe. 41 For each peripheral/bank we will describe in a u32 if a pin can be 112 name describe the pin function and group hierarchy. 118 4. The gpio controller must be describe in the pinctrl simple-bus.
|
/openbmc/openbmc/meta-phosphor/recipes-core/os-release/ |
H A D | os-release.bbappend | 22 # contents of the 'git describe --dirty' call. Create a strong/immediate 24 PHOSPHOR_OS_RELEASE_DISTRO_VERSION := "${@run_git(d, 'describe --dirty')}"
|
/openbmc/linux/Documentation/driver-api/80211/ |
H A D | mac80211.rst | 49 This chapter should describe PHY handling including start/stop callbacks 62 This chapter should describe virtual interface basics that are relevant 85 This should describe the receive and transmit paths in mac80211/the
|
/openbmc/entity-manager/docs/ |
H A D | entity_manager_dbus_api.md | 15 Entities are top level json objects that describe a piece of hardware. They are 46 Entity objects describe pieces of physical hardware. 56 Configuration objects describe components owned by the Entity.
|
/openbmc/linux/security/keys/ |
H A D | user_defined.c | 31 .describe = user_describe, 51 .describe = user_describe,
|
/openbmc/linux/Documentation/input/ |
H A D | event-codes.rst | 41 - Used to describe state changes of keyboards, buttons, or other key-like 46 - Used to describe relative axis value changes, e.g. moving the mouse 5 units 51 - Used to describe absolute axis value changes, e.g. describing the 56 - Used to describe miscellaneous input data that do not fit into other types. 60 - Used to describe binary state input switches. 187 EV_REL events describe relative changes in a property. For example, a mouse may 221 EV_ABS events describe absolute changes in a property. For example, a touchpad 228 - Used to describe the distance of a tool from an interaction surface. This 240 - Used to describe the state of a multi-value profile switch. An event is 246 - Used to describe multitouch input events. Please see [all …]
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-bus-nvdimm | 14 Description: (RO) Attribute group to describe the magic bits 32 Description: (RO) Attribute group to describe performance monitoring events
|
/openbmc/qemu/scripts/ |
H A D | qemu-version.sh | 12 pkgversion=$(git describe --match 'v*' --dirty) || :
|
/openbmc/webui-vue/tests/unit/Global/ |
H A D | InfoTooltip.spec.js | 6 describe('InfoTooltip.vue', () => {
|
H A D | PageContainer.spec.js | 4 describe('PageContainer.vue', () => {
|
H A D | PageSection.spec.js | 4 describe('PageSection.vue', () => {
|