Searched full:strongly (Results 1 – 25 of 197) sorted by relevance
12345678
| /linux-6.8/Documentation/devicetree/bindings/mmc/ |
| D | arasan,sdhci.yaml | 52 For this device it is strongly suggested to include
58 For this device it is strongly suggested to include
64 For this device it is strongly suggested to include
68 For this device it is strongly suggested to include
74 For this device it is strongly suggested to include
80 For this device it is strongly suggested to include
86 For this device it is strongly suggested to include
90 For this device it is strongly suggested to include
94 For this device it is strongly suggested to include
|
| /linux-6.8/drivers/pinctrl/nuvoton/ |
| D | Kconfig | 16 the Nuvoton WPCM450 SoC. This is strongly recommended when
46 the Nuvoton NPCM8XX SoC. This is strongly recommended when
|
| /linux-6.8/arch/m68k/include/asm/ |
| D | mac_psc.h | 89 #define PSC_FDC_ADDR 0x1060 /* strongly suspected */
90 #define PSC_FDC_LEN 0x1064 /* strongly suspected */
91 #define PSC_FDC_CMD 0x1068 /* strongly suspected */
|
| /linux-6.8/arch/powerpc/perf/ |
| D | power9-events-list.h | 62 /* Branch event that are not strongly biased */
64 /* ALternate branch event that are not strongly biased */
|
| /linux-6.8/Documentation/admin-guide/ |
| D | abi-testing.rst | 15 Programs that use these interfaces are strongly encouraged to add their
|
| D | ramoops.rst | 31 memory to be mapped strongly ordered, and atomic operations on strongly ordered
|
| /linux-6.8/arch/arm64/kernel/probes/ |
| D | decode-insn.h | 14 * ARM strongly recommends a limit of 128 bytes between LoadExcl and
|
| /linux-6.8/arch/parisc/include/asm/ |
| D | pci.h | 91 ** access under HP PCI bus adapters, strongly recommend the use of MMIO
102 ** 2) The Programmed I/O (PIO) data may not always be strongly ordered with
|
| /linux-6.8/Documentation/userspace-api/media/dvb/ |
| D | frontend_legacy_api.rst | 24 kernel due to compatibility issues only. Their usage is strongly not
|
| /linux-6.8/virt/kvm/ |
| D | Kconfig | 25 # Only strongly ordered architectures can select this, as it doesn't
|
| /linux-6.8/drivers/media/usb/gspca/stv06xx/ |
| D | stv06xx_st6422.h | 9 * Strongly based on qc-usb-messenger, which is:
|
| /linux-6.8/Documentation/devicetree/bindings/phy/ |
| D | rockchip-emmc-phy.txt | 13 access to it), it is strongly suggested.
|
| /linux-6.8/fs/crypto/ |
| D | Kconfig | 27 # strongly recommended to enable optimized implementations too. It is safe to
|
| /linux-6.8/Documentation/hwmon/ |
| D | shtc1.rst | 59 strongly recommended.
|
| /linux-6.8/Documentation/devicetree/bindings/sound/ |
| D | tas571x.txt | 4 signals that can be wired up to GPIOs: reset (strongly recommended), and
|
| /linux-6.8/lib/math/ |
| D | int_sqrt.c | 45 * int_sqrt64 - strongly typed int_sqrt function when minimum 64 bit input
|
| /linux-6.8/Documentation/virt/kvm/arm/ |
| D | vcpu-features.rst | 44 It is **strongly recommended** that userspace modify the ID register values
|
| /linux-6.8/Documentation/admin-guide/cifs/ |
| D | introduction.rst | 11 the most current dialect) is strongly preferred over using older
|
| /linux-6.8/include/linux/platform_data/ |
| D | mtd-davinci.h | 63 /* none == NAND_ECC_ENGINE_TYPE_NONE (strongly *not* advised!!)
|
| /linux-6.8/arch/arm/common/ |
| D | vlock.S | 43 * The vlock structure must reside in Strongly-Ordered or Device memory.
|
| /linux-6.8/arch/riscv/include/asm/ |
| D | pgtable-64.h | 120 * 10 - IO Non-cacheable, non-idempotent, strongly-ordered I/O memory
136 * 10010 - IO Strongly-ordered, Non-cacheable, Non-bufferable, Shareable, Non-trustable
|
| /linux-6.8/Documentation/ |
| D | atomic_t.txt | 364 Such implementations are strongly encouraged to add exponential backoff loops
366 also strongly encouraged to inspect/audit the atomic fallbacks, refcount_t and
|
| /linux-6.8/Documentation/filesystems/nfs/ |
| D | exporting.rst | 133 fh_to_parent (optional but strongly recommended)
138 get_parent (optional but strongly recommended)
|
| /linux-6.8/Documentation/admin-guide/perf/ |
| D | nvidia-pmu.rst | 32 strongly-ordered (SO) PCIE write traffic to local/remote memory. Please see
247 PCIE1 traffic represents strongly ordered (SO) writes.
298 PCIE1 traffic represents strongly ordered (SO) writes.
|
| /linux-6.8/Documentation/nvdimm/ |
| D | maintainer-entry-profile.rst | 41 to push back on the proliferation of NVDIMM command sets, so do strongly
|
12345678