| /linux/Documentation/arch/powerpc/ |
| H A D | vmemmap_dedup.rst | 14 With 2M PMD level mapping, we require 32 struct pages and a single 64K vmemmap
18 With 1G PUD level mapping, we require 16384 struct pages and a single 64K
20 require 16 64K pages in vmemmap to map the struct page for 1G PUD level mapping.
48 require 8 4K pages in vmemmap to map the struct page for 2M pmd level mapping.
74 With 1G PUD level mapping, we require 262144 struct pages and a single 4K
76 require 4096 4K pages in vmemmap to map the struct pages for 1G PUD level
|
| /linux/arch/mips/configs/generic/ |
| H A D | board-xilfpga.config | 1 # require CONFIG_CPU_MIPS32_R2=y
2 # require CONFIG_CPU_LITTLE_ENDIAN=y
|
| H A D | board-ni169445.config | 1 # require CONFIG_CPU_MIPS32_R2=y
2 # require CONFIG_CPU_LITTLE_ENDIAN=y
|
| H A D | board-sead-3.config | 1 # require CONFIG_32BIT=y
|
| H A D | board-ocelot.config | 1 # require CONFIG_CPU_MIPS32_R2=y
|
| /linux/Documentation/admin-guide/perf/ |
| H A D | arm-ccn.rst | 26 Crosspoint PMU events require "xp" (index), "bus" (bus number)
30 require "xp" and "vc" as above plus "port" (device port index),
40 not require any other settings.
|
| /linux/Documentation/scheduler/ |
| H A D | membarrier.rst | 14 require each architecture to have a full memory barrier after coming from
24 require each architecture to have a full memory barrier after updating rq->curr,
|
| /linux/tools/testing/kunit/configs/ |
| H A D | arch_uml.config | 3 # Enable pci, as a lot of tests require it.
|
| /linux/Documentation/devicetree/bindings/sound/ |
| H A D | nvidia,tegra30-ahub.txt | 33 Tegra114 and later additionally require:
36 Tegra124 and later additionally require:
|
| /linux/drivers/net/wireless/intersil/p54/ |
| H A D | Kconfig | 12 These devices require softmac firmware which can be found at
24 These devices require softmac firmware which can be found at
|
| /linux/arch/arm/mach-axxia/ |
| H A D | Kconfig | 14 The LSI Axxia platforms require a Flattened Device Tree to be passed
|
| /linux/kernel/trace/rv/monitors/sssw/ |
| H A D | Kconfig | 11 sleeping tasks require wakeup.
|
| /linux/tools/perf/tests/config-fragments/ |
| H A D | README | 3 an optimistic set as some features require hardware support in order to
|
| /linux/Documentation/networking/dsa/ |
| H A D | bcm_sf2.rst | 63 driver require a struct device to be bound to a struct device_node, but things
70 Broadcom switches connected to a SF2 require the use of the DSA user MDIO bus
82 MoCA interfaces are fairly specific and require the use of a firmware blob which
|
| /linux/Documentation/userspace-api/gpio/ |
| H A D | gpio-v2-get-line-ioctl.rst | 66 The drive flags, ``GPIO_V2_LINE_FLAG_OPEN_xxx``, require the
75 The edge flags, ``GPIO_V2_LINE_FLAG_EDGE_xxx``, require
125 configuration for platforms that support internal bias as those that require
|
| /linux/drivers/staging/media/ipu3/ |
| H A D | TODO | 12 documentation. This may require driver changes as well.
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | smsc-lan87xx.txt | 3 Some boards require special tuning values. Configure them
|
| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices-power_resources_wakeup | 7 require ACPI power resources for wakeup signaling.
|
| /linux/Documentation/filesystems/ |
| H A D | virtiofs.rst | 17 Guests often require access to files residing on the host or remote systems.
23 tasks, they require configuration steps that are hard to automate and they
|
| /linux/drivers/usb/core/ |
| H A D | Kconfig | 45 Say N here unless you require new-device enumeration failure to
134 hub require user space authorization before they can be used.
140 USB devices require user space authorization before they can be
|
| /linux/Documentation/userspace-api/media/dvb/ |
| H A D | dvb-fe-read-status.rst | 22 Most statistics require the demodulator to be fully locked
|
| /linux/kernel/debug/kdb/ |
| H A D | kdb_cmds | 3 # processes. Commands that require process data (including stack or
|
| /linux/Documentation/process/ |
| H A D | development-process.rst | 12 discussion which does not require a deep knowledge of kernel programming to
|
| /linux/Documentation/dev-tools/kunit/ |
| H A D | faq.rst | 20 require installing the kernel on a test machine or in a virtual machine. All
21 testing frameworks require tests to be written in userspace and run on the
37 In short, yes, you can run KUnit on other architectures, but it might require
|
| /linux/Documentation/devicetree/bindings/clock/ti/ |
| H A D | clockdomain.txt | 5 only needs this information for specific clocks which require
|