Home
last modified time | relevance | path

Searched full:an (Results 1 – 25 of 4975) sorted by relevance

12345678910>>...199

/openbmc/phosphor-power/phosphor-regulators/src/
H A Dconfig_file_parser.hpp11 * distributed under the License is distributed on an "AS IS" BASIS,
67 * Throws a ConfigFileParserError if an error occurs.
85 * Throws an invalid_argument exception if the property does not exist.
107 * Parses a JSON element containing an action.
111 * Throws an exception if parsing fails.
119 * Parses a JSON element containing an array of actions.
123 * Throws an exception if parsing fails.
132 * Parses a JSON element containing an and action.
136 * Throws an exception if parsing fails.
148 * Throws an exception if parsing fails.
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/Callout/
H A DREADME.md5 A callout is typically an indication of a faulty hardware component in a system.
6 In OpenBMC, a callout is defined as any other error, via a YAML file. An example
7 would be `xyz.openbmc_project.Error.Callout.IIC`, to indicate an IIC callout.
10 is familiar to them, such as a sysfs entry, or an IIC address. It would be up to
16 An OpenBMC error has associated metadata, the same is true for a callout. Such
17 metadata would be defined in the callout YAML interface. Here is an example (for
29 An application wanting to add an IIC callout will have to provide values for the
31 figure out that this is in fact an IIC callout.
33 A callout is typically associated with an error log. For eg,
34 `xyz.openbmc_project.Error.Foo` may want to add an IIC callout. This is
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/src/
H A Dconfig_file_parser.hpp11 * distributed under the License is distributed on an "AS IS" BASIS,
50 * Throws an exception if an error occurs.
55 * @return path to the JSON configuration file, or an empty path if none was
67 * Throws a ConfigFileParserError if an error occurs.
83 * Throws an invalid_argument exception if the property does not exist.
109 * Throws an exception if parsing fails.
129 * Throws an exception if parsing fails.
141 * Throws an exception if parsing fails.
149 * Parses a JSON element containing an array of rails.
153 * Throws an exception if parsing fails.
[all …]
/openbmc/qemu/include/qom/
H A Dobject_interfaces.h23 * @can_be_deleted: callback to be called before an object is removed
32 * Interface also provides an optional ability to do the second
53 * @errp: if an error occurs, a pointer to an area to store the error
78 * @errp: if an error occurs, a pointer to an area to store the error
80 * Create an instance of the user creatable object @type, placing
93 * @errp: if an error occurs, a pointer to an area to store the error
95 * Create an instance of the user creatable object according to the
103 * @errp: if an error occurs, a pointer to an area to store the error
110 * Returns: ObjectOptions on success, NULL when an error occurred (*errp is set
118 * @errp: if an error occurs, a pointer to an area to store the error
[all …]
/openbmc/qemu/tests/functional/
H A Dtest_x86_cpu_model_versions.py77 Check if unversioned CPU model is an alias pointing to right version
90 'Cascadelake-Server must be an alias of Cascadelake-Server-v1')
92 'Cascadelake-Server-v1 must not be an alias')
97 'qemu64 must be an alias of qemu64-v1')
99 'qemu64-v1 must not be an alias')
106 "Haswell must be an alias")
109 "Haswell-noTSX must be an alias")
112 "Haswell-IBRS must be an alias")
115 "Haswell-noTSX-IBRS must be an alias")
119 "Broadwell must be an alias")
[all …]
/openbmc/u-boot/drivers/video/bridge/
H A DKconfig7 requires LVDS, an eDP->LVDS bridge chip can be used to provide the
15 differential signalling) converters. They enable an LVDS LCD panel
16 to be connected to an eDP output device such as an SoC that lacks
25 signalling) converter. It enables an LVDS LCD panel to be connected
26 to an eDP output device such as an SoC that lacks LVDS capability,
34 The Analogix ANX6345 is RGB-to-DP converter. It enables an eDP LCD
35 panel to be connected to an parallel LCD interface.
/openbmc/openbmc/poky/meta/lib/oeqa/selftest/cases/
H A Dincompatible_lic.py21 # Verify that a package with an SPDX license cannot be built when
22 # INCOMPATIBLE_LICENSE contains an alias (in SPDXLICENSEMAP) of this SPDX
25 …_test('incompatible-license', 'GPL-3.0-only', 'GPLv3', "is an obsolete license, please use an SPDX…
27 # Verify that a package with an SPDX license cannot be built when
31 …self.lic_test('incompatible-license', 'GPL-3.0-only', '*GPLv3', "*GPLv3 is an invalid license wild…
33 # Verify that a package with an alias (from SPDXLICENSEMAP) to an SPDX
36 …'incompatible-license-alias', 'GPL-3.0-only', 'GPLv3', "is an obsolete license, please use an SPDX…
38 # Verify that a package with an alias (from SPDXLICENSEMAP) to an SPDX
42 …self.lic_test('incompatible-license-alias', 'GPL-3.0-only', '*GPL-3.0', "*GPL-3.0 is an invalid li…
44 # Verify that a package with an alias (from SPDXLICENSEMAP) to an SPDX
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/
H A DAttributeRegistry.v1_3_9.json37 …an attribute registry. It includes mechanisms for building user interfaces, or menus, allowing co…
38 …"longDescription": "This resource shall represent an attribute registry for a Redfish implementati…
80 … "longDescription": "This property shall contain an RFC5646-conformant language code.",
112 "description": "An array of systems that this attribute registry supports.",
116 …"longDescription": "This property shall contain an array containing a list of systems that this at…
141 "Integer": "An integer value.",
149 "description": "A possible value for an enumeration attribute.",
177 …ame` is a unique string within the list of possible values in the `Value` array for an attribute.",
189 "description": "An attribute and its possible values and other metadata.",
190 …"longDescription": "This type shall describe an attribute and its possible values and other metada…
[all …]
H A DPhysicalContext.json84 "ACInput": "An AC electrical input or input-related circuit.",
85 "ACMaintenanceBypassInput": "An AC electrical maintenance bypass input.",
86 "ACOutput": "An AC electrical output or output-related circuit.",
87 "ACStaticBypassInput": "An AC electrical static bypass input.",
88 "ACUtilityInput": "An AC electrical utility input.",
89 "ASIC": "An ASIC device, such as a networking chip or chipset component.",
90 "Accelerator": "An accelerator.",
102 "ExpansionBay": "An expansion bay.",
104 "FPGA": "An FPGA.",
120 "PowerOutlet": "An electrical outlet.",
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/
H A DAttributeRegistry.v1_3_9.json37 …an attribute registry. It includes mechanisms for building user interfaces, or menus, allowing co…
38 …"longDescription": "This resource shall represent an attribute registry for a Redfish implementati…
80 … "longDescription": "This property shall contain an RFC5646-conformant language code.",
112 "description": "An array of systems that this attribute registry supports.",
116 …"longDescription": "This property shall contain an array containing a list of systems that this at…
141 "Integer": "An integer value.",
149 "description": "A possible value for an enumeration attribute.",
177 …ame` is a unique string within the list of possible values in the `Value` array for an attribute.",
189 "description": "An attribute and its possible values and other metadata.",
190 …"longDescription": "This type shall describe an attribute and its possible values and other metada…
[all …]
H A DPhysicalContext.json84 "ACInput": "An AC electrical input or input-related circuit.",
85 "ACMaintenanceBypassInput": "An AC electrical maintenance bypass input.",
86 "ACOutput": "An AC electrical output or output-related circuit.",
87 "ACStaticBypassInput": "An AC electrical static bypass input.",
88 "ACUtilityInput": "An AC electrical utility input.",
89 "ASIC": "An ASIC device, such as a networking chip or chipset component.",
90 "Accelerator": "An accelerator.",
102 "ExpansionBay": "An expansion bay.",
104 "FPGA": "An FPGA.",
120 "PowerOutlet": "An electrica
[all...]
/openbmc/bmcweb/redfish-core/include/registries/
H A Dupdate_message_registry.hpp6 * This is an auto-generated header which contains definitions
58 …"Indicates that all target resources or devices for an update operation were determined by the ser…
68 "Indicates that the component failed to apply an image.",
81 "Indicates that a component is applying an image.",
94 …"Indicates that the resource or device is waiting for an action to proceed with activating an imag…
95 "Awaiting for an action to proceed with activating image '%1' on '%2'.",
107 …"Indicates that the resource or device is waiting for an action to proceed with installing an imag…
108 "Awaiting for an action to proceed with installing image '%1' on '%2'.",
120 "Indicates that a component is installing an image.",
133 "Indicates that no target resource or device for an image was determined for update.",
[all …]
/openbmc/phosphor-power/phosphor-power-sequencer/docs/
H A Dmonitoring_chassis_pgood.md35 - Log an error specifying the power on attempt failed due to an inability to
41 - Log an error specifying an input power problem.
43 - Log an error specifying the power on attempt failed due to an inability to
60 - Log an error specifying an inability to read the chassis power good status.
66 - Log an error specifying an input power problem.
70 - Log an error specifying an inability to read the chassis power good
/openbmc/libpldm/include/libpldm/
H A Dbios_table.h51 * @return Pointer to an entry in bios table
57 * @return Pointer to an entry in bios attribute table
68 * @return Pointer to an entry in bios string table
79 * @return Pointer to an entry in bios attribute value table
88 /** @brief Get the length of an entry in the BIOS String Table
90 * @return Length of an entry in bytes
94 /** @brief Create an entry of BIOS String Table and check the validity of the
97 * @param[out] entry - Pointer to a buffer to create an entry
98 * @param[in] entry_length - Length of the buffer to create an entry
102 * PLDM_ERROR_INVALID_LENGTH if entry_length is insufficient for encoding str. An
[all …]
/openbmc/qemu/include/qapi/
H A Dvisitor.h30 * and QemuOpts) parse an external representation and build the
32 * take a QAPI object and generate an external representation, the
72 * the root of a tree, @name is ignored; when visiting a member of an
74 * member of a list, @name is NULL; and when visiting the member of an
88 * If an error is detected during visit_type_FOO() with an input
92 * Using an output or clone visitor with an incomplete object has
95 * incomplete objects. Since input visitors never produce an
96 * incomplete object, such an object is possible only by manual
102 * is an additional generated function in qapi-visit-MODULE.h
183 * succeeded, even if an intermediate visit encounters an error).
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/
H A DObjectMapper.interface.yaml20 An array of result set constraining interfaces.
30 Obtain a dictionary of ancestor -> services where ancestor is an
41 An array of result set constraining interfaces.
66 An array of result set constraining interfaces.
76 Obtain an array of paths where array elements are in subtree.
90 An array of result set constraining interfaces.
95 An array of paths.
100 Same as GetSubTree, but only return the dbus paths that are an
119 An array of result set constraining interfaces.
129 Same as GetSubTreePaths, but only return the dbus paths that are an
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/
H A DCable.events.yaml10 description: The port where an expected cable is not connected.
12 description: An expected cable is not connected.
13 message: An expected cable on port {PortId} is not connected.
23 description: The port where an expected cable is connected.
25 description: An expected cable is connected.
26 message: An expected cable on port {PortId} is connected.
/openbmc/qemu/docs/
H A Dimage-fuzzer.txt44 The runner uses an external image fuzzer to generate test images. An image
79 - $off for an offset in the fuzzed image
136 The runner calls an image generator specifying the path to a test image file,
138 An image generator is expected to provide a
155 purpose, so an image generator is not recommended to modify it internally.
183 6. Should generate the test image with the correct structure based on an image
185 7. Should accept a seed as an argument (for regression purpose)
186 8. Should generate a seed if it is not specified as an input parameter.
189 10. Should accept a vector of actions as an argument (for test reproducing and
193 actions, if it is not specified as an input parameter
[all …]
/openbmc/bmcweb/docs/
H A DDBUS_USAGE.md6 - Do not require (ie set 500 internal error on) an implementation present a
10 - If an implementation presents a property that doesn't match the type specified
12 - If the DBus interface definition has an "unknown" or "unspecified" value,
15 - All DBus interfaces on all object paths are optional. An object missing an
16 interface is never an error, and shall simply omit the relevant properties
22 - There are interfaces for which there is an expectation that there will only
/openbmc/qemu/include/hw/xtensa/
H A Dxtensa-isa.h20 * CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
48 * . an instruction buffer - for holding the raw instruction bits
73 * specific values are only fixed for a particular instantiation of an
108 * Decoding an instruction involves first finding the format, which
124 * Encoding an instruction is roughly the same procedure in reverse:
144 * xtensa_isa_ok, an error message containing additional information
146 * The error messages are stored in an internal buffer, which should
188 /* Allocate an xtensa_insnbuf of the right size. */
193 /* Release an xtensa_insnbuf. */
230 /* Deallocate an xtensa_isa structure. */
[all …]
/openbmc/qemu/docs/interop/
H A Dparallels.rst34 Block Allocation Table, an entity that contains information for
40 The header is placed at the start of an image and contains the following
76 A zero in this field means that the image was opened by an old
83 An offset, in sectors, from the start of the file to the start of
105 Format Extension offset, an offset, in sectors, from the start of
118 Each BAT entry contains an offset from the start of the file to the
137 The data area is an area from the data offset (provided by ``header.data_off``
148 The Format Extension is an area 1 cluster in size that provides additional
173 If the software cannot load the extension (due to an
175 changed. If this flag is unset and there is an error on
[all …]
/openbmc/docs/architecture/code-update/
H A Demmc-storage-design.md11 Proposal to define an initial storage design for an eMMC device. This includes
25 - Updatable: Ensure that the filesystem design allows for an effective and
45 partitioning due to the lack of offline tools to build an LVM image (see
48 - Initramfs: An initramfs is needed to run sgdisk on first boot to move the
50 tool does not currently support building an image of a specified size and
61 bind mount is more reliable than an overlay, and has been around longer. Since
64 by the image, so it is an overlayfs to have the ability to restore its
86 SOCs such as the AST2500 do not support executing U-Boot from an eMMC. In
111 - Filesystem: f2fs (Flash-Friendly File System). The f2fs is an up-and-coming
113 ext4 filesystem, although it is unknown how any of the two would perform in an
[all …]
/openbmc/qemu/docs/devel/
H A Dmultiple-iothreads.rst16 QEMU is an event-driven program that can do several things at once using an
53 The main difference between legacy code and new code that can run in an
67 * LEGACY ``qemu_aio_set_event_notifier()`` - monitor an event notifier
71 * LEGACY ``qemu_aio_wait()`` - run an event loop iteration
74 runs in an ``IOThread``. They might cause a crash or deadlock if called from an
79 * ``aio_set_event_notifier()`` - monitor an event notifier
83 * ``aio_poll()`` - run an event loop iteration
93 ``qemu_get_aio_context()``. Code that takes an ``AioContext`` argument
97 How to synchronize with an ``IOThread``
104 are thread-safe. They can be used to trigger activity in an ``IOThread``.
[all …]
/openbmc/u-boot/drivers/sound/
H A DKconfig6 Support making sounds through an audio codec. This is normally a
28 Rockchip SoCs support an I2S interface for sending audio data to an
37 Samsung Exynos SoCs support an I2S interface for sending audio
38 data to an audio codec. This option enables support for this,
40 option provides an implementation for sound_init() and
52 This is quite an old feature, called PIT (Programmable Interval
59 Most Intel chips have an HDA (High-definition audio) codec which can
102 Enable the Realtek RT5677 audio codec. This is an I2S device used on
104 an I2C interface and supports multiple sound inputs and outputs,
/openbmc/docs/designs/
H A Dnmi-dbus-interface.md23 Whenever the host is unresponsive/running, Admin needs to trigger an NMI event
24 which, in turn, triggers an architecture-dependent procedure that fires an
29 This proposal aims to trigger NMI, which in turn will invoke an
48 - ComputerSystem 1.6.0 schema provides an action called #ComputerSystem.Reset,
51 An NMI type
52 - Nmi: Generate a Diagnostic Interrupt (usually an NMI on x86 systems) to
63 3. Redfish URI will invoke a D-Bus NMI back-end call which will use an arch
65 trigger an NMI on all the processors on the system.
70 - Note: NMI can be sent to the host in any state, not just at an unresponsive

12345678910>>...199