| /openbmc/linux/Documentation/devicetree/bindings/mmc/ |
| H A 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
|
| /openbmc/linux/drivers/pinctrl/nuvoton/ |
| H A D | Kconfig | 17 the Nuvoton WPCM450 SoC. This is strongly recommended when
47 the Nuvoton NPCM8XX SoC. This is strongly recommended when
|
| /openbmc/linux/arch/m68k/include/asm/ |
| H A 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 */
|
| /openbmc/linux/arch/powerpc/perf/ |
| H A D | power9-events-list.h | 62 /* Branch event that are not strongly biased */
64 /* ALternate branch event that are not strongly biased */
|
| /openbmc/openbmc/poky/documentation/dev-manual/ |
| H A D | custom-distribution.rst | 15 Project for production use then you are strongly encouraged to create
25 separate. It is strongly recommended that you create and use your own
|
| /openbmc/linux/Documentation/admin-guide/ |
| H A D | abi-testing.rst | 15 Programs that use these interfaces are strongly encouraged to add their
|
| H A D | ramoops.rst | 31 memory to be mapped strongly ordered, and atomic operations on strongly ordered
|
| /openbmc/linux/arch/arm64/kernel/probes/ |
| H A D | decode-insn.h | 14 * ARM strongly recommends a limit of 128 bytes between LoadExcl and
|
| /openbmc/linux/Documentation/userspace-api/media/dvb/ |
| H A D | frontend_legacy_api.rst | 24 kernel due to compatibility issues only. Their usage is strongly not
|
| /openbmc/linux/virt/kvm/ |
| H A D | Kconfig | 22 # Only strongly ordered architectures can select this, as it doesn't
|
| /openbmc/linux/arch/parisc/include/asm/ |
| H A 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
|
| /openbmc/openbmc/meta-openpower/recipes-bsp/skiboot/ |
| H A D | skiboot.inc | 29 # libflash.so is a SONAME and is strongly required in the production
|
| /openbmc/linux/drivers/media/usb/gspca/stv06xx/ |
| H A D | stv06xx_st6422.h | 9 * Strongly based on qc-usb-messenger, which is:
|
| /openbmc/openbmc/poky/meta/conf/machine/include/mips/ |
| H A D | feature-mips-mips16e.inc | 9 # mips32/64 system and vice versa. It is strongly recommended that DISTROs not
|
| /openbmc/linux/fs/crypto/ |
| H A D | Kconfig | 27 # strongly recommended to enable optimized implementations too. It is safe to
|
| /openbmc/linux/Documentation/hwmon/ |
| H A D | shtc1.rst | 59 strongly recommended.
|
| /openbmc/linux/Documentation/devicetree/bindings/phy/ |
| H A D | rockchip-emmc-phy.txt | 13 access to it), it is strongly suggested.
|
| /openbmc/qemu/docs/devel/ |
| H A D | multi-thread-tcg.rst | 253 consistency models. Even emulating weakly ordered systems on strongly
279 complete at the memory barrier. On single-core non-SMP strongly
289 In the case of a strongly ordered guest architecture being emulated on
|
| /openbmc/u-boot/include/ |
| H A D | time.h | 18 * strongly encouraged to use them
|
| /openbmc/linux/Documentation/devicetree/bindings/sound/ |
| H A D | tas571x.txt | 4 signals that can be wired up to GPIOs: reset (strongly recommended), and
|
| /openbmc/linux/lib/math/ |
| H A D | int_sqrt.c | 45 * int_sqrt64 - strongly typed int_sqrt function when minimum 64 bit input
|
| /openbmc/qemu/docs/system/ |
| H A D | vnc-security.rst | 59 authentication. The use of x509 certificates is strongly recommended,
139 layers, then it is strongly advised to run it in combination with TLS
|
| /openbmc/u-boot/arch/arm/include/asm/ |
| H A D | armv7_mpu.h | 123 attr = 0; /* strongly ordered */ in get_attr_encoding()
|
| /openbmc/linux/Documentation/admin-guide/cifs/ |
| H A D | introduction.rst | 11 the most current dialect) is strongly preferred over using older
|
| /openbmc/linux/arch/arm/common/ |
| H A D | vlock.S | 43 * The vlock structure must reside in Strongly-Ordered or Device memory.
|