Searched full:strongly (Results 1 – 25 of 205) sorted by relevance
123456789
52 For this device it is strongly suggested to include58 For this device it is strongly suggested to include64 For this device it is strongly suggested to include68 For this device it is strongly suggested to include74 For this device it is strongly suggested to include80 For this device it is strongly suggested to include86 For this device it is strongly suggested to include90 For this device it is strongly suggested to include94 For this device it is strongly suggested to include
16 the Nuvoton WPCM450 SoC. This is strongly recommended when46 the Nuvoton NPCM8XX SoC. This is strongly recommended when
89 #define PSC_FDC_ADDR 0x1060 /* strongly suspected */90 #define PSC_FDC_LEN 0x1064 /* strongly suspected */91 #define PSC_FDC_CMD 0x1068 /* strongly suspected */
62 /* Branch event that are not strongly biased */64 /* ALternate branch event that are not strongly biased */
14 * ARM strongly recommends a limit of 128 bytes between LoadExcl and
17 Programs that use these interfaces are strongly encouraged to add their
33 memory to be mapped strongly ordered, and atomic operations on strongly ordered
7 Modern NICs are strongly encouraged to focus on implementing the ``switchdev``
91 ** access under HP PCI bus adapters, strongly recommend the use of MMIO102 ** 2) The Programmed I/O (PIO) data may not always be strongly ordered with
24 kernel due to compatibility issues only. Their usage is strongly not
9 * Strongly based on qc-usb-messenger, which is:
28 # strongly recommended to enable optimized implementations too.
22 # Only strongly ordered architectures can select this, as it doesn't
59 strongly recommended.
45 * int_sqrt64 - strongly typed int_sqrt function when minimum 64 bit input
44 It is **strongly recommended** that userspace modify the ID register values
11 the most current dialect) is strongly preferred over using older
43 * The vlock structure must reside in Strongly-Ordered or Device memory.
364 Such implementations are strongly encouraged to add exponential backoff loops366 also strongly encouraged to inspect/audit the atomic fallbacks, refcount_t and
133 fh_to_parent (optional but strongly recommended)138 get_parent (optional but strongly recommended)
41 to push back on the proliferation of NVDIMM command sets, so do strongly
53 It is strongly recommended to work with the Linux NVMe and block layer
320 * exclusivity some other way. Locking is strongly recommended.418 * exclusivity some other way. Locking is strongly recommended.517 * exclusivity some other way. Locking is strongly recommended.
32 strongly-ordered (SO) PCIE write traffic to local/remote memory. Please see281 PCIE1 traffic represents strongly ordered (SO) writes.332 PCIE1 traffic represents strongly ordered (SO) writes.
70 * A higher number applies xnr filtering more strongly. A value of 1.0