Home
last modified time | relevance | path

Searched full:fully (Results 1 – 25 of 1866) sorted by relevance

12345678910>>...75

/linux-6.14.4/Documentation/arch/arm/nwfpe/
Dnetwinder-fpe.rst28 These instructions are fully implemented.
40 These instructions are fully implemented. They store/load three words
58 FLT/FIX are fully implemented.
60 RFS/WFS are fully implemented.
62 RFC/WFC are fully implemented. RFC/WFC are supervisor only instructions, and
73 These are fully implemented.
87 These are fully implemented.
93 These are fully implemented as well. They use the same algorithm as the
103 This is fully implemented.
110 These are fully implemented.
[all …]
/linux-6.14.4/Documentation/virt/hyperv/
Dcoco.rst40 * Fully-enlightened mode. In this mode, the guest operating system is
46 fully-enlightened case.
48 Conceptually, fully-enlightened mode and paravisor mode may be treated as
50 as a CoCo VM. Fully-enlightened mode is one end of the spectrum. A full
76 The hardware architectural approach to fully-enlightened vs. paravisor mode
79 * With AMD SEV-SNP processors, in fully-enlightened mode the guest OS runs in
88 * With Intel TDX processor, in fully-enlightened mode the guest OS runs in an
108 AMD SEV-SNP in fully-enlightened mode.
118 support. While these CPUID flags are visible in fully-enlightened CoCo VMs,
134 of the decrypted references that would be used in a fully-enlightened CoCo
[all …]
/linux-6.14.4/Documentation/core-api/
Drefcount-vs-atomic.rst33 In the absence of any memory ordering guarantees (i.e. fully unordered)
86 * none (both fully unordered)
99 * none (both fully unordered)
110 * fully unordered --> RELEASE ordering
123 * fully ordered --> control dependency on success for stores
139 * fully ordered --> RELEASE ordering + ACQUIRE ordering on success
152 * fully ordered --> RELEASE ordering + control dependency
167 * fully ordered --> RELEASE ordering + control dependency + hold
/linux-6.14.4/Documentation/arch/arm/sa1100/
Dassabet.rst257 - I2C: Implemented, not fully tested.
258 - L3: Fully tested, pass.
262 - LCD: Fully tested. PM
266 - Video out: Not fully
270 - Playback: Fully tested, pass.
285 - LPE: Fully tested, pass.
288 - SIR: Fully tested, pass.
289 - FIR: Fully tested, pass.
/linux-6.14.4/drivers/hid/
DKconfig218 Support for Corsair devices that are not fully compliant with the
230 Support for Cougar devices that are not fully compliant with the
239 Support for Macally devices that are not fully compliant with the
448 - Normal: LEDs are fully on when enabled
458 Support for Keytouch HID devices not fully compliant with
465 Support for KYE/Genius devices not fully compliant with HID standard:
529 Support for ITE devices not fully compliant with HID standard.
578 Support for IBM/Lenovo devices that are not fully compliant with HID standard.
608 Support for Logitech devices that are not fully compliant with HID standard.
726 tristate "Microsoft non-fully HID-compliant devices"
[all …]
Dhid-keytouch.c3 * HID driver for Keytouch devices not fully compliant with HID standard
49 MODULE_DESCRIPTION("HID driver for Keytouch devices not fully compliant with HID standard");
/linux-6.14.4/Documentation/devicetree/bindings/pinctrl/
Dsunplus,sp7021-pinctrl.yaml40 (2) fully pin-mux (like phone exchange mux) pins:
41 GPIO 8 to 71 are 'fully pin-mux' pins. Any pins of peripherals of
43 can be routed to any pins of fully pin-mux pins.
62 routed to any of 64 'fully pin-mux' pins.
68 Vendor property "sunplus,pins" is used to select "fully pin-mux" pins,
126 Bit 23~16: defines types: (1) fully pin-mux pins
/linux-6.14.4/include/asm-generic/bitops/
Dinstrumented-atomic.h66 * This is an atomic fully-ordered operation (implied full memory barrier).
80 * This is an atomic fully-ordered operation (implied full memory barrier).
94 * This is an atomic fully-ordered operation (implied full memory barrier).
/linux-6.14.4/drivers/net/ethernet/qualcomm/
Dqca_7k_common.c55 * Return: QCAFRM_GATHER No ethernet frame fully received yet.
59 * > 0 Number of byte in the fully received
140 /* Frame is fully received. */ in qcafrm_fsm_decode()
/linux-6.14.4/Documentation/
Datomic_t.txt156 atomic variable) can be fully ordered and no intermediate state is lost or
169 - RMW operations that have a return value are fully ordered;
183 Fully ordered primitives are ordered against everything prior and everything
184 subsequent. Therefore a fully ordered primitive is like having an smp_mb()
205 NOTE: when the atomic RmW ops are fully ordered, they should also imply a
Datomic_bitops.txt59 - RMW operations that have a return value are fully ordered.
61 - RMW operations that are conditional are fully ordered.
/linux-6.14.4/drivers/thunderbolt/
Dtunnel.h25 * @TB_TUNNEL_ACTIVE: The tunnel is fully active
70 * @callback: Optional callback called when DP tunnel is fully activated
142 * tb_tunnel_is_active() - Is tunnel fully activated
145 * Returns %true if @tunnel is fully activated. For other than DP
/linux-6.14.4/Documentation/devicetree/bindings/iio/proximity/
Dvishay,vcnl3020.yaml13 The VCNL3020 is a fully integrated proximity sensor. Fully integrated means
/linux-6.14.4/Documentation/kbuild/
Dgendwarfksyms.rst86 instead of fully expanded strings.
124 - `target`: Specifies the target of the rule, typically the fully
155 - `target`: The fully qualified name of the target data structure
182 - `target`: The fully qualified name of the target enum
207 - `target`: The fully qualified name of the target enum
/linux-6.14.4/Documentation/gpu/
Ddrm-usage-stats.rst34 1. Mandatory, fully standardised.
35 2. Optional, fully standardised.
45 Mandatory fully standardised keys
53 Optional fully standardised keys
/linux-6.14.4/Documentation/ABI/testing/
Dsysfs-hypervisor-xen8 "HVM": fully virtualized guest (x86)
10 "PVH": fully virtualized guest without legacy emulation (x86)
/linux-6.14.4/Documentation/hwmon/
Dmpq8785.rst17 The MPQ8785 is a fully integrated, PMBus-compatible, high-frequency, synchronous
32 Fully integrated protection features include over-current protection (OCP),
/linux-6.14.4/Documentation/firmware-guide/acpi/
Dacpi-lid.rst46 trigger some system power saving operations on Windows. Since it is fully
77 and whether the "opened"/"closed" events are paired fully relies on the
90 are paired fully relies on the firmware implementation.
/linux-6.14.4/tools/power/cpupower/utils/helpers/
Dmsr.c21 * EFAULT -If the read/write did not fully complete
51 * EFAULT -If the read/write did not fully complete
/linux-6.14.4/include/linux/
Dinterval_tree.h40 * a used, which is fully covered by nodes. Each iteration step toggles between
42 * fully cover the requested range.
Datomic.h15 * - Fully ordered: The default implementation, no suffix required.
37 * variant is already fully ordered, no additional barriers are needed.
/linux-6.14.4/lib/
Dtest_hmm_uapi.h47 * HMM_DMIRROR_PROT_PMD: PMD sized page is fully mapped by same permissions
48 * HMM_DMIRROR_PROT_PUD: PUD sized page is fully mapped by same permissions
/linux-6.14.4/arch/riscv/include/asm/
Dio.h35 * These are defined as being "fully synchronous", but also "not guaranteed to
36 * be fully ordered with respect to other memory and I/O operations". We're
38 * - Fully ordered WRT each other, by bracketing them with two fences. The
/linux-6.14.4/Documentation/devicetree/bindings/gpu/
Darm,mali-bifrost.yaml30 - const: arm,mali-bifrost # Mali Bifrost GPU model/revision is fully discoverable
35 - const: arm,mali-valhall-jm # Mali Valhall GPU model/revision is fully discoverable
40 - const: arm,mali-valhall-jm # Mali Valhall GPU model/revision is fully discoverable
/linux-6.14.4/include/media/
Dvsp1.h52 * @alpha: alpha value (0: fully transparent, 255: fully opaque)

12345678910>>...75