| /openbmc/linux/Documentation/gpu/amdgpu/display/ |
| H A D | mpo-overview.rst | 6 'Documentation/gpu/amdgpu/display/dcn-overview.rst'.
10 fixed-function hardware in the display controller rather than using graphics or
11 compute shaders for composition. This can yield some power savings if it means
12 the graphics/compute pipelines can be put into low-power states. In summary,
13 MPO can bring the following benefits:
15 * Decreased GPU and CPU workload - no composition shaders needed, no extra
16 buffer copy needed, GPU can remain idle.
17 * Plane independent page flips - No need to be tied to global compositor
18 page-flip present rate, reduced latency, independent timing.
20 .. note:: Keep in mind that MPO is all about power-saving; if you want to learn
[all …]
|
| /openbmc/qemu/docs/system/ |
| H A D | virtio-net-failover.rst | 2 QEMU virtio-net standby (net_failover)
5 This document explains the setup and usage of virtio-net standby feature which
8 The general idea is that we have a pair of devices, a (vfio-)pci and a
9 virtio-net device. Before migration the vfio device is unplugged and data flows
10 through the virtio-net device, on the target side another vfio-pci device is
11 plugged in to take over the data-path. In the guest the net_failover kernel
14 The two devices are called primary and standby device. The fast hardware based
15 networking device is called the primary device and the virtio-net device is the
19 ------------
21 Currently only PCIe devices are allowed as primary devices, this restriction
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/net/can/ |
| H A D | st,stm32-bxcan.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/net/can/st,stm32-bxcan.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
9 description: STMicroelectronics BxCAN controller for CAN bus
12 - Dario Binacchi <dario.binacchi@amarulasolutions.com>
15 - $ref: can-controller.yaml#
20 - st,stm32f4-bxcan
22 st,can-primary:
24 Primary mode of the bxCAN peripheral is only relevant if the chip has
[all …]
|
| /openbmc/linux/Documentation/virt/ |
| H A D | ne_overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0
15 can be separated from other applications running in the same VM. This
16 application then runs in a separate VM than the primary VM, namely an enclave.
24 carved out of the primary VM. Each enclave is mapped to a process running in the
25 primary VM, that communicates with the NE kernel driver via an ioctl interface.
29 1. An enclave abstraction process - a user space process running in the primary
33 There is a NE emulated PCI device exposed to the primary VM. The driver for this
39 hypervisor running on the host where the primary VM is running. The Nitro
42 2. The enclave itself - a VM running on the same host as the primary VM that
43 spawned it. Memory and CPUs are carved out of the primary VM and are dedicated
[all …]
|
| /openbmc/linux/drivers/mfd/ |
| H A D | wm831x-irq.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * wm831x-irq.c -- Interrupt controller support for Wolfson WM831x PMICs
26 int primary; member
33 .primary = WM831X_TEMP_INT,
38 .primary = WM831X_GP_INT,
43 .primary = WM831X_GP_INT,
48 .primary = WM831X_GP_INT,
53 .primary = WM831X_GP_INT,
58 .primary = WM831X_GP_INT,
63 .primary = WM831X_GP_INT,
[all …]
|
| /openbmc/linux/Documentation/arch/sparc/oradax/ |
| H A D | dax-hv-api.txt | 3 Publication date 2017-09-25 08:21
5 Extracted via "pdftotext -f 547 -l 572 -layout sun4v_20170925.pdf"
16 live-migration and other system management activities.
20 …high speed processoring of database-centric operations. The coprocessors may support one or more of
28 …e Completion Area and, unless execution order is specifically restricted through the use of serial-
39 …machine, however, internal resource limitations within the virtual machine can cause CCB submissio…
45 …device node in the guest MD (Section 8.24.17, “Database Analytics Accelerators (DAX) virtual-device
51 36.1.1.1. "ORCL,sun4v-dax" Device Compatibility
54 • No-op/Sync
81 36.1.1.2. "ORCL,sun4v-dax-fc" Device Compatibility
[all …]
|
| /openbmc/qemu/docs/ |
| H A D | block-replication.txt | 2 ----------------------------------------
8 See the COPYING file in the top-level directory.
11 for COLO (COarse-grain LOck-stepping) where the Secondary VM is running.
12 It can also be applied for FT/HA (Fault-tolerance/High Assurance) scenario,
19 consecutive checkpoints. The VM state of the Primary and Secondary VM is
25 the Primary disk are asynchronously forwarded to the Secondary node.
30 +----------------------+ +------------------------+
31 |Primary Write Requests| |Secondary Write Requests|
32 +----------------------+ +------------------------+
36 | /-------------\
[all …]
|
| H A D | COLO-FT.txt | 1 COarse-grained LOck-stepping Virtual Machines for Non-stop Service
2 ----------------------------------------
8 See the COPYING file in the top-level directory.
14 application-agnostic software-implemented hardware fault tolerance,
15 also known as "non-stop service".
17 COLO (COarse-grained LOck-stepping) is a high availability solution.
18 Both primary VM (PVM) and secondary VM (SVM) run in parallel. They receive the
27 The primary node running the PVM, and the secondary node running the SVM
33 primary node, and then forwarded to the secondary node, so that both the PVM
44 Primary Node Secondary Node
[all …]
|
| H A D | igd-assign.txt | 1 Intel Graphics Device (IGD) assignment with vfio-pci
4 IGD has two different modes for assignment using vfio-pci:
6 1) Universal Pass-Through (UPT) mode:
8 In this mode the IGD device is added as a *secondary* (ie. non-primary)
9 graphics device in combination with an emulated primary graphics device.
16 or to use this mode in combination with guest-based remote access software,
18 theoretically has no device specific handling dependencies on vfio-pci or
23 In this mode the IGD device is intended to be the primary and exclusive
35 ISA/LPC bridge device (vfio-pci-igd-lpc-bridge) on the root bus at
44 may generate faults and errors upon re-binding to an IGD device after it
[all …]
|
| /openbmc/linux/drivers/gpu/drm/ |
| H A D | drm_modeset_helper.c | 35 * This helper library contains various one-off functions which don't really fit
40 * drm_helper_move_panel_connectors_to_head() - move panels to the front in the
57 spin_lock_irq(&dev->mode_config.connector_list_lock); in drm_helper_move_panel_connectors_to_head()
59 &dev->mode_config.connector_list, head) { in drm_helper_move_panel_connectors_to_head()
60 if (connector->connector_type == DRM_MODE_CONNECTOR_LVDS || in drm_helper_move_panel_connectors_to_head()
61 connector->connector_type == DRM_MODE_CONNECTOR_eDP || in drm_helper_move_panel_connectors_to_head()
62 connector->connector_type == DRM_MODE_CONNECTOR_DSI) in drm_helper_move_panel_connectors_to_head()
63 list_move_tail(&connector->head, &panel_list); in drm_helper_move_panel_connectors_to_head()
66 list_splice(&panel_list, &dev->mode_config.connector_list); in drm_helper_move_panel_connectors_to_head()
67 spin_unlock_irq(&dev->mode_config.connector_list_lock); in drm_helper_move_panel_connectors_to_head()
[all …]
|
| /openbmc/u-boot/doc/ |
| H A D | README.gpt | 1 # SPDX-License-Identifier: GPL-2.0+
9 - UUID -(Universally Unique Identifier)
10 - GUID - (Globally Unique ID)
11 - EFI - (Extensible Firmware Interface)
12 - UEFI - (Unified EFI) - EFI evolution
13 - GPT (GUID Partition Table) - it is the EFI standard part
14 - partitions - lists of available partitions (defined at u-boot):
20 the gpt command in u-boot.
26 globally unique value. A UUID is a 16-byte (128-bit) number. The number of
29 separated by hyphens, in the form 8-4-4-4-12 for a total of 36 characters
[all …]
|
| /openbmc/linux/drivers/block/drbd/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
19 DRBD is a shared-nothing, synchronously replicated block device. It
21 clusters and in this context, is a "drop-in" replacement for shared
24 Each minor device has a role, which can be 'primary' or 'secondary'.
25 On the node with the primary device the application is supposed to
31 DRBD can also be used in dual-Primary mode (device writable on both
32 nodes), which means it can exhibit shared disk semantics in a
33 shared-nothing cluster. Needless to say, on top of dual-Primary
38 See also: https://www.drbd.org/, http://www.linux-ha.org
|
| /openbmc/webui-vue/docs/guide/components/buttons/ |
| H A D | index.md | 4 the `primary` and `secondary` buttons. Buttons, like all Boostrap-vue components
5 can be themed by setting the `variant` prop on the component to one of the
6 [theme-color map keys](/guide/guidelines/colors). To create a button that looks
9 [Learn more about Bootstrap-vue buttons](https://bootstrap-vue.js.org/docs/components/button)
13 Add `btn-icon-only` class to the button and add `title` attribute to get helper
22 <b-button variant="primary">Primary</b-button>
23 <b-button variant="primary">
24 <icon-add />
25 <span>Primary with icon</span>
26 </b-button>
[all …]
|
| /openbmc/linux/arch/powerpc/kvm/ |
| H A D | book3s_hv_ras.c | 1 // SPDX-License-Identifier: GPL-2.0-only
21 #define SRR1_MC_LDSTERR (1ul << (63-42))
22 #define SRR1_MC_IFETCH_SH (63-45)
25 #define SRR1_MC_IFETCH_SLBMULTI 3 /* SLB multi-hit */
26 #define SRR1_MC_IFETCH_SLBPARMULTI 4 /* SLB parity + multi-hit */
27 #define SRR1_MC_IFETCH_TLBMULTI 5 /* I-TLB multi-hit */
30 #define DSISR_MC_DERAT_MULTI 0x800 /* D-ERAT multi-hit */
31 #define DSISR_MC_TLB_MULTI 0x400 /* D-TLB multi-hit */
33 #define DSISR_MC_SLB_MULTI 0x080 /* SLB multi-hit */
34 #define DSISR_MC_SLB_PARMULTI 0x040 /* SLB parity + multi-hit */
[all …]
|
| /openbmc/linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
| H A D | coex.c | 1 // SPDX-License-Identifier: GPL-2.0 OR BSD-3-Clause
3 * Copyright (C) 2013-2014, 2018-2020, 2022 Intel Corporation
4 * Copyright (C) 2013-2015 Intel Mobile Communications GmbH
11 #include "iwl-modparams.h"
13 #include "iwl-debug.h"
100 * Checking that we hold mvm->mutex is a good idea, but the rate in iwl_get_coex_type()
101 * control can't acquire the mutex since it runs in Tx path. in iwl_get_coex_type()
109 chanctx_conf = rcu_dereference(vif->bss_conf.chanctx_conf); in iwl_get_coex_type()
112 chanctx_conf->def.chan->band != NL80211_BAND_2GHZ) { in iwl_get_coex_type()
119 if (mvm->cfg->bt_shared_single_ant) { in iwl_get_coex_type()
[all …]
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-tuner.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_G_TUNER - VIDIOC_S_TUNER - Get or set tuner attributes
52 Since this is a write-only ioctl, it does not return the actually
68 .. flat-table:: struct v4l2_tuner
69 :header-rows: 0
70 :stub-columns: 0
72 * - __u32
73 - ``index``
74 - :cspan:`1` Identifies the tuner, set by the application.
75 * - __u8
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| H A D | msi-pic.txt | 4 - compatible : compatible list, may contain one or two entries
5 The first is "fsl,CHIP-msi", where CHIP is the processor(mpc8610, mpc8572,
6 etc.) and the second is "fsl,mpic-msi" or "fsl,ipic-msi" or
7 "fsl,mpic-msi-v4.3" depending on the parent type and version. If mpic
9 provided to access these 16 registers, and compatible "fsl,mpic-msi-v4.3"
13 - reg : It may contain one or two regions. The first region should contain
19 - interrupts : each one of the interrupts here is one entry per 32 MSIs,
21 be set as edge sensitive. If msi-available-ranges is present, only
25 - msi-available-ranges: use <start count> style section to define which
26 msi interrupt can be used in the 256 msi interrupts. This property is
[all …]
|
| /openbmc/openbmc-test-automation/ipmi/ |
| H A D | test_ipmi_systeminfo_parameters.robot | 5 ... 1. Set In Progress - param 0,
6 ... 2. System Firmware Version - param 1,
7 ... 3. System Name - param 2,
8 ... 4. Primary OS Name - param 3,
9 ... 5. OS Name - param 4,
10 ... 6. Present OS Version Number - param 5.
35 ... to set the set-in-progress and set complete state via IPMI,
39 # Set In Progress - set complete.
42 # Get System Info Parameter for param 0 - Set In Progress.
43 # Check if set-in-progress set to set complete.
[all …]
|
| /openbmc/linux/drivers/video/console/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
20 The program SVGATextMode can be used to utilize SVGA video cards to
28 tristate "MDA text console (dual-headed)"
33 say Y here if your MDA card is the primary card in your system; the
59 On PA-RISC, the default value is 160, which should fit a 1280x1024
69 On PA-RISC, the default value is 64, which should fit a 1280x1024
81 Low-level framebuffer-based console driver.
89 This option enables the fbcon (framebuffer text-based) hardware
93 On modern machines, on mainstream machines (like x86-64) or when
104 bool "Map the console to the primary display device"
[all …]
|
| /openbmc/phosphor-webui/app/common/styles/layout/ |
| H A D | header.scss | 10 @mixin round-corners {
11 -webkit-border-radius: 6px 6px;
12 -moz-border-radius: 6px 6px;
13 border-radius: 6px 6px;
21 z-index: 300;
24 .header__info-section {
26 background: $primary-dark;
27 color: $primary-light;
31 justify-content: space-between;
32 .dropdown-menu {
[all …]
|
| /openbmc/linux/drivers/gpu/drm/i915/display/ |
| H A D | intel_sprite_uapi.c | 1 // SPDX-License-Identifier: MIT
19 struct intel_plane *plane = to_intel_plane(plane_state->uapi.plane); in intel_plane_set_ckey()
20 struct drm_i915_private *dev_priv = to_i915(plane->base.dev); in intel_plane_set_ckey()
21 struct drm_intel_sprite_colorkey *key = &plane_state->ckey; in intel_plane_set_ckey()
27 * sprite and not on the primary. in intel_plane_set_ckey()
29 if (plane->id == PLANE_PRIMARY && in intel_plane_set_ckey()
30 set->flags & I915_SET_COLORKEY_SOURCE) in intel_plane_set_ckey()
31 key->flags = 0; in intel_plane_set_ckey()
35 * the primary and not on the sprite. in intel_plane_set_ckey()
37 if (DISPLAY_VER(dev_priv) >= 9 && plane->id != PLANE_PRIMARY && in intel_plane_set_ckey()
[all …]
|
| /openbmc/phosphor-dbus-interfaces/ |
| H A D | requirements.md | 11 Do not over-optimize properties by selecting explicit sizes such as `uint8`
17 non-countable values prefer `uint64` or `int64`.
23 as "... can be shown in user interfaces but this field should not be used for
28 The sdbusplus implementation has built-in support for enumerations, which flow
32 In some cases it is useful to have hardware-specific or OEM values for
34 the values contained within are to be sdbusplus-enumerations of a specific
35 pattern. See the [software compatibility][software-compat] and [dump
36 interface][dump-interface] as two current examples of this.
38 [software-compat]:
39 …https://github.com/openbmc/phosphor-dbus-interfaces/blob/master/yaml/xyz/openbmc_project/Software/…
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/config_files/ |
| H A D | Rainier.json | 3 "phosphor-regulators configuration file for IBM Rainier systems"
106 "asserts at the roll-over bug identified in the",
128 "Set VOUT_MODE to exponent of -9 for VDD regulator",
137 "can go down to 0.5V so we want to lower this",
148 "can go up to 1.1V so we want to raise this",
221 "can go down to 0.6V so we want to lower this",
232 "can go up to 1.0V so we want to raise this",
272 "can go down to 0.7V so we want to lower this",
283 "can go up to 1.1V so we want to raise this",
323 "can go down to 0.8V so we want to lower this",
[all …]
|
| H A D | BlueRidge.json | 3 "phosphor-regulators configuration file for IBM BlueRidge systems"
106 "asserts at the roll-over bug identified in the",
128 "Set VOUT_MODE to exponent of -9 for VDD regulator",
137 "can go down to 0.5V so we want to lower this",
148 "can go up to 1.1V so we want to raise this",
221 "can go down to 0.6V so we want to lower this",
232 "can go up to 1.0V so we want to raise this",
272 "can go down to 0.7V so we want to lower this",
283 "can go up to 1.1V so we want to raise this",
323 "can go down to 0.8V so we want to lower this",
[all …]
|
| /openbmc/linux/include/drm/ |
| H A D | drm_file.h | 4 * Copyright (c) 2009-2010, Code Aurora Forum.
69 * struct drm_minor - DRM device minor structure
74 * &struct drm_device, which is also where driver-private data and resources can
91 * struct drm_pending_event - Event queued up for userspace to read
93 * This represents a DRM event. Drivers can use this as a generic completion
94 * mechanism, which supports kernel-internal &struct completion, &struct dma_fence
95 * and also the DRM-specific &struct drm_event delivery mechanism.
120 * read using drm_read(). Can be optional, since nowadays events are
145 * Double-linked list to keep track of this event. Can be used by the
147 * this list entry is owned by the core for its own book-keeping.
[all …]
|