| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 1 # Power Supply Monitoring Application
7 Created: 2019-06-17
12 supply application for enterprise class systems. Some enterprise class systems
14 supply types and numbers. An application capable of communicating with the
22 The OpenBMC project currently has a [witherspoon-pfault-analysis][1] repository
23 that contains a power supply monitor application and a power sequencer monitor
24 application. The current power supply application is lacking things desired for
27 The intent of this new application design is to enhance the OpenBMC project with
28 a single power supply application that can communicate with one or more
30 in the existing application that has multiple instances talking to a single
[all …]
|
| H A D | voltage-regulator-configuration.md | 8 Created: 2019-07-13
13 voltage, over-current limit, and pgood thresholds. The configuration is often
17 new application is needed to configure regulators. It should be data-driven to
18 support a variety of regulator types and to avoid hard-coded logic.
24 Hardware engineers must specify many low-level configuration values for a
25 regulator. Some simple examples include output voltage, over-current limit, and
33 non-volatile memory on the regulator. This provides the hardware/power-on
39 - New information found during hardware testing. For example, downstream
41 - Hardware workarounds. Problems in the regulator hardware or related hardware
47 - Improve manufacturing yields. Sometimes regulator configuration values must be
[all …]
|
| H A D | thermal-control-modes.md | 7 Created: 2019-02-06
13 can be resolved by altering the fan control application's floor table,
17 optical cables plugged into a card downwind from the GPUs' exhaust, an end-user
35 https://github.com/openbmc/dbus-sensors/blob/master/src/ExitAirTempSensor.cpp
39 Create the ability for an end-user to enable the use of a thermal control mode
40 other than the default. In this use-case, the mode is specific to an
42 standardized profile/modes such "Acoustic" and "Performance". Once the end-user
43 selects a documented mode for the platform, the thermal control application
45 implementation specific to that instance of the application on that platform.
54 As one implementation, phosphor-fan-presence/control would be updated to extend
[all …]
|
| H A D | vpd-collection.md | 5 Created: 2019-06-11
10 Field Replaceable Units (FRUs) today - one example is the BMC FRU. On OpenPower
18 - Some of the VPD information such as FRU part number, serial number need to be
21 - Several use cases on the BMC require that the applications decide on a certain
23 application that controls voltage regulators might need to set different
26 - There are use cases for the BMC to send VPD data to the host
31 of certain parameters of the FRU (atypical - for FRUs that do not have an
39 Essentially, the IPZ VPD structure consists of key-value pairs called keywords.
40 Each keyword can be used to contain specific data about the FRU. For example,
52 - IPZ VPD has different records and keywords.
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | Application.v1_0_1.json | 2 "$id": "http://redfish.dmtf.org/schemas/v1/Application.v1_0_1.json",
3 "$ref": "#/definitions/Application",
4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
26 "#Application.Reset": {
31 "description": "The available OEM-specific actions for this resource.",
32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
37 "Application": { object
39 …"description": "The `Application` schema represents an application or service running on a compute…
[all …]
|
| H A D | AllowDeny.v1_0_3.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
54 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/context"
57 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/etag"
60 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/id"
63 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/type"
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | pixfmt-v4l2.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
4 Single-planar format structure
13 .. flat-table:: struct v4l2_pix_format
14 :header-rows: 0
15 :stub-columns: 0
18 * - __u32
19 - ``width``
20 - Image width in pixels.
21 * - __u32
22 - ``height``
[all …]
|
| /openbmc/phosphor-networkd/docs/ |
| H A D | Network-Configuration.md | 19 1. SystemConfiguration: This describes the system-specific parameters.
20 2. EthernetInterface: This describes the interface-specific parameters.
21 3. IP: This describes the IP address-specific parameters.
23 5. VLANInterface: This describes the VLAN-specific properties.
42 IPv4 objects will have the following D-Bus object path.
46 IPv6 objects will have the following D-Bus object path.
66 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST -d
76 busctl get-property xyz.openbmc_project.Network
80 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X GET
87 busctl set-property xyz.openbmc_project.Network
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/config_file/ |
| H A D | README.md | 1 # phosphor-power-sequencer Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Name](#name)
8 - [Contents](#contents)
9 - [Installation](#installation)
13 The `phosphor-power-sequencer` configuration file (config file) contains
21 The config file is optional. If no file is found, the application will log a
22 general error when a pgood fault occurs. No specific rail will be identified.
33 A config file is normally system-specific. Each system type usually has a
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 1 # phosphor-power-sequencer
5 The phosphor-power-sequencer application powers the chassis on/off and monitors
9 application uses information from the power sequencer device to determine the
12 ## Application section in phosphor-power-sequencer
14 The application is a single-threaded C++ executable. It is a 'daemon' process
15 that runs continually. The application is launched by systemd when the BMC
18 The application is driven by an optional, system-specific JSON configuration
28 This application currently supports the following power sequencer device types:
30 - UCD90160
31 - UCD90320
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Application_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Application v1.0.1 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/ |
| H A D | README.md | 19 1. SystemConfiguration: This describes the system-specific parameters.
20 2. EthernetInterface: This describes the interface specific parameters.
21 3. IP: This describes the IP address specific parameters.
23 5. VLANInterface: This describes the VLAN specific properties.
26 ## D-Bus Objects
42 IPv4 objects will have the following D-Bus object path:
46 IPv6 objects will have the following D-Bus object path:
69 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \
70 -d '{
84 curl -c cjar -b cjar -k -H "Content-Type: application/json" -X POST \
[all …]
|
| /openbmc/webui-vue/docs/customization/ |
| H A D | theme.md | 3 Customization of the application requires knowledge of Sass and CSS. It also
4 will require becoming familiar with the Bootstrap and Bootstrap-Vue component
8 ## Environment specific builds
12 application navigation, and theming.
16 ### Configuring environment specific builds
20 [Configuring environment specific builds page](./env.md)
25 these built-in variables is `enabled-*`.
27 ### $enable-rounded
29 This option enables or disables the border-radius styles on various components.
31 - Set to `false` to remove rounded corners on all container elements and buttons
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/config_file/ |
| H A D | README.md | 1 # phosphor-regulators Configuration File
5 - [Overview](#overview)
6 - [Data Format](#data-format)
7 - [Example](#example)
8 - [Name](#name)
9 - [Contents](#contents)
10 - [Validation](#validation)
11 - [Installation](#installation)
12 - [Loading and Reloading](#loading-and-reloading)
13 - [Testing](#testing)
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
| H A D | ThermalMode.interface.yaml | 8 Implementation specific mode for the thermal control application
12 - name: Supported
15 - readonly
17 An implementation specific list of supported modes that the thermal
18 control application can be configured to provide for a platform.
19 - name: Current
23 The current mode the thermal control application should execute in
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details
11 low-level userspace applications, with a new kernel release, the users
12 of sysfs must follow some rules to use an as-abstract-as-possible way to
21 - Do not use libsysfs
23 offer any abstraction, it exposes all the kernel driver-core
31 - sysfs is always at ``/sys``
35 application's behavior, but never try to search for sysfs. Never try
38 - devices are only "devices"
39 There is no such thing like class-, bus-, physical devices,
41 just simply a "device". Class-, bus-, physical, ... types are just
[all …]
|
| /openbmc/linux/Documentation/admin-guide/cgroup-v1/ |
| H A D | net_prio.rst | 9 Nominally, an application would set the priority of its traffic via the
12 1) The application may not have been coded to set this value
13 2) The priority of application traffic is often a site-specific administrative
14 decision rather than an application defined one.
20 # mount -t cgroup -onet_prio none /sys/fs/cgroup/net_prio
26 Each net_prio cgroup contains two files that are subsystem specific
29 This file is read-only, and is simply informative. It contains a unique
52 One usage for the net_prio cgroup is with mqprio qdisc allowing application
|
| /openbmc/qemu/docs/system/arm/ |
| H A D | mps2.rst | 1 …ards (``mps2-an385``, ``mps2-an386``, ``mps2-an500``, ``mps2-an505``, ``mps2-an511``, ``mps2-an521…
4 These board models use Arm M-profile or R-profile CPUs.
16 FPGA images using M-profile CPUs:
18 ``mps2-an385``
19 Cortex-M3 as documented in Arm Application Note AN385
20 ``mps2-an386``
21 Cortex-M4 as documented in Arm Application Note AN386
22 ``mps2-an500``
23 Cortex-M7 as documented in Arm Application Note AN500
24 ``mps2-an505``
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-gnome/recipes-connectivity/geary/geary/ |
| H A D | 0001-application-client.vala-hardcode-some-paths.patch | 2 From: Markus Volk <f_l_k@t-online.de>
4 Subject: [PATCH] application-client.vala: hardcode some paths
7 https://gitlab.gnome.org/GNOME/geary/-/blob/main/src/client/application/application-client.vala?ref…
8 https://gitlab.gnome.org/GNOME/geary/-/blob/main/src/client/application/application-client.vala?ref…
11 WARNING: geary-46.0-r0 do_package_qa: QA Issue: File /usr/lib/geary/libgeary-client-46.0.so in pack…
12 WARNING: geary-46.0-r0 do_package_qa: QA Issue: File /usr/lib/geary/.debug/libgeary-client-46.0.so …
14 Upstream-Status: Inappropriate [oe-specific]
16 Signed-off-by: Markus Volk <f_l_k@t-online.de>
17 ---
18 src/client/application/application-client.vala | 4 ++--
[all …]
|
| /openbmc/linux/arch/mips/include/asm/octeon/ |
| H A D | cvmx-boot-vector.h | 6 * Copyright (C) 2003-2017 Cavium, Inc.
19 * Once cvmx_boot_vector_get() returns a non-NULL value (indicating
24 * be used by the application that has set the target_ptr in any
25 * application specific manner, they are not touched by the vectoring
30 * registers are preserved, except on pre-OCTEON II CPUs, where k1 is
37 * Applications install the boot bus code in cvmx-boot-vector.c, which
45 /* Three application specific arguments. */
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/ |
| H A D | README.md | 12 ### Signed Certificate upload Design flow(Pre-generated)
14 - The REST Server copies the certificate and private key file to a temporary
16 - REST server should map the URI to the target DBus application (Certs) object.
17 The recommendation for the D-Bus application implementing certificate D-Bus
19 - The URI /xyz/openbmc_project/certs/server/https maps to instance of the
20 certificate application handling Https server certificate.
21 - The URI /xyz/openbmc_project/certs/client/ldap maps to instance of the
22 certificate application handling LDAP client certificate.
23 - The URI /xyz/openbmc_project/certs/authority/truststore maps to instance of
24 the certificate application handling Certificate Authority certificates.
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.u-boot_on_efi | 1 # SPDX-License-Identifier: GPL-2.0+
5 U-Boot on EFI
7 This document provides information about U-Boot running on top of EFI, either
8 as an application or just as a means of getting U-Boot onto a new platform.
18 EFI Application
22 32/64-bit
28 ----------
29 Running U-Boot on EFI is useful in several situations:
31 - You have EFI running on a board but U-Boot does not natively support it
32 fully yet. You can boot into U-Boot from EFI and use that until U-Boot is
[all …]
|
| /openbmc/phosphor-rest-server/servers/gevent/ |
| H A D | phosphor-gevent | 3 # Contributors Listed Below - COPYRIGHT 2016
11 # http://www.apache.org/licenses/LICENSE-2.0
16 # implied. See the License for the specific language governing
31 # <wsgi application> REQUIRED Application to import and run (e.g. rest_dbus)
32 # <--no-ssl> OPTIONAL Don't use SSL
35 # by default to all address's at port 443 or 80(--no-ssl)
39 sys.stderr.write('WSGI application required!')
42 if (len(sys.argv) > 2) and (sys.argv[2] == "--no-ssl"):
61 # ECDH - Allow Elliptic Curve Diffie Hellman
62 # kDH - Allow Key Exchange algorithm as Diffie Hellman
[all …]
|
| /openbmc/linux/Documentation/powerpc/ |
| H A D | vas-api.rst | 1 .. SPDX-License-Identifier: GPL-2.0
2 .. _VAS-API:
12 allows both userspace and kernel communicate to co-processor
14 unit comprises of one or more hardware engines or co-processor types
21 Requests to the GZIP engine must be formatted as a co-processor Request
37 Application access to the GZIP engine is provided through
38 /dev/crypto/nx-gzip device node implemented by the VAS/NX device driver.
39 An application must open the /dev/crypto/nx-gzip device to obtain a file
42 engine for this process. Once a connection is established, the application
44 request queue into the application's virtual address space.
[all …]
|
| /openbmc/linux/Documentation/bpf/libbpf/ |
| H A D | libbpf_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 libbpf is a C-based library containing a BPF loader that takes compiled BPF
10 kernel hooks, allowing BPF application developers to focus only on BPF program
13 The following are the high-level features supported by libbpf:
15 * Provides high-level and low-level APIs for user space programs to interact
16 with BPF programs. The low-level APIs wrap all the bpf system call
17 functionality, which is useful when users need more fine-grained control
22 * Provides BPF-side APIS, including BPF helper definitions, BPF maps support,
24 * Supports BPF CO-RE mechanism, enabling BPF developers to write portable
35 A BPF application consists of one or more BPF programs (either cooperating or
[all …]
|