| /openbmc/u-boot/doc/ |
| H A D | README.bus_vcxk | 45 describes the acknowledge line from vcxk hardware
48 describes the enable line to vcxk hardware
51 describes the invert line to vcxk hardware
54 describes the reset line to vcxk hardware
57 describes the request line to vcxk hardware
|
| /openbmc/linux/Documentation/devicetree/bindings/x86/ |
| H A D | ce4100.txt | 30 A "cpu" node describes one logical processor (hardware thread).
44 This node describes the in-core peripherals. Required property:
49 This node describes the PCI bus on the SoC. Its property should be
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/ |
| H A D | ibm,powerpc-cpu-features.txt | 12 This device tree binding describes CPU features available to software, with
104 This property describes the privilege levels and/or software components
118 This property describes the HV privilege support required to enable the
137 This property describes the OS privilege support required to enable the
154 property describes the bit number in the HFSCR register that the
167 property describes the bit number in the FSCR register that the
180 This property describes the bit number that should be set in the ELF AUX
|
| /openbmc/libcper/specification/document/ |
| H A D | cper-json-specification.tex | 83 This structure describes the JSON format of the standard CPER header as defined in section N.2.1 of…
120 This structure describes the error severity of a single CPER record.
130 This structure describes a bitfield for validating the fields of the header of a single CPER record.
142 This structure describes the notification type of a single CPER record.
152 This structure describes the enabled flag on a given CPER record header.
162 This section describes the JSON format of a single CPER record section descriptor as defined by sec…
166 …t64 & The offset (in bytes) of the section body this section descriptor describes from the base of…
191 This structure describes the enabled flags on a given CPER section descriptor.
212 This section describes generic CPER structures that are re-used throughout the specification.
217 This structure describes the revision of a single CPER record or sub-structure.
[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.
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.
|
| /openbmc/phosphor-dbus-interfaces/yaml/com/ibm/ipzvpd/ |
| H A D | README.md | 8 The [OpenPower VPD][1] format is quite similar to the IPZ format and describes
11 Also refer to the [VPD Collection design document][2] that describes how the VPD
|
| /openbmc/linux/Documentation/devicetree/bindings/net/ |
| H A D | marvell-orion-net.txt | 9 first level describes the ethernet controller itself and the second level
10 describes up to 3 ethernet port nodes within that controller. The reason for
12 set of controller registers. Each port node describes port-specific properties.
|
| /openbmc/u-boot/doc/device-tree-bindings/video/ |
| H A D | rockchip-lvds.txt | 16 This describes how the color bits are laid out in the
20 <LVDS_OUTPUT_DUAL>, This describes the output face.
|
| H A D | tegra20-dc.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
20 The panel node describes the panel itself. This has the properties listed in
|
| /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.
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.
|
| /openbmc/qemu/docs/interop/ |
| H A D | vnc-ledstate-pseudo-encoding.rst | 7 This document describes the Pseudo-encoding of LED state for RFB which
37 The LED state Pseudo-encoding describes the encoding of LED state which
|
| /openbmc/u-boot/doc/device-tree-bindings/nand/ |
| H A D | nvidia,tegra20-nand.txt | 4 (there isn't yet a generic binding in Linux, so this describes what is in
6 a binding that describes this hardware. But agreeing a binding in Linux in
|
| /openbmc/entity-manager/schemas/ |
| H A D | README.md | 11 most schema describes a single object or an array of objects.
42 The probe property describes the event which will cause entity manager to export
47 The exposes property describes the configuration data at its most specific
|
| /openbmc/linux/Documentation/arch/arm/ |
| H A D | setup.rst | 5 The following document describes the kernel initialisation parameter
55 This describes the character position of cursor on VGA console, and
85 This describes the kernel virtual start address and size of the
|
| /openbmc/linux/Documentation/admin-guide/perf/ |
| H A D | imx-ddr.rst | 16 The "format" directory describes format of the config (event ID) and config1
18 devices/imx8_ddr0/format/. The "events" directory describes the events types
20 devices/imx8_ddr0/events/. The "caps" directory describes filter features implemented
|
| H A D | hns3-pmu.rst | 24 The "events" directory describes the event code of all supported events
27 The "filtermode" directory describes the supported filter modes of each
30 The "format" directory describes all formats of the config (events) and
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A D | sysfs-bus-i3c | 53 This entry describes the BCR of the master controller driving
63 This entry describes the DCR of the master controller driving
75 This entry describes the PID of the master controller driving
88 This entry describes the HDRCAP of the master controller
|
| /openbmc/linux/Documentation/devicetree/bindings/display/imx/ |
| H A D | ldb.txt | 48 or a display-timings node that describes the video timings for the connected
66 - display-timings : A node that describes the display timings as defined in
69 This describes how the color bits are laid out in the
|
| /openbmc/qemu/docs/system/ |
| H A D | device-emulation.rst | 10 used to describes devices within QEMU.
26 A front end is often paired with a back end, which describes how the
56 The back end describes how the data from the emulated device will be
|
| /openbmc/linux/Documentation/firmware-guide/ |
| H A D | index.rst | 7 This section describes the ACPI subsystem in Linux from firmware perspective.
|
| /openbmc/u-boot/doc/device-tree-bindings/firmware/ |
| H A D | ti,sci.txt | 19 The TI-SCI node describes the Texas Instrument's System Controller entity node.
22 functionality as may be required for the SoC. This hierarchy also describes the
|
| /openbmc/linux/drivers/staging/fieldbus/Documentation/devicetree/bindings/fieldbus/ |
| H A D | arcx,anybus-controller.txt | 41 - reg: Must contain the host index of the card this subnode describes:
45 index uniquely describes the card location.
|
| /openbmc/linux/Documentation/devicetree/bindings/iio/adc/ |
| H A D | xilinx-xadc.txt | 3 This binding document describes the bindings for the Xilinx 7 Series XADC as well
11 document describes the bindings for both of them since the bindings are very
18 called the Xilinx System Management Wizard. This document describes the bindings
|
| /openbmc/u-boot/doc/device-tree-bindings/pmic/ |
| H A D | rn5t567.txt | 3 This file describes the binding info for the PMIC driver.
|
| H A D | s2mps11.txt | 3 This file describes the binding info for the PMIC driver:
|