Searched refs:architecture (Results 1 – 25 of 368) sorted by relevance
12345678910>>...15
| /Linux-v5.4/Documentation/features/ |
| D | arch-support.txt | 2 For generic kernel features that need architecture support, the
8 | ok | # feature supported by the architecture
9 |TODO| # feature not yet supported by the architecture
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ti/ |
| D | k3.txt | 1 Texas Instruments K3 Multicore SoC architecture device tree bindings
4 Platforms based on Texas Instruments K3 Multicore SoC architecture
11 architecture it uses, using one of the following compatible values:
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 90 ARM ARM architecture is enabled.
91 ARM64 ARM64 architecture is enabled.
105 IA-64 IA-64 architecture is enabled.
106 IMA Integrity measurement architecture is enabled.
119 M68k M68k architecture is enabled.
123 MIPS MIPS architecture is enabled.
133 PARISC The PA-RISC architecture is enabled.
138 PPC PowerPC architecture is enabled.
143 S390 S390 architecture is enabled.
151 SH SuperH architecture is enabled.
[all …]
|
| D | cputopology.rst | 12 socket number, but the actual value is architecture and platform
19 architecture and platform dependent.
25 architecture and platform dependent.
31 architecture and platform dependent.
37 architecture and platform dependent.
94 For an architecture to support this feature, it must define some of
|
| /Linux-v5.4/arch/mips/jazz/ |
| D | Kconfig | 10 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
22 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
33 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
|
| /Linux-v5.4/Documentation/ |
| D | irqflags-tracing.txt | 15 CONFIG_PROVE_RWSEM_LOCKING will be offered on an architecture - these
21 state changes. But an architecture can be irq-flags-tracing enabled in a
42 - if the architecture has non-maskable interrupts then those need to be
47 implementation in an architecture: lockdep will detect that and will
|
| /Linux-v5.4/Documentation/ABI/stable/ |
| D | syscalls | 7 Note that this interface is different for every architecture
8 that Linux supports. Please see the architecture-specific
|
| /Linux-v5.4/Documentation/vm/ |
| D | memory-model.rst | 18 FLATMEM, DISCONTIGMEM and SPARSEMEM. Each architecture defines what
49 To allocate the `mem_map` array, architecture specific setup code
55 If an architecture enables `CONFIG_ARCH_HAS_HOLES_MEMORYMODEL` option,
57 actual physical pages. In such case, the architecture specific
80 The architecture setup code should call :c:func:`free_area_init_node` for
120 `MAX_PHYSMEM_BITS` constants defined by each architecture that
122 physical address that an architecture supports, the
145 The architecture setup code should call :c:func:`memory_present` for
167 To use vmemmap, an architecture has to reserve a range of virtual
170 the architecture should implement :c:func:`vmemmap_populate` method
[all …]
|
| /Linux-v5.4/Documentation/usb/ |
| D | linux.inf | 19 ; Decoration for x86 architecture
23 ; Decoration for x64 architecture
27 ; Decoration for ia64 architecture
|
| /Linux-v5.4/tools/perf/pmu-events/ |
| D | README | 19 - To reduce JSON event duplication per architecture, platform JSONs may
21 events", defined in architecture standard JSONs.
22 Architecture standard JSONs must be located in the architecture root
44 - Set of 'PMU events tables' for all known CPUs in the architecture,
61 - A 'mapping table' that maps each CPU of the architecture, to its
86 3. _All_ known CPU tables for architecture are included in the perf
|
| /Linux-v5.4/Documentation/arm64/ |
| D | legacy_instructions.rst | 7 the architecture. The infrastructure code uses undefined instruction
19 have been obsoleted in the architecture, e.g., SWP
39 architecture. Deprecated instructions should default to emulation
|
| /Linux-v5.4/Documentation/nios2/ |
| D | nios2.rst | 2 Linux on the Nios II architecture
17 Nios II is a 32-bit embedded-processor architecture designed specifically for the
|
| /Linux-v5.4/arch/ |
| D | Kconfig | 3 # General architecture dependent options
12 menu "General architecture-dependent options"
143 This symbol should be selected by an architecture if it can
158 inline assembler that the architecture code provides in the
163 store-and-swap instructions if the architecture has them. It
168 Any architecture with load-and-swap or store-and-swap
232 An architecture should select this when it can successfully
270 An architecture should select this to provide hardened usercopy
314 This symbol should be selected by an architecture if it
381 bit-mapping of each registers and a unique architecture id.
[all …]
|
| /Linux-v5.4/drivers/clk/bcm/ |
| D | Kconfig | 18 based on the ARM architecture
26 based on the MIPS architecture
41 based on the iProc architecture
|
| /Linux-v5.4/Documentation/arm/samsung/ |
| D | gpio.rst | 8 This outlines the Samsung GPIO implementation and the architecture
33 Pin configuration is specific to the Samsung architecture, with each SoC
|
| /Linux-v5.4/Documentation/timers/ |
| D | highres.rst | 48 code out of the architecture-specific areas into a generic management
49 framework, as illustrated in figure #3 (OLS slides p. 18). The architecture
76 for various event driven functionalities is hardwired into the architecture
80 architecture. Another implication of the current design is that it is necessary
81 to touch all the architecture-specific implementations in order to provide new
87 to minimize the clock event related architecture dependent code to the pure
93 Clock event devices are registered either by the architecture dependent boot
116 architecture specific timer interrupt handlers and hands the control over the
131 The conversion of an architecture has no functional impact, but allows to
135 adding the kernel/time/Kconfig file to the architecture specific Kconfig and
|
| /Linux-v5.4/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | cpus.txt | 17 Freescale Power Architecture) defines the architecture for Freescale
18 Power CPUs. The EREF defines some architecture categories not defined
|
| /Linux-v5.4/Documentation/core-api/ |
| D | genericirq.rst | 22 interrupt subsystem based for their architecture, with the help of the
67 Analysing a couple of architecture's IRQ subsystem implementations
81 and extensible. For example, an (sub)architecture can use a generic
83 (sub)architecture specific 'edge type' implementation.
118 Whenever an interrupt triggers, the low-level architecture code calls
171 The interrupt flow handlers (either pre-defined or architecture
172 specific) are assigned to specific interrupts by the architecture either
319 which have no platform-specific IRQ handling quirks. If an architecture
383 The locking of chip registers is up to the architecture that defines the
|
| /Linux-v5.4/tools/testing/selftests/x86/ |
| D | trivial_32bit_program.c | 8 # error wrong architecture
|
| D | trivial_64bit_program.c | 8 # error wrong architecture
|
| /Linux-v5.4/include/asm-generic/ |
| D | spinlock.h | 9 #error need an architecture specific asm/spinlock.h
|
| D | tlbflush.h | 10 #error need to implement an architecture specific asm/tlbflush.h
|
| /Linux-v5.4/Documentation/riscv/ |
| D | index.rst | 2 RISC-V architecture
|
| /Linux-v5.4/Documentation/mic/ |
| D | index.rst | 2 Intel Many Integrated Core (MIC) architecture
|
| /Linux-v5.4/Documentation/x86/x86_64/ |
| D | machinecheck.rst | 81 For more details about the x86 machine check architecture
82 see the Intel and AMD architecture manuals from their developer websites.
84 For more details about the architecture see
|
12345678910>>...15
