/openbmc/linux/drivers/gpu/drm/ci/xfails/ |
H A D | msm-sdm845-fails.txt | 25 kms_cursor_legacy@cursor-vs-flip-atomic-transitions,Fail 26 kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size,Fail 35 kms_cursor_legacy@short-flip-after-cursor-atomic-transitions,Fail 36 kms_cursor_legacy@short-flip-after-cursor-atomic-transitions-varying-size,Fail 38 kms_cursor_legacy@short-flip-before-cursor-atomic-transitions,Fail 39 kms_cursor_legacy@short-flip-before-cursor-atomic-transitions-varying-size,Fail
|
H A D | msm-sc7180-fails.txt | 3 kms_cursor_legacy@cursorA-vs-flipA-atomic-transitions,Crash
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | debugfs-cros-ec | 40 Some ECs have a feature where they will track transitions to 44 transitions that occurred. The last_resume_result file returns 48 transitions that occurred since the suspend message was 50 system due to a timeout when watching for SLP_S0 transitions. 53 transitions have been attempted, or the EC does not support 62 Some ECs have a feature where they will track transitions of
|
/openbmc/linux/security/safesetid/ |
H A D | Kconfig | 3 bool "Gate setid transitions to limit CAP_SET{U/G}ID capabilities" 9 restrict UID/GID transitions from a given UID/GID to only those
|
/openbmc/linux/Documentation/cpu-freq/ |
H A D | cpufreq-stats.rst | 44 about the frequency transitions before the stats driver insertion. 83 This gives the total number of frequency transitions on this CPU. The cat 85 transitions. 95 transitions. The cat output here is a two dimensional matrix, where an entry 96 <i,j> (row i, column j) represents the count of number of transitions from
|
/openbmc/linux/net/llc/ |
H A D | llc_s_st.c | 177 .transitions = llc_sap_inactive_state_transitions, 181 .transitions = llc_sap_active_state_transitions,
|
/openbmc/linux/include/net/ |
H A D | llc_s_st.h | 33 struct llc_sap_state_trans **transitions; member
|
H A D | llc_c_st.h | 48 struct llc_conn_state_trans **transitions; member
|
/openbmc/linux/net/bridge/ |
H A D | br_private_mrp.h | 126 __be16 transitions; member 135 __be16 transitions; member
|
/openbmc/linux/Documentation/trace/ |
H A D | events-power.rst | 5 The power tracing system captures events related to power transitions 11 - Power domains related changes and transitions 64 The power domain events are used for power domains transitions
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
H A D | Host.interface.yaml | 20 A const property describing the allowed host transitions. Some systems 21 may not support all transitions so this property can be filled in with 22 only the supported transitions. If this property is empty then all are
|
/openbmc/qemu/docs/devel/ |
H A D | blkdebug.txt | 60 rule to match. See the "State transitions" section for information 99 State transitions 109 transitions come in. 134 The first write_aio request matches the set-state rule and transitions from
|
/openbmc/linux/Documentation/core-api/ |
H A D | entry.rst | 4 All transitions between execution domains require state updates which are 56 state transitions must run with interrupts disabled. 126 Do not nest KVM entry/exit transitions because doing so is nonsensical. 132 and KVM transitions. 209 NMIs and other NMI-like exceptions handle state transitions without
|
/openbmc/linux/Documentation/admin-guide/blockdev/drbd/ |
H A D | figures.rst | 17 Sub graphs of DRBD's state transitions
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Logging/ |
H A D | ErrorBlocksTransition.interface.yaml | 8 while a critical error is open. The managed host, via systemd transitions,
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Software/ |
H A D | ActivationBlocksTransition.interface.yaml | 9 transitions, might start the power-on sequence and then wait for any object
|
/openbmc/linux/Documentation/admin-guide/LSM/ |
H A D | SafeSetID.rst | 5 UID/GID transitions from a given UID/GID to only those approved by a 57 to do process spawning and UID/GID transitions). Unfortunately, there are a 90 None of the other in-tree LSMs have the capability to gate setid transitions, or 99 This LSM hooks the setid syscalls to make sure transitions are allowed if an
|
/openbmc/phosphor-ipmi-flash/ |
H A D | ipmi_flash.md | 106 If verification fails, the state still transitions to `verificationCompleted` 107 and similarly, if the update fails the state still transitions to
|
/openbmc/webui-vue/src/assets/styles/bootstrap/ |
H A D | _index.scss | 4 @import "~bootstrap/scss/transitions";
|
/openbmc/linux/Documentation/hwmon/ |
H A D | pm6764tr.rst | 29 The PM6764TR supports power state transitions featuring VFDE, and programmable DPM
|
/openbmc/linux/Documentation/admin-guide/hw-vuln/ |
H A D | srso.rst | 67 not address User->Kernel and Guest->Host transitions protection but it 89 User->Kernel and Guest->Host transitions protection. 103 transitions only.
|
H A D | cross-thread-rsb.rst | 9 transitions out of C0 state, the other sibling thread could use return target 43 When the thread re-enters the C0 state, the processor transitions back
|
/openbmc/linux/Documentation/devicetree/bindings/arm/tegra/ |
H A D | nvidia,tegra-ccplex-cluster.yaml | 17 registers that initiate CPU frequency/voltage transitions.
|
/openbmc/linux/Documentation/devicetree/bindings/arm/freescale/ |
H A D | fsl,imx7ulp-pm.yaml | 15 monitors events to trigger transitions between power modes while
|
/openbmc/u-boot/doc/driver-model/ |
H A D | remoteproc-framework.txt | 40 Overall, the driver statemachine transitions are typically as follows: 75 state transitions of the device as necessary.
|