| /openbmc/u-boot/doc/device-tree-bindings/leds/ |
| H A D | leds-bcm6358.txt | 5 which can either be controlled by software (exporting the 74x164 as spi-gpio.
6 See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 - compatible : should be "brcm,bcm6358-leds".
11 - #address-cells : must be 1.
12 - #size-cells : must be 0.
13 - reg : BCM6358 LED controller address and size.
16 - brcm,clk-div : SCK signal divider. Possible values are 1, 2, 4 and 8.
18 - brcm,clk-dat-low : Boolean, makes clock and data signals active low.
21 Each LED is represented as a sub-node of the brcm,bcm6358-leds device.
23 LED sub-node required properties:
[all …]
|
| H A D | leds-bcm6328.txt | 7 as spi-gpio. See Documentation/devicetree/bindings/gpio/gpio-74x164.txt), or
10 exporting the 74x164 as spi-gpio prevents those LEDs to be hardware
14 - compatible : should be "brcm,bcm6328-leds".
15 - #address-cells : must be 1.
16 - #size-cells : must be 0.
17 - reg : BCM6328 LED controller address and size.
20 - brcm,serial-leds : Boolean, enables Serial LEDs.
22 - brcm,serial-mux : Boolean, enables Serial LEDs multiplexing.
24 - brcm,serial-clk-low : Boolean, makes clock signal active low.
26 - brcm,serial-dat-low : Boolean, makes data signal active low.
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-fbdarwin/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | host-powercycle | 3 set -x
6 # BMC_SYS_PWR_CYC0 (connects to CPLD and control the whole system power cycling) -> Maps to GPIOO0
7 # BMC_SYS_PWR_CYC1 (to power cycle CPU through CPLD) -> Maps to GPIOO2
8 # Mapping sourced from: meta-facebook/meta-fbdarwin/recipes-utils/openbmc-utils/files/setup-gpio.sh
13 # Sourced from the fbdarwin image with: gpiocli --chip aspeed-gpio --pin-name GPIOO2 map-name-to-of…
17 LOW=0
22 echo "GPIO Reset pin - drive-high failed"
27 # The GPIO must be driven low before a subsequent reset can be issued
28 gpioset "$ASPEED_CHIP" "$BMC_SYS_PWR_CYC1_OFFSET=$LOW"
30 echo "Reset pin driven low."
|
| H A D | chassis-powercycle | 3 set -x
5 # BMC_SYS_PWR_CYC0 (connects to CPLD and control the whole system power cycling) -> Maps to GPIOO0
10 # Sourced from the fbdarwin image with: gpiocli --chip aspeed-gpio --pin-name GPIOO0 map-name-to-of…
14 LOW=0
20 mount -o ro,remount /run/mnt-persist
23 # Drive the pin HIGH, triggering the chassis power cycle
29 # If it does, it means something is wrong -_-
30 echo "ERROR: unable to power cycle chassis!!!"
31 gpioset "$ASPEED_CHIP" "$BMC_SYS_PWR_CYC0_OFFSET=$LOW"
|
| /openbmc/docs/designs/ |
| H A D | device-tree-gpio-naming.md | 12 subsystem. The replacement is a "descriptor-based" character device interface.
25 specific field used to name the GPIOs in the DTS is `gpio-line-names`. This
29 scheme in the face of a universe of potential use-cases.
37 - Ensure common function GPIOs within OpenBMC use the same naming convention
52 Pattern: `*-button`
55 BMC-less machines use a button to trigger system behavior and in a BMC-managed
59 #### power-button
64 depends on the index of Host and the active state is high or low.
68 - `host*-ready`: Host ready, active high
69 - `host*-ready-n`: Host ready, active low
[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 …]
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | message_registry.json | 378 "SyslogID": "phosphor-log-manager",
429 "SyslogID": "phosphor-log-manager",
618 "Description": "Failure occurred during PHAL pre-poweroff operations",
619 "Message": "Failure occurred during PHAL pre-poweroff operations",
699 "Description": "Failure re-initializing BMC to Host data structure",
700 "Message": "Failure occurred during re-initializing BMC to Host data structure",
774 "Priority": "low",
775 "LocCode": "P0-C15"
787 "Priority": "low",
788 "LocCode": "P0-C61"
[all …]
|
| /openbmc/u-boot/arch/mips/dts/ |
| H A D | netgear,cg3100d.dts | 1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
19 stdout-path = "serial0:115200n8";
22 gpio-leds {
23 compatible = "gpio-leds";
36 label = "CG3100D:red:power";
47 active-low;
48 label = "CG3100D:green:power";
53 active-low;
59 active-low;
[all …]
|
| H A D | netgear,dgnd3700v2.dts | 1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
19 stdout-path = "serial0:115200n8";
22 gpio-leds {
23 compatible = "gpio-leds";
36 label = "DGND3700v2:red:power";
50 compatible = "brcm,enetsw-port";
53 brcm,phy-id = <0xff>;
55 full-duplex;
56 bypass-link;
[all …]
|
| H A D | comtrend,ar-5315u.dts | 1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
11 model = "Comtrend AR-5315u";
12 compatible = "comtrend,ar5315-un", "brcm,bcm6318";
19 stdout-path = "serial0:115200n8";
31 compatible = "brcm,enetsw-port";
34 brcm,phy-id = <1>;
38 compatible = "brcm,enetsw-port";
41 brcm,phy-id = <2>;
45 compatible = "brcm,enetsw-port";
[all …]
|
| H A D | comtrend,vr-3032u.dts | 1 // SPDX-License-Identifier: GPL-2.0+
6 /dts-v1/;
11 model = "Comtrend VR-3032u";
12 compatible = "comtrend,vr-3032u", "brcm,bcm63268";
19 stdout-path = "serial0:115200n8";
31 compatible = "brcm,enetsw-port";
34 brcm,phy-id = <1>;
38 compatible = "brcm,enetsw-port";
41 brcm,phy-id = <2>;
45 compatible = "brcm,enetsw-port";
[all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
| H A D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin
15 need to reconfigure pins at run-time, for example to tri-state pins when the
47 pinctrl-0: List of phandles, each pointing at a pin configuration
65 pinctrl-1: List of phandles, each pointing at a pin configuration
68 pinctrl-n: List of phandles, each pointing at a pin configuration
70 pinctrl-names: The list of names to assign states. List entry 0 defines the
78 pinctrl-names = "active", "idle";
79 pinctrl-0 = <&state_0_node_a>;
80 pinctrl-1 = <&state_1_node_a &state_1_node_b>;
85 pinctrl-0 = <&state_0_node_a>;
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Item/ |
| H A D | Dimm.interface.yaml | 4 - name: MemoryDataWidth
8 - name: MemorySizeInKB
12 - name: MemoryDeviceLocator
16 - name: MemoryType
20 - name: MemoryTypeDetail
24 - name: MaxMemorySpeedInMhz
28 - name: MemoryAttributes
33 - name: MemoryConfiguredSpeedInMhz
37 - name: ECC
40 Error-Correcting Code.
[all …]
|
| /openbmc/u-boot/drivers/video/ |
| H A D | am335x-fb.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * Copyright (C) 2013-2018 Hannes Schmelzer <oe5hpm@oevsv.at> -
4 * B&R Industrial Automation GmbH - http://www.br-automation.com
29 * 0 = DE is low-active
30 * 1 = DE is high-active
33 * 0 = pix-clk is high-active
34 * 1 = pic-clk is low-active
38 * 1 = HSYNC is avtive low
42 * 1 = VSYNC is active low
58 * time in ms after power on to
[all …]
|
| /openbmc/bmcweb/redfish-core/include/generated/enums/ |
| H A D | log_entry.hpp | 1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
8 // clang-format off
183 {LogEntryCode::LowerNoncriticalgoinglow, "Lower Non-critical - going low"},
184 {LogEntryCode::LowerNoncriticalgoinghigh, "Lower Non-critical - going high"},
185 {LogEntryCode::LowerCriticalgoinglow, "Lower Critical - going low"},
186 {LogEntryCode::LowerCriticalgoinghigh, "Lower Critical - going high"},
187 {LogEntryCode::LowerNonrecoverablegoinglow, "Lower Non-recoverable - going low"},
188 {LogEntryCode::LowerNonrecoverablegoinghigh, "Lower Non-recoverable - going high"},
189 {LogEntryCode::UpperNoncriticalgoinglow, "Upper Non-critical - going low"},
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-jade/recipes-ampere/platform/ampere-platform-init/ |
| H A D | ampere_platform_init.sh | 4 # shellcheck source=meta-ampere/meta-jade/recipes-ampere/platform/ampere-platform-init/mtjade_platf…
8 pre-platform-init
14 echo "CONFIGURE: gpio pins to output high after AC power"
18 echo "CONFIGURE: gpio pins to output low after AC power"
22 echo "CONFIGURE: gpio pins to input after AC power"
34 echo "CONFIGURE: gpio pins to output low"
44 post-platform-init
|
| /openbmc/bmcweb/redfish-core/include/registries/ |
| H A D | openbmc_message_registry.hpp | 1 // SPDX-License-Identifier: Apache-2.0
2 // SPDX-FileCopyrightText: Copyright OpenBMC Authors
6 * This is an auto-generated header which contains definitions
18 // clang-format off
38 …"https://raw.githubusercontent.com/openbmc/bmcweb/refs/heads/master/redfish-core/include/registrie…
60 "Indicates At-Scale Debug connection has been established",
61 "At-Scale Debug service is now connected %1",
72 "Indicates At-Scale Debug connection aborted/failed",
73 "At-Scale Debug connection aborted/failed",
82 "Indicates At-Scale Debug connection has ended",
[all …]
|
| H A D | openbmc.json | 18 "Description": "Indicates At-Scale Debug connection has been established",
19 "Message": "At-Scale Debug service is now connected %1",
27 "Description": "Indicates At-Scale Debug connection aborted/failed",
28 "Message": "At-Scale Debug connection aborted/failed",
35 "Description": "Indicates At-Scale Debug connection has ended",
36 "Message": "At-Scale Debug service is now disconnected",
43 "Description": "Indicates that At-Scale Debug service is stopped.",
44 "Message": "At-Scale Debug service is stopped.",
51 "Description": "Indicates that At-Scale Debug disable is detected in hardware.",
52 "Message": "At-Scale Debug Feature is disabled in hardware.",
[all …]
|
| /openbmc/openbmc/meta-ampere/meta-mitchell/recipes-ampere/platform/ampere-platform-init/ |
| H A D | ampere_platform_init.sh | 4 # shellcheck source=meta-ampere/meta-mitchell/recipes-ampere/platform/ampere-platform-init/mtmitche…
5 # shellcheck source=meta-ampere/meta-common/recipes-ampere/platform/ampere-utils/utils-lib.sh
7 source /usr/sbin/utils-lib.sh
9 function socket-based-fan-conf-update() {
10 echo "Checking phosphor-fan configurations based on CPU 1 presence..."
11 …fanControlConfDir="/usr/share/phosphor-fan-presence/control/com.ampere.Hardware.Chassis.Model.MtMi…
24 if [ -f "$fanControlConfDir/$refConf" ]; then
36 board_id=$(i2cget -y -a 0 0x20 0x0 b)
57 # P0[7] -> GPI[1] and P0[6] -> GPI[0]
60 if [[ $md_id_7_6_5_4 -gt 8 ]]; then
[all …]
|
| /openbmc/skeleton/libopenbmc_intf/ |
| H A D | gpio_configs.c | 9 * http://www.apache.org/licenses/LICENSE-2.0
29 * Loads the GPIO information into the gpios->power_gpio structure
32 * @param gpios - the structure where GpioConfigs.power_gpio will
34 * @param gpio_configs - cJSON pointer to the GPIO JSON
44 /* PGOOD - required */ in read_power_gpios()
49 gpios->power_gpio.power_good_in.name = g_strdup(pgood->valuestring); in read_power_gpios()
51 g_print("Power GPIO power good input: %s\n", in read_power_gpios()
52 gpios->power_gpio.power_good_in.name); in read_power_gpios()
54 /* Latch out - optional */ in read_power_gpios()
59 gpios->power_gpio.latch_out.name = g_strdup(latch->valuestring); in read_power_gpios()
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.VSC3316-3308 | 2 Vitesse cross-point devices, VSC3316 and VSC3308 for board B4860QDS
8 VSC 3316/3308 is a low-power, low-cost asynchronous crosspoint switch capable of data rates upto 11…
10 …and 8 output ports. Programming of these devices are performed by two-wire or four-wire serial int…
14 On reset, VSC devices are in low-power state with all inputs, outputs and connections in an off sta…
15 First thing required is to program it to interface with either two-wire or four-wire interface.
16 …he interface is two-wire I2C serial interface. So the value in Interface mode register at address …
22 --------------------------
23 …-wire or four-wire interface. In our case the interface is two-wire I2C serial interface. So the v…
25 vsc_addr - Address of the VSC device on board.
29 ---------------------------------------------------------
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | LogEntry.v1_19_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 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…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
68 …operties contained in this object shall conform to the Redfish Specification-described requirement…
74 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
118 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | LogEntry.v1_19_0.json | 4 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
5 …"copyright": "Copyright 2014-2025 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…
40 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
57 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
68 …operties contained in this object shall conform to the Redfish Specification-described requirement…
74 … "pattern": "^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$",
118 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha…
[all …]
|
| /openbmc/phosphor-power/phosphor-power-supply/ |
| H A D | util.hpp | 7 #include <phosphor-logging/elog-errors.hpp>
8 #include <phosphor-logging/elog.hpp>
9 #include <phosphor-logging/lg2.hpp>
15 namespace phosphor::power::psu namespace
68 auto invService = phosphor::power::util::getService( in setPresence()
101 auto invService = phosphor::power::util::getService( in setAvailable()
130 auto service = phosphor::power::util::getService( in handleChassisHealthRollup()
134 phosphor::power::util::getProperty<AssociationsProperty>( in handleChassisHealthRollup()
164 phosphor::power::util::getProperty<bool>( in handleChassisHealthRollup()
176 phosphor::power::util::setProperty(ASSOC_DEF_IFACE, ASSOC_PROP, in handleChassisHealthRollup()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/Power/ |
| H A D | Mode.interface.yaml | 2 Customer requested system power mode.
5 - name: PowerMode
9 This property shall contain the computer system power mode setting.
10 This defines the processor speed based on the priority of power
13 - xyz.openbmc_project.Common.Error.InvalidArgument
14 - xyz.openbmc_project.Common.Error.NotAllowed
16 - name: SafeMode
19 - readonly
23 this is true, the system power mode is not being used in the system.
25 - name: AllowedPowerModes
[all …]
|