Home
last modified time | relevance | path

Searched full:setups (Results 1 – 25 of 290) sorted by relevance

12345678910>>...12

/kernel/linux/linux-5.10/arch/x86/mm/
Dnuma_64.c3 * Generic VM initialization for x86-64 NUMA setups.
/kernel/linux/linux-4.19/arch/x86/mm/
Dnuma_64.c3 * Generic VM initialization for x86-64 NUMA setups.
/kernel/linux/linux-4.19/arch/arm/mach-imx/
Diomux-v3.h126 * setups a single pad in the iomuxer
131 * setups multiple pads
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/sound/
Dsirf-audio.txt1 * SiRF atlas6 and prima2 internal audio codec and port based audio setups
Domap-twl4030.txt1 * Texas Instruments SoC with twl4030 based audio setups
Ddavinci-evm-audio.txt1 * Texas Instruments SoC audio setups with TLV320AIC3X Codec
Domap-abe-twl6040.txt1 * Texas Instruments OMAP4+ and twl6040 based audio setups
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/
Dsirf-audio.txt1 * SiRF atlas6 and prima2 internal audio codec and port based audio setups
Domap-twl4030.txt1 * Texas Instruments SoC with twl4030 based audio setups
Ddavinci-evm-audio.txt1 * Texas Instruments SoC audio setups with TLV320AIC3X Codec
Domap-abe-twl6040.txt1 * Texas Instruments OMAP4+ and twl6040 based audio setups
/kernel/linux/linux-4.19/Documentation/
Ddebugging-modules.txt6 "succeed" in this case is hacky and breaks some setups, and also we
Dbus-virt-phys-mapping.txt24 However, on many setups, there are actually **three** different ways of looking
48 not generally necessarily true on other PCI/ISA setups.
/kernel/linux/linux-4.19/arch/arm/mach-pxa/
Dmioa701_bootresume.S15 * sleep_save_sp in the .text section as well, but some setups might
/kernel/linux/linux-5.10/drivers/ntb/hw/idt/
DKconfig25 BAR settings of peer NT-functions, the BAR setups can't be done over
/kernel/linux/linux-5.10/arch/arm/mach-pxa/
Dmioa701_bootresume.S14 * sleep_save_sp in the .text section as well, but some setups might
/kernel/linux/linux-4.19/drivers/ntb/hw/idt/
DKconfig23 BAR settings of peer NT-functions, the BAR setups can't be done over
/kernel/linux/linux-5.10/tools/perf/util/libunwind/
Darm64.c3 * This file setups defines to compile arch specific binary from the
Dx86_32.c3 * This file setups defines to compile arch specific binary from the
/kernel/linux/linux-4.19/tools/perf/util/libunwind/
Darm64.c3 * This file setups defines to compile arch specific binary from the
Dx86_32.c3 * This file setups defines to compile arch specific binary from the
/kernel/linux/linux-5.10/Documentation/core-api/
Dbus-virt-phys-mapping.rst24 However, on many setups, there are actually **three** different ways of looking
48 not generally necessarily true on other PCI/ISA setups.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/dsa/
Ddsa.yaml17 SoC. Such setups are typical for embedded devices.
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/i2c/
Di2c-ocores.txt27 This is to keep backwards compatibility with setups using old DTB. i2c bus
/kernel/linux/linux-4.19/Documentation/networking/mac80211_hwsim/
DREADME29 configuration of both very simply setups (e.g., just a single access

12345678910>>...12