| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
| H A D | EthernetInterface.v1_12_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…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
51 "type": "string" string
55 "description": "DHCPv4 configuration for this interface.",
[all …]
|
| H A D | IPAddresses.v1_1_5.json | 3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
14 …ddress is currently within its valid lifetime but is now outside its RFC4862-defined preferred lif…
16 …"Preferred": "This address is currently within both its RFC4862-defined valid and preferred lifeti…
19 "type": "string" string
23 "description": "This type describes an IPv4 address.",
24 "longDescription": "This type shall describe an IPv4 address assigned to an interface.",
26 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "type": [ array
42 …ain an IPv4 address assigned to this interface. If DHCPv4 is enabled on the interface, this prope…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
| H A D | EthernetInterface.v1_12_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…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
51 "type": "string" string
55 "description": "DHCPv4 configuration for this interface.",
[all …]
|
| H A D | HostInterface.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…
10 "longDescription": "This type shall contain the available actions for this resource.",
12 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
14 "type": [ array
28 "description": "The available OEM-specific actions for this resource.",
29 …"longDescription": "This property shall contain the available OEM-specific actions for this resour…
33 "type": "object" string
48 "type": "string" string
52 "description": "The credential bootstrapping settings for this interface.",
[all …]
|
| H A D | IPAddresses.v1_1_5.json | 3 "$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
4 …"copyright": "Copyright 2014-2024 DMTF. For the full DMTF copyright policy, see http://www.dmtf.or…
14 …ddress is currently within its valid lifetime but is now outside its RFC4862-defined preferred lif…
16 …"Preferred": "This address is currently within both its RFC4862-defined valid and preferred lifeti…
19 "type": "string" string
23 "description": "This type describes an IPv4 address.",
24 "longDescription": "This type shall describe an IPv4 address assigned to an interface.",
26 "^([a-zA-Z_][a-zA-Z0-9_]*)?@(odata|Redfish|Message)\\.[a-zA-Z_][a-zA-Z0-9_]*$": {
28 "type": [ array
42 …ain an IPv4 address assigned to this interface. If DHCPv4 is enabled on the interface, this prope…
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/fans/phosphor-fan-control-events-config/witherspoon/ |
| H A D | events.yaml | 2 - name: poweron_pgood
4 type: /org/openbmc/control
6 - /power0
7 - name: zone0_control_mode
10 type: /xyz/openbmc_project/control/thermal
12 - /0
13 - name: air_cooled_zone0_fans
15 type: /xyz/openbmc_project/inventory
17 - /system/chassis/motherboard/fan0
18 - /system/chassis/motherboard/fan1
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Network/ |
| H A D | EthernetInterface.interface.yaml | 2 This defines an ethernet interface. An object implementing this interface
6 - name: InterfaceName
7 type: string
9 - const
11 Name of the ethernet interface.
12 - name: Speed
13 type: uint32
15 - readonly
17 Current speed of the ethernet interface, in Mbps.
18 - name: AutoNeg
[all …]
|
| H A D | README.md | 6 must implement the `xyz.openbmc_project.Network.SystemConfiguration.interface`
15 interface object.
19 1. SystemConfiguration: This describes the system-specific parameters.
20 2. EthernetInterface: This describes the interface specific parameters.
22 4. IPProtocol: This describes the IP protocol type(IPv4/IPv6).
24 6. Bond: This describes the interface bonding parameters.
26 ## D-Bus Objects
28 ### Interface Objects
30 Interface objects can be physical as well as virtual.
32 If the object is a physical interface, it can't be deleted, but if it is a
[all …]
|
| /openbmc/qemu/ui/ |
| H A D | dbus-display1.xml | 1 <?xml version="1.0" encoding="utf-8"?>
3 <!--
6 This interface is implemented on ``/org/qemu/Display1/VM``.
7 -->
8 <interface name="org.qemu.Display1.VM">
9 <!--
13 -->
14 <property name="Name" type="s" access="read"/>
16 <!--
20 -->
[all …]
|
| /openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/fans/phosphor-fan-control-events-config/ |
| H A D | events.yaml | 2 - name: air_cooled_zone0_fans
4 type: /xyz/openbmc_project/inventory
6 - /system/chassis/motherboard/fan0
7 - /system/chassis/motherboard/fan1
8 - /system/chassis/motherboard/fan2
9 - name: zone0_ambient
11 type: /xyz/openbmc_project/sensors
13 - /temperature/outlet
14 - name: occ0_object
16 type: /org/open_power/control
[all …]
|
| /openbmc/phosphor-fan-presence/control/example/ |
| H A D | events.yaml | 1 #Example set speed events for phosphor-fan-control
4 # - name: [A unique name for this group]
6 # type: [The '/xyz/openbmc_project' path extension]
11 # - name: [The name associated with a supported match string function]
17 # - name: [The name associated with a supported signal function]
24 # - name: [The name associated with a supported method function]
30 # - name: [The name associated with a supported handler function]
37 # - name: [Name associated with an available precondition function]
43 # - name: [Name associated with an available action function]
49 # - name: [A unique name for this event]
[all …]
|
| H A D | zone_conditions.yaml | 1 #Example zone conditions for phosphor-fan-control
4 # - name: [A unique name for this condition.]
5 # type: [The type of condition. Currently, the only supported type is
8 # - property: [The Dbus property name on the interface.]
9 # interface: [The Dbus interface that contains the property.]
10 # path: [The Dbus path where the interface is located.]
11 # type: [The property type for this property.]
16 # - name: air_cooled_chassis
17 # type: getProperty
19 # - property: WaterCooled
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | blk.h | 1 /* SPDX-License-Identifier: GPL-2.0+ */
3 * (C) Copyright 2000-2004
22 /* Interface types: */
38 IF_TYPE_COUNT, /* Number of interface types */
46 * Identifies the partition table type (ie. MBR vs GPT GUID) signature
65 enum if_type if_type; /* type of the interface */
67 unsigned char part_type; /* partition type */
71 unsigned char type; /* device type */ member
83 enum sig_type sig_type; /* Partition table signature type */
111 #define BLOCK_CNT(size, blk_desc) (PAD_COUNT(size, blk_desc->blksz))
[all …]
|
| /openbmc/linux/drivers/usb/typec/ucsi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
4 tristate "USB Type-C Connector System Software Interface driver"
9 USB Type-C Connector System Software Interface (UCSI) is a
10 specification for an interface that allows the operating system to
11 control the USB Type-C ports. On UCSI system the USB Type-C ports
15 that are equipped with Embedded Controller and USB Type-C ports.
17 UCSI specification does not define the interface method, so depending
20 for every supported interface method.
23 https://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.html
31 tristate "UCSI Interface Driver for Cypress CCGx"
[all …]
|
| /openbmc/openbmc/meta-raspberrypi/recipes-graphics/userland/files/ |
| H A D | 0012-implement-buffer-wrapping-interface-for-dispmanx.patch | 3 Date: Sat, 2 Apr 2016 10:54:59 -0700
4 Subject: [PATCH] implement buffer wrapping interface for dispmanx
8 Signed-off-by: Khem Raj <raj.khem@gmail.com>
9 ---
10 Upstream-Status: Pending
12 interface/khronos/ext/egl_wayland.c | 42 +++++++++++++++++++++++++++++
13 interface/wayland/dispmanx.xml | 10 +++++++
16 diff --git a/interface/khronos/ext/egl_wayland.c b/interface/khronos/ext/egl_wayland.c
18 --- a/interface/khronos/ext/egl_wayland.c
19 +++ b/interface/khronos/ext/egl_wayland.c
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/fsl/cpm_qe/ |
| H A D | network.txt | 4 - fsl,cpm1-scc-enet
5 - fsl,cpm2-scc-enet
6 - fsl,cpm1-fec-enet
7 - fsl,cpm2-fcc-enet (third resource is GFEMR)
8 - fsl,qe-enet
13 compatible = "fsl,mpc8272-fcc-enet",
14 "fsl,cpm2-fcc-enet";
16 local-mac-address = [ 00 00 00 00 00 00 ];
18 interrupt-parent = <&PIC>;
19 phy-handle = <&PHY0>;
[all …]
|
| /openbmc/linux/Documentation/networking/ |
| H A D | net_failover.rst | 1 .. SPDX-License-Identifier: GPL-2.0
16 original paravirtual interface is registered as 'standby' slave netdev and
19 'pci' device. The user accesses the network interface via 'failover' netdev.
28 virtio-net accelerated datapath: STANDBY mode
31 net_failover enables hypervisor controlled accelerated datapath to virtio-net
35 feature on the virtio-net interface and assign the same MAC address to both
36 virtio-net and VF interfaces.
41 <interface type='network'>
45 <model type='virtio'/>
48 <teaming type='persistent'/>
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | HostInterface_v1.xml | 1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: HostInterface 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-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/settings/phosphor-settings-defaults/ |
| H A D | host-template.yaml | 2 - Interface: xyz.openbmc_project.Control.Boot.RebootPolicy
8 - Interface: xyz.openbmc_project.Control.Boot.RebootPolicy
14 - Interface: xyz.openbmc_project.Control.Boot.Source
18 - Interface: xyz.openbmc_project.Control.Boot.Mode
22 - Interface: xyz.openbmc_project.Control.Boot.Type
25 Default: Type::Types::EFI
26 - Interface: xyz.openbmc_project.Object.Enable
32 - Interface: xyz.openbmc_project.Object.Enable
38 - Interface: xyz.openbmc_project.Control.Power.Cap
43 Type: "range"
[all …]
|
| /openbmc/sdbusplus/docs/yaml/ |
| H A D | interface.md | 1 # Interface YAML
3 D-Bus interfaces can be defined by creating a YAML file to describe the methods,
9 An interface YAML may have the following sections:
11 - description
12 - A small documentation section describing the purpose of the interface.
13 - methods
14 - A list of methods provided by this D-Bus interface.
15 - properties
16 - A list of properties provided by this D-Bus interface.
17 - signals
[all …]
|
| /openbmc/linux/Documentation/networking/dsa/ |
| H A D | configuration.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 .. _dsa-config-showcases:
13 -----------------------
33 interface. The CPU port is the switch port connected to an Ethernet MAC chip.
34 The corresponding linux Ethernet interface is called the master interface.
37 The slave interfaces depend on the master interface being up in order for them
39 interface had to be managed explicitly by the user. Starting with kernel v5.12,
42 - when a DSA slave interface is brought up, the master interface is
44 - when the master interface is brought down, all DSA slave interfaces are
50 the master interface
[all …]
|
| /openbmc/phosphor-networkd/docs/ |
| H A D | Network-Configuration.md | 6 must implement the `xyz.openbmc_project.Network.SystemConfiguration.interface`
15 interface object.
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.
22 4. IPProtocol: This describes the IP protocol type (IPv4/IPv6).
23 5. VLANInterface: This describes the VLAN-specific properties.
24 6. Bond: This describes the interface bonding parameters.
28 ### Interface Objects
30 Interface objects can be physical as well as virtual.
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/settings/phosphor-settings-manager/ |
| H A D | HypervisorInterface-default-p10bmc.override.yml | 2 - Interface: xyz.openbmc_project.Network.SystemConfiguration
8 - Interface: xyz.openbmc_project.Network.MACAddress
13 Type: "regex"
14 Validator: '^([0-9A-Fa-f]{2}[:-]){5}([0-9A-Fa-f]{2})$'
15 - Interface: xyz.openbmc_project.Network.EthernetInterface
21 - Interface: xyz.openbmc_project.Network.IP
28 Type: "range"
33 Type:
35 - Interface: xyz.openbmc_project.Object.Enable
41 - Interface: xyz.openbmc_project.Network.MACAddress
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | ca_high_level.rst | 1 .. SPDX-License-Identifier: GPL-2.0
25 Why the need for another CI interface?
29 Strictly speaking this is not a new interface.
31 The CI interface is defined in the DVB API in ca.h as:
33 .. code-block:: c
38 int type; /* CA interface this slot supports */
39 #define CA_CI 1 /* CI high level interface */
40 #define CA_CI_LINK 2 /* CI link layer level interface */
41 #define CA_CI_PHYS 4 /* CI physical layer level interface */
42 #define CA_DESCR 8 /* built-in descrambler */
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
| H A D | Event.interface.yaml | 1 #TODO This interface and the logging entry interface
3 # one common interface and the specific properties
7 Implement to provide event entry attributes. This interface should be
8 instantiated for the phosphor::events namespace. This interface is a
12 entries. The event D-Bus object path would look like
13 <PhosphorDbusRoot>/events/<type>/<id> Here "type" is the type of event,
14 Could be network/system state event etc. Type would be given by the
15 application configuration file which would be implementing this interface.
19 - name: Timestamp
20 type: uint64
[all …]
|