Home
last modified time | relevance | path

Searched full:describe (Results 1 – 25 of 1407) sorted by relevance

12345678910>>...57

/openbmc/dbus-sensors/src/mctp/
H A DMCTPReactor.cpp23 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 …]
/openbmc/linux/Documentation/PCI/
H A Dacpi-info.rst7 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/drivers/scsi/pm8001/
H A Dpm8001_hwi.h151 * use to describe enable the phy (64 bytes)
214 * use to describe the sata task response (64 bytes)
239 * use to describe MPI REGISTER DEVICE Command (64 bytes)
292 * use to describe MPI Local Phy Control Response (64 bytes)
377 * use to describe MPI General Event Notification Response (64 bytes)
390 * use to describe MPI SMP REQUEST Command (64 bytes)
416 * use to describe MPI SMP Completion Response (64 bytes)
427 * use to describe MPI SSP SMP & SATA Abort Command (64 bytes)
439 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
451 * use to describe MPI SAS Diagnostic Start/End Command (64 bytes)
[all …]
H A Dpm80xx_hwi.h349 * use to describe enable the phy (128 bytes)
411 * use to describe the sata task response (64 bytes)
445 * use to describe MPI REGISTER DEVICE Command (64 bytes)
493 * use to describe MPI Local Phy Control Response (64 bytes)
615 * use to describe MPI General Event Notification Response (64 bytes)
627 * use to describe MPI SMP REQUEST Command (64 bytes)
654 * use to describe MPI SMP Completion Response (64 bytes)
665 * use to describe MPI SSP SMP & SATA Abort Command (64 bytes)
677 * use to describe SSP SMP & SATA Abort Response ( 64 bytes)
688 * use to describe MPI SAS Diagnostic Start/End Command (64 bytes)
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A Dredfish-error.v1_0_2.json14 "description": "The properties that describe an error from a Redfish service.",
15 …s described by the Redfish Specification, shall contain properties that describe an error from a R…
25 "description": "The properties that describe an error from a Redfish service.",
26 …"The Redfish Specification-described type shall contain properties that describe an error from a R…
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A Dredfish-error.v1_0_2.json14 "description": "The properties that describe an error from a Redfish service.",
15 …s described by the Redfish Specification, shall contain properties that describe an error from a R…
25 "description": "The properties that describe an error from a Redfish service.",
26 …"The Redfish Specification-described type shall contain properties that describe an error from a R…
H A DManifest.v1_1_2.json27 …"longDescription": "This type shall describe a manifest containing a set of requests to be fulfill…
66 … "description": "An array of stanzas that describe the requests specified by this manifest.",
77 …longDescription": "This property shall contain an array of stanzas that describe the requests spec…
96 …"longDescription": "This type shall describe the request details of a stanza within a manifest. I…
117 …"longDescription": "This type shall describe the response details of a stanza within a manifest. …
137 …"description": "A stanza contains properties that describe a request to be fulfilled within a mani…
138 …"longDescription": "This type shall contain properties that describe a request to be fulfilled wit…
H A DSwitchMetrics.v1_0_2.json72 …"longDescription": "This type shall describe the memory metrics since the last reset or `ClearCurr…
112 …"longDescription": "This property shall contain properties that describe the memory metrics for a …
131 …"longDescription": "This property shall contain properties that describe the metrics for the curre…
136 …"longDescription": "This property shall contain properties that describe the metrics for the lifet…
144 …"longDescription": "This type shall describe the memory metrics since manufacturing for a switch.",
256 …"longDescription": "This property shall contain properties that describe the memory metrics for a …
H A DProcessorMetrics.v1_6_4.json40 …"longDescription": "This type shall contain properties that describe the C-state residency of the …
82 …"longDescription": "This type shall contain properties that describe cache metrics of a processor …
161 …"longDescription": "This property shall contain properties that describe the metrics for all of th…
180 …"longDescription": "This property shall contain properties that describe the metrics for the curre…
186 …"longDescription": "This property shall contain properties that describe the metrics for the lifet…
228 … "longDescription": "This type shall contain properties that describe the cores of a processor.",
249 …"longDescription": "This property shall contain properties that describe the C-state residency of …
257 …"longDescription": "This property shall contain properties that describe the cache metrics of this…
351 …"longDescription": "This type shall describe the cache memory metrics since last system reset or `…
393 …"longDescription": "This type shall describe the cache memory metrics since manufacturing for a pr…
[all …]
/openbmc/webui-vue/.github/ISSUE_TEMPLATE/
H A Dfeature_request.md9 **Is your feature request related to a problem? Please describe.** A clear and
12 **Describe the solution you'd like** A clear and concise description of what you
15 **Describe alternatives you've considered** A clear and concise description of
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-fs-nilfs214 Describe attributes of /sys/fs/nilfs2/features group.
58 Describe attributes of /sys/fs/nilfs2/<device> group.
90 Describe attributes of /sys/fs/nilfs2/<device>/superblock
180 Describe attributes of /sys/fs/nilfs2/<device>/segctor
211 Describe attributes of /sys/fs/nilfs2/<device>/segments
242 Describe attributes of /sys/fs/nilfs2/<device>/checkpoints
249 Describe content of /sys/fs/nilfs2/<device>/mounted_snapshots
268 Describe attributes of /sys/fs/nilfs2/<device>/mounted_snapshots/<id>
/openbmc/openbmc/meta-raspberrypi/.github/
H A DISSUE_TEMPLATE.md11 Briefly describe the problem you are having in a few paragraphs.
19 **Describe the results you received:**
22 **Describe the results you expected:**
/openbmc/openbmc/poky/meta/files/
H A Dlayers.example.json7 "describe": "", string
20 "describe": "15.0-hardknott-3.3-310-g0a96edae", string
33 "describe": "4.1_M1-374-g9dda719b2a", string
/openbmc/openbmc/poky/meta/classes/
H A Dcreate-spdx-3.0.bbclass56 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/linux/Documentation/input/
H A Devent-codes.rst41 - 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/devicetree/bindings/fsi/
H A Dfsi.txt11 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/linux/Documentation/devicetree/bindings/pinctrl/
H A Datmel,at91-pinctrl.txt23 - 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/dbus-sensors/src/tests/
H A Dtest_MCTPReactor.cpp26 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()
207 EXPECT_CALL(*endpoint, describe()) in TEST()
219 EXPECT_CALL(*initial, describe()) in TEST()
228 EXPECT_CALL(*replacement, describe()) in TEST()
/openbmc/openbmc/meta-openembedded/meta-python/recipes-extended/python-cson/python3-cson/
H A D0001-setup.py-Do-not-poke-at-git-describe-to-find-version.patch4 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/linux/drivers/interconnect/imx/
H A Dimx.h50 * struct imx_icc_node_adj - Describe a dynamic adjustable node
59 * struct imx_icc_node - Describe an interconnect node
74 * struct imx_icc_noc_setting - Describe an interconnect node setting
/openbmc/openbmc/poky/meta/lib/oe/
H A Dbuildcfg.py55 describe, _ = bb.process.run('git describe --tags --dirty', cwd=path)
58 return describe.strip()
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DRedfishError_v1.xml32 …<Annotation Term="OData.Description" String="The properties that describe an error from a Redfish …
33 …s described by the Redfish Specification, shall contain properties that describe an error from a R…
40 …<Annotation Term="OData.Description" String="The properties that describe an error from a Redfish …
41 …"The Redfish Specification-described type shall contain properties that describe an error from a R…
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DRedfishError_v1.xml32 …<Annotation Term="OData.Description" String="The properties that describe an error from a Redfish …
33 …s described by the Redfish Specification, shall contain properties that describe an error from a R…
40 …<Annotation Term="OData.Description" String="The properties that describe an error from a Redfish …
41 …"The Redfish Specification-described type shall contain properties that describe an error from a R…
/openbmc/qemu/scripts/qapi/
H A Dschema.py163 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/openbmc/poky/meta/lib/oeqa/selftest/cases/
H A Dbblayers.py217 first_desc_1 = data['sources'][repos[0]]['git-remote']['describe']
219 second_desc_1 = data['sources'][repos[1]]['git-remote']['describe']
222 self.assertEqual(first_desc_1, '', "Describe not cleared: '{}'".format(first_desc_1))
224 self.assertEqual(second_desc_1, '', "Describe not cleared: '{}'".format(second_desc_1))
235 first_desc_2 = data['sources'][repos[0]]['git-remote']['describe']
237 second_desc_2 = data['sources'][repos[1]]['git-remote']['describe']
240 self.assertEqual(first_desc_2, '', "Describe not cleared: '{}'".format(first_desc_2))
242 …self.assertEqual(second_desc_2, second_desc_1, "Describe should not be updated: '{}'".format(secon…

12345678910>>...57