Searched full:fully (Results 1 – 25 of 1672) sorted by relevance
12345678910>>...67
/Linux-v6.6/Documentation/arch/arm/nwfpe/ |
D | netwinder-fpe.rst | 28 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-v6.6/Documentation/core-api/ |
D | refcount-vs-atomic.rst | 33 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-v6.6/Documentation/arch/arm/sa1100/ |
D | assabet.rst | 257 - 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-v6.6/drivers/hid/ |
D | Kconfig | 217 Support for Corsair devices that are not fully compliant with the 227 Support for Cougar devices that are not fully compliant with the 236 Support for Macally devices that are not fully compliant with the 439 - Normal: LEDs are fully on when enabled 449 Support for Keytouch HID devices not fully compliant with 456 Support for KYE/Genius devices not fully compliant with HID standard: 511 Support for ITE devices not fully compliant with HID standard. 558 Support for IBM/Lenovo devices that are not fully compliant with HID standard. 588 Support for Logitech devices that are not fully compliant with HID standard. 706 tristate "Microsoft non-fully HID-compliant devices" [all …]
|
/Linux-v6.6/Documentation/devicetree/bindings/pinctrl/ |
D | sunplus,sp7021-pinctrl.yaml | 40 (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-v6.6/include/asm-generic/bitops/ |
D | instrumented-atomic.h | 66 * 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-v6.6/Documentation/gpu/ |
D | drm-usage-stats.rst | 34 1. Mandatory, fully standardised. 35 2. Optional, fully standardised. 45 Mandatory fully standardised keys 53 Optional fully standardised keys
|
/Linux-v6.6/Documentation/ |
D | atomic_t.txt | 156 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
|
D | atomic_bitops.txt | 59 - RMW operations that have a return value are fully ordered. 61 - RMW operations that are conditional are fully ordered.
|
/Linux-v6.6/drivers/net/ethernet/qualcomm/ |
D | qca_7k_common.c | 68 * Return: QCAFRM_GATHER No ethernet frame fully received yet. 72 * > 0 Number of byte in the fully received 153 /* Frame is fully received. */ in qcafrm_fsm_decode()
|
/Linux-v6.6/Documentation/devicetree/bindings/iio/proximity/ |
D | vishay,vcnl3020.yaml | 13 The VCNL3020 is a fully integrated proximity sensor. Fully integrated means
|
/Linux-v6.6/Documentation/ABI/testing/ |
D | sysfs-hypervisor-xen | 8 "HVM": fully virtualized guest (x86) 10 "PVH": fully virtualized guest without legacy emulation (x86)
|
/Linux-v6.6/Documentation/firmware-guide/acpi/ |
D | acpi-lid.rst | 46 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-v6.6/tools/power/cpupower/utils/helpers/ |
D | msr.c | 21 * EFAULT -If the read/write did not fully complete 51 * EFAULT -If the read/write did not fully complete
|
/Linux-v6.6/include/linux/ |
D | interval_tree.h | 40 * a used, which is fully covered by nodes. Each iteration step toggles between 42 * fully cover the requested range.
|
D | atomic.h | 15 * - Fully ordered: The default implementation, no suffix required. 37 * variant is already fully ordered, no additional barriers are needed.
|
/Linux-v6.6/lib/ |
D | test_hmm_uapi.h | 47 * 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-v6.6/Documentation/devicetree/bindings/gpu/ |
D | arm,mali-bifrost.yaml | 29 - const: arm,mali-bifrost # Mali Bifrost GPU model/revision is fully discoverable 34 - const: arm,mali-valhall-jm # Mali Valhall GPU model/revision is fully discoverable 38 - const: arm,mali-valhall-jm # Mali Valhall GPU model/revision is fully discoverable
|
/Linux-v6.6/arch/riscv/include/asm/ |
D | io.h | 35 * 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-v6.6/include/media/ |
D | vsp1.h | 52 * @alpha: alpha value (0: fully transparent, 255: fully opaque)
|
/Linux-v6.6/include/linux/surface_aggregator/ |
D | controller.h | 79 * This struct fully describes a SAM request with payload. It is intended to 227 * fully initializes it via the provided request specification, submits it, 344 * request has been fully completed. The required transport buffer will be 383 * returning once the request has been fully completed. The required transport 424 * request itself, returning once the request has been fully completed. The 484 * itself, returning once the request has been fully completed. The required 544 * returning once the request has been fully completed. The required transport 585 * the request itself, returning once the request has been fully completed. 628 * execution of the request itself, returning once the request has been fully 690 * execution of the request itself, returning once the request has been fully
|
/Linux-v6.6/drivers/fpga/ |
D | dfl-afu-dma-region.c | 116 * dma_region_check_iova - check if memory area is fully contained in the region 122 * Return true if memory area is fully contained in the region, otherwise false. 238 * - otherwise, it finds the dma region which fully contains 267 /* the iova region is not fully covered. */ in afu_dma_region_find()
|
/Linux-v6.6/Documentation/scheduler/ |
D | sched-bwc.rst | 155 a. it fully consumes its own quota within a period 156 b. a parent's quota is fully consumed within its period 182 applies if quota had been assigned to a cpu and then not fully used or returned 200 cpu-bound application from fully using its quota by that same amount. In these
|
/Linux-v6.6/Documentation/gpu/rfc/ |
D | i915_scheduler.rst | 33 * GuC submission backend fully integrated with DRM scheduler 47 * ROI low on fully integrating into DRM scheduler 48 * Fully integrating would add lots of complexity to DRM
|
/Linux-v6.6/Documentation/filesystems/smb/ |
D | cifsroot.rst | 26 recommended version of the protocol (SMB3) have not been fully 32 default will change once the SMB3 POSIX extensions are fully
|
12345678910>>...67