Home
last modified time | relevance | path

Searched full:platforms (Results 1 – 25 of 379) sorted by relevance

12345678910>>...16

/Documentation/ABI/testing/
Dsysfs-driver-intel-xe-hwmon13 Only supported for particular Intel Xe graphics platforms.
21 Only supported for particular Intel Xe graphics platforms.
30 Only supported for particular Intel Xe graphics platforms.
39 Only supported for particular Intel Xe graphics platforms.
53 Only supported for particular Intel Xe graphics platforms.
61 Only supported for particular Intel Xe graphics platforms.
74 Only supported for particular Intel Xe graphics platforms.
93 Only supported for particular Intel Xe graphics platforms.
102 Only supported for particular Intel Xe graphics platforms.
110 Only supported for particular Intel Xe graphics platforms.
Dsysfs-driver-intel-i915-hwmon7 Only supported for particular Intel i915 graphics platforms.
21 Only supported for particular Intel i915 graphics platforms.
29 Only supported for particular Intel i915 graphics platforms.
38 Only supported for particular Intel i915 graphics platforms.
51 Only supported for particular Intel i915 graphics platforms.
64 Only supported for particular Intel i915 graphics platforms.
77 Only supported for particular Intel i915 graphics platforms.
85 Only supported for particular Intel i915 graphics platforms.
/Documentation/devicetree/bindings/arm/ti/
Domap.yaml12 description: Platforms based on Texas Instruments OMAP SoC architecture.
20 - description: TI OMAP2420 SoC based platforms
30 - description: TI OMAP2430 SoC based platforms
37 - description: TI OMAP3430 SoC based platforms
76 - description: TI OMAP3630 SoC based platforms
94 - description: TI AM35 SoC based platforms
131 - description: TI OMAP4430 SoC based platforms
151 - description: TI OMAP4460 SoC based platforms
168 - description: TI OMAP5 SoC based platforms
/Documentation/devicetree/bindings/sound/
Dmvebu-audio.txt6 "marvell,kirkwood-audio" for Kirkwood platforms
7 "marvell,dove-audio" for Dove platforms
8 "marvell,armada370-audio" for Armada 370 platforms
9 "marvell,armada-380-audio" for Armada 38x platforms
/Documentation/devicetree/bindings/arm/
Dapple.yaml13 ARM platforms using SoCs designed by Apple Inc., branded "Apple Silicon".
68 - description: Apple M1 SoC based platforms
79 - description: Apple M2 SoC based platforms
88 - description: Apple M1 Pro SoC based platforms
96 - description: Apple M1 Max SoC based platforms
105 - description: Apple M1 Ultra SoC based platforms
Dgoogle.yaml7 title: Google Tensor platforms
13 ARM platforms using SoCs designed by Google branded "Tensor" used in Pixel
/Documentation/firmware-guide/acpi/
Dacpi-lid.rst14 Platforms containing lids convey lid state (open/close) to OSPMs
20 For most platforms, both the _LID method and the lid notifications are
22 exceptional buggy platforms, special restrictions and exceptions should be
37 There are platforms always return "closed" as initial lid state.
58 the previous explanation, it is not reliable enough on some platforms. So
80 This option can be used to fix some platforms where the returning value
92 This may fix some platforms where the returning value of the _LID
Dlpit.rst7 To enumerate platform Low Power Idle states, Intel platforms are using
15 On platforms supporting S0ix sleep states, there can be two types of
/Documentation/devicetree/bindings/crypto/
Dmarvell-cesa.txt20 required for orion and kirkwood platforms
24 platforms.
25 "cesazX" clocks are not required on armada-370 platforms
/Documentation/PCI/
Dsysfs-pci.rst7 sysfs, usually mounted at /sys, provides access to PCI resources on platforms
72 used to do actual device programming from userspace. Note that some platforms
119 Supporting PCI access on new platforms
125 mmap() through files in /proc/bus/pci, platforms may also set HAVE_PCI_MMAP.
127 Alternatively, platforms which set HAVE_PCI_MMAP may provide their own
131 Platforms which support write-combining maps of PCI resources must define
133 write-combining is permitted. Platforms which support maps of I/O resources
136 Legacy resources are protected by the HAVE_PCI_LEGACY define. Platforms
/Documentation/devicetree/bindings/mfd/
Darm,dev-platforms-syscon.yaml4 $id: http://devicetree.org/schemas/mfd/arm,dev-platforms-syscon.yaml#
7 title: Arm Ltd Developer Platforms System Controllers
14 platforms are contain various system controller blocks. Often these blocks
/Documentation/arch/powerpc/
Dbooting.rst14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
15 platforms which move into arch/powerpc will be required to use these rules as
89 Board supports (platforms) are not exclusive config options. An
101 "arch/powerpc/platforms/myplatform/myboard_setup.c" and add it
107 A kernel image may support multiple platforms, but only if the
108 platforms feature the same core architecture. A single kernel build
/Documentation/arch/arm/
Dmemory.rst11 free for platforms to use, and which are used by generic code.
31 Platforms must not use this address range.
42 fffe8000 fffeffff DTCM mapping area for platforms with
45 fffe0000 fffe7fff ITCM mapping area for platforms with
69 This maps the platforms RAM, and typically
/Documentation/dev-tools/
Dautofdo.rst29 can be applied across platforms to achieve performance gains. For
57 effective on platforms supporting advanced PMU features like
124 - For Intel platforms::
128 - For AMD platforms:
144 - For ARM platforms with ETM trace:
153 For ARM platforms running Android, follow the instructions in the
/Documentation/devicetree/bindings/hwinfo/
Dti,k3-socinfo.yaml7 title: Texas Instruments K3 Multicore SoC platforms chipid module
14 Texas Instruments (ARM64) K3 Multicore SoC platforms chipid module is
/Documentation/devicetree/bindings/firmware/
Dnvidia,tegra210-bpmp.txt7 some platforms. The binding document defines the resources that would
23 - #clock-cells : Should be 1 for platforms where DRAM clock control is
/Documentation/process/
Dmaintainer-soc-clean-dts.rst4 SoC Platforms with DTS Compliance Requirements
10 SoC platforms or subarchitectures should follow all the rules from
Dmaintainer-soc.rst27 of new platforms, or the removal of existing ones, often go through the SoC
39 individual platforms and driver subdirectories.
89 As new platforms spring up, they often bring with them new submaintainers,
152 Some platforms also have System on Modules, containing an SoC, which are then
153 integrated into several different boards. For these platforms, $soc-$som.dtsi
167 For new platforms, or additions to existing ones, ``make dtbs_check`` should not
187 platforms including dts files and drivers.
/Documentation/networking/device_drivers/ethernet/neterion/
Ds2io.rst63 significant performance improvement on certain platforms(SGI Altix,
66 d. MSI/MSI-X. Can be enabled on platforms which support this feature
68 platforms).
174 certain platforms(eg. SGI Altix, IBM xSeries).
185 For AMD opteron platforms with 8131 chipset, MMRBC=1 and MOST=1 are
/Documentation/devicetree/bindings/interrupt-controller/
Dmarvell,mpic.yaml14 platforms it also provides inter-processor interrupts.
32 Parent interrupt on platforms where MPIC is not the top-level
/Documentation/ABI/stable/
Dvdso13 platforms they are called just like ordinary C function. On other platforms
/Documentation/admin-guide/pm/
Dcpufreq_drivers.rst62 The cpufreq-nforce2 driver changes the FSB on nVidia nForce2 platforms.
64 This works better than on other platforms, because the FSB of the CPU
103 1.2 Platforms affected
180 1.2 Platforms affected:
187 Currently, certain HP ProLiant platforms implement the PCC interface. On those
188 platforms PCC is the "default" choice.
191 such an instance, as is also the case on platforms where the PCC interface
266 Currently, the PCC driver does not evaluate _PSD. The platforms that support
/Documentation/devicetree/bindings/i2c/
Dti,omap4-i2c.yaml45 This property is applicable only on legacy platforms mainly omap2/3
46 and ti81xx and should not be used on other platforms.
/Documentation/devicetree/bindings/mips/
Dni.txt1 National Instruments MIPS platforms
/Documentation/mm/
Dnuma.rst22 these types of interconnects can be aggregated to create NUMA platforms with
25 For Linux, the NUMA platforms of interest are primarily what is known as Cache
34 bandwidths than accesses to memory on other, remote cells. NUMA platforms
63 the existing nodes--or the system memory for non-NUMA platforms--into multiple
66 application features on non-NUMA platforms, and as a sort of memory resource

12345678910>>...16