| /openbmc/u-boot/doc/ |
| H A D | README.fsl-hwconfig | 1 Freescale-specific 'hwconfig' options. 3 This file documents Freescale-specific key:value pairs for the 'hwconfig' 7 Specific to the P1022DS reference board. 13 will be programmed accordingly. Second, the clock-frequency property 24 Specific to boards have USB controller 26 This option specifies the following for a USB controller: 28 - which controller mode to use 29 - which USB PHY to use 31 This is used by generic USB device-tree fixup function to update 32 modified values of phy type and controller mode. [all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | StorageControllerMetrics.v1_1_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… 37 …"longDescription": "The object shall contain the NVMe-defined 'Endurance Group Critical Warning Su… 39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 54 …indication of whether namespaces in one or more Endurance Groups are in read-only mode not as a re… 55 …hall indicate whether namespaces in one or more Endurance Groups are in read-only mode not as a re… 63 …ability of one or more Endurance Groups is degraded due to significant media-related errors or any… [all …]
|
| H A D | MediaController.v1_3_2.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_]*$": { 31 "description": "The available OEM-specific actions for this resource.", 32 …"longDescription": "This property shall contain the available OEM-specific actions for this resour… 40 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha… 42 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 57 … "description": "An array of links to the endpoints that connect to this media controller.", 61 …an array of links to resources of type `Endpoint` with which this media controller is associated.", 66 "$ref": "http://redfish.dmtf.org/schemas/v1/odata-v4.json#/definitions/count" [all …]
|
| H A D | USBController.v1_0_1.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… 37 …"longDescription": "This Redfish Specification-described type shall contain links to resources tha… 39 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 56 …operties contained in this object shall conform to the Redfish Specification-described requirement… 60 "description": "A link to the PCIe device that represents this USB controller.", 61 …erty shall contain a link to a resource of type `PCIeDevice` that represents this USB controller.", [all …]
|
| H A D | GraphicsController.v1_0_2.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… 36 …"description": "The `GraphicsController` schema defines a graphics controller that can be used to … 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" [all …]
|
| H A D | StorageController.v1_10_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… 16 …essed by a controller that reports this state for an ANA group provide non-optimized access charac… 17 …"Optimized": "Commands processed by a controller provide optimized access to any namespace in the … 24 … "description": "The ANA characteristics and volume information for a storage controller.", 25 …"This type shall contain the ANA characteristics and volume information for a storage controller.", 27 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 68 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 96 "description": "The available OEM-specific actions for this resource.", 97 …"longDescription": "This property shall contain the available OEM-specific actions for this resour… [all …]
|
| /openbmc/u-boot/include/ |
| H A D | nvme.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */ 13 * nvme_identify - identify controller or namespace capabilities and status 15 * This issues an identify command to the NVMe controller to return a data 16 * buffer that describes the controller or namespace capabilities and status. 18 * @dev: NVMe controller device 19 * @nsid: 0 for controller, namespace id for namespace to identify 20 * @cns: 1 for controller, 0 for namespace 22 * @return: 0 on success, -ETIMEDOUT on command execution timeout, 23 * -EIO on command execution fails 29 * nvme_get_features - retrieve the attributes of the feature specified [all …]
|
| /openbmc/u-boot/drivers/mmc/ |
| H A D | Kconfig | 1 menu "MMC Host controller Support" 12 also to your specific host controller driver. 31 Secure Digital I/O (SDIO) cards. Both removable (SD, micro-SD, etc.) 32 and non-removable (e.g. eMMC chip) devices are supported. These 33 appear as block devices in U-Boot and can support filesystems such 42 Secure Digital I/O (SDIO) cards. Both removable (SD, micro-SD, etc.) 43 and non-removable (e.g. eMMC chip) devices are supported. These 44 appear as block devices in U-Boot and can support filesystems such 161 you are reading this help text, you most likely have no idea :-) 188 bool "Exynos specific extensions for Synopsys DW Memory Card Interface" [all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | StorageControllerMetrics_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 <!----> 3 <!--################################################################################ … 4 <!--# Redfish Schema: StorageControllerMetrics v1.1.0 … 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-2025 DMTF in cooperation with Storage Networking Industry Association (SNIA). … 9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright … 10 <!--################################################################################ … [all …]
|
| H A D | GraphicsController_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 <!----> 3 <!--################################################################################ --> 4 <!--# Redfish Schema: GraphicsController v1.0.2 --> 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-2025 DMTF. --> 9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright --> 10 <!--################################################################################ --> [all …]
|
| H A D | USBController_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 <!----> 3 <!--################################################################################ --> 4 <!--# Redfish Schema: USBController 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-2025 DMTF. --> 9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright --> 10 <!--################################################################################ --> [all …]
|
| H A D | MediaController_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?> 2 <!----> 3 <!--################################################################################ --> 4 <!--# Redfish Schema: MediaController v1.3.2 --> 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-2025 DMTF. --> 9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright --> 10 <!--################################################################################ --> [all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/gpio/ |
| H A D | gpio.txt | 5 ----------------- 8 properties, each containing a 'gpio-list': 10 gpio-list ::= <single-gpio> [gpio-list] 11 single-gpio ::= <gpio-phandle> <gpio-specifier> 12 gpio-phandle : phandle to gpio controller node 13 gpio-specifier : Array of #gpio-cells specifying specific gpio 14 (controller specific) 16 GPIO properties should be named "[<name>-]gpios", with <name> being the purpose 17 of this GPIO for the device. While a non-existent <name> is considered valid 31 and bit-banged data signals: [all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | StorageController.v1_10_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… 16 …essed by a controller that reports this state for an ANA group provide non-optimized access charac… 17 …"Optimized": "Commands processed by a controller provide optimized access to any namespace in the … 24 … "description": "The ANA characteristics and volume information for a storage controller.", 25 …"This type shall contain the ANA characteristics and volume information for a storage controller.", 27 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 68 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": { 96 "description": "The available OEM-specific actions for this resource.", 97 …"longDescription": "This property shall contain the available OEM-specific actions for this resour… [all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/nand/ |
| H A D | nvidia,tegra20-nand.txt | 2 ---------- 5 U-Boot. There should not be Linux-specific or U-Boot specific binding, just 12 - compatible : Should be "manufacturer,device", "nand-flash" 14 This node should sit inside its controller. 17 Nvidia NAND Controller 18 ---------------------- 20 The device node for a NAND flash controller is as follows: 24 nvidia,wp-gpios : GPIO of write-protect line, three cells in the format: 26 nvidia,nand-width : bus width of the NAND device in bits 28 - nvidia,nand-timing : Timing parameters for the NAND. Each is in ns. [all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/pinctrl/ |
| H A D | rockchip,pinctrl.txt | 1 * Rockchip Pinmux Controller 3 The Rockchip Pinmux Controller, enables the IC 8 Please refer to pinctrl-bindings.txt in this directory for details of the 13 used for a specific device or function. This node represents both mux and 16 settings such as pull-up, etc. 19 defined as gpio sub-nodes of the pinmux controller. 21 Required properties for iomux controller: 22 - compatible: one of "rockchip,rk2928-pinctrl", "rockchip,rk3066a-pinctrl" 23 "rockchip,rk3066b-pinctrl", "rockchip,rk3188-pinctrl" 24 "rockchip,rk3288-pinctrl" [all …]
|
| H A D | pinctrl-bindings.txt | 4 such as pull-up/down, tri-state, drive-strength etc are designated as pin 5 controllers. Each pin controller must be represented as a node in device tree, 13 set up certain specific pin configurations. Some client devices need a 15 need to reconfigure pins at run-time, for example to tri-state pins when the 25 For example, a pin controller may set up its own "active" state when the 31 they require certain specific named states for dynamic pin configuration. 47 pinctrl-0: List of phandles, each pointing at a pin configuration 49 nodes of the pin controller that they configure. Multiple 52 from multiple nodes for a single pin controller, each 59 used in an SoC either without a pin controller, or where the [all …]
|
| /openbmc/libcper/sections/ |
| H A D | cper-section-pcie.c | 12 #include <libcper/cper-utils.h> 13 #include <libcper/sections/cper-section-pcie.h> 23 // Base Class 00h - Legacy devices 25 "All currently implemented devices except VGA-compatible devices" }, 26 { 0x00, 0x01, 0x00, "VGA-compatible device" }, 28 // Base Class 01h - Mass storage controllers 29 { 0x01, 0x00, 0x00, "SCSI controller - vendor-specific interface" }, 31 "SCSI storage device - SCSI over PCI Express (SOP) with PQI" }, 33 "SCSI controller - SCSI over PCI Express (SOP) with PQI" }, 35 "SCSI storage device and SCSI controller - SOP with PQI" }, [all …]
|
| /openbmc/u-boot/arch/arm/mach-at91/include/mach/ |
| H A D | at91sam9x5.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */ 3 * Chip-specific header file for the AT91SAM9x5 family 5 * Copyright (C) 2012-2013 Atmel Corporation. 17 #define ATMEL_ID_FIQ 0 /* Advanced Interrupt Controller (FIQ) */ 18 #define ATMEL_ID_SYS 1 /* System Controller Interrupt */ 19 #define ATMEL_ID_PIOAB 2 /* Parallel I/O Controller A and B */ 20 #define ATMEL_ID_PIOCD 3 /* Parallel I/O Controller C and D */ 22 #define ATMEL_ID_FUSE 4 /* FUSE Controller, only for AT91SAM9N12 */ 27 #define ATMEL_ID_TWI0 9 /* Two-Wire Interface 0 */ 28 #define ATMEL_ID_TWI1 10 /* Two-Wire Interface 1 */ [all …]
|
| H A D | sama5d3.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */ 3 * Chip-specific header file for the SAMA5D3 family 5 * (C) 2012 - 2013 Atmel Corporation. 18 #define ATMEL_ID_FIQ 0 /* Advanced Interrupt Controller (FIQ) */ 19 #define ATMEL_ID_SYS 1 /* System Controller Interrupt */ 23 #define ATMEL_ID_SMC 5 /* Multi-bit ECC Interrupt */ 24 #define ATMEL_ID_PIOA 6 /* Parallel I/O Controller A */ 25 #define ATMEL_ID_PIOB 7 /* Parallel I/O Controller B */ 26 #define ATMEL_ID_PIOC 8 /* Parallel I/O Controller C */ 27 #define ATMEL_ID_PIOD 9 /* Parallel I/O Controller D */ [all …]
|
| /openbmc/u-boot/doc/device-tree-bindings/remoteproc/ |
| H A D | k3-system-controller.txt | 1 Texas Instruments' K3 System Controller 4 K3 specific SoCs have a dedicated microcontroller for doing 10 -------------------- 11 - compatible: Shall be: "ti,am654-system-controller" 12 - mbox-names: "tx" for Transfer channel 14 - mboxes: Corresponding phandles to mailbox channels. 18 -------- 20 system-controller: system-controller { 21 compatible = "ti,am654-system-controller"; 23 mbox-names = "tx", "rx";
|
| /openbmc/u-boot/arch/arm/mach-omap2/omap3/ |
| H A D | Kconfig | 52 bool "CompuLab CM-T3530 and CM-T3730 boards" 58 bool "CompuLab CM-T3517 boards" 178 prompt "Memory Controller" 182 bool "SDRC controller" 184 The default memory controller on most OMAP3 boards is SDRC. 187 bool "EMIF4 controller" 189 Enable this on boards like AM3517 which use EMIF4 controller 193 bool "Support OMAP3-specific ID and MFR function" 195 Support for an OMAP3-specific set of functions to return the
|
| /openbmc/u-boot/drivers/usb/gadget/ |
| H A D | Kconfig | 3 # (a) a peripheral controller, and 6 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !! 8 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks). 9 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks). 10 # - Some systems have both kinds of controllers. 12 # With help from a special transceiver and a "Mini-AB" jack, systems with 13 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG). 22 you can't connect a "to-the-host" connector to a peripheral. 24 U-Boot can run in the host, or in the peripheral. In both cases 25 you need a low level bus controller driver, and some software [all …]
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_mc_id.robot | 3 Documentation Module to test IPMI management controller ID functionality. 19 Verify Get And Set Management Controller ID String 20 [Documentation] Verify get and set management controller ID string. 22 # Get the value of the managemment controller ID string. 24 # Get Management Controller Identifier String: witherspoon 29 # Extract management controller ID from cmd_output. 32 # Set the management controller ID string to other value. 34 # Set Management Controller Identifier String Command: HOST 36 Set Management Controller ID String ${new_mc_id} 38 # Get the management controller ID and verify. [all …]
|
| /openbmc/u-boot/arch/arm/mach-aspeed/ |
| H A D | Kconfig | 21 The Aspeed AST2400 is a ARM-based SoC with arm926ejs CPU. 22 It is used as Board Management Controller on many server boards, 30 The Aspeed AST2500 is a ARM-based SoC with arm1176 CPU. 31 It is used as Board Management Controller on many server boards, 43 The Aspeed AST2600 is a ARM-based SoC with Cortex-A7 CPU. 44 It is used as Board Management Controller on many server boards, 54 absolutely required for a specific system or for debugging 60 bool "Enable built-in AST2x00 Super I/O hardware" 63 The Aspeed AST2400 and AST2500 include a built-in Super I/O 69 specific system. [all …]
|