| /linux/Documentation/features/ |
| A 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
11 | N/A| # feature doesn't apply to the architecture
|
| /linux/Documentation/admin-guide/ |
| A D | kernel-parameters.rst | 102 ARM ARM architecture is enabled.
103 ARM64 ARM64 architecture is enabled.
117 IA-64 IA-64 architecture is enabled.
131 M68k M68k architecture is enabled.
135 MIPS MIPS architecture is enabled.
151 PPC PowerPC architecture is enabled.
155 RISCV RISCV architecture is enabled.
157 S390 S390 architecture is enabled.
165 SH SuperH architecture is enabled.
167 SPARC Sparc architecture is enabled.
[all …]
|
| /linux/arch/ |
| A D | Kconfig | 3 # General architecture dependent options
12 menu "General architecture-dependent options"
123 This symbol should be selected by an architecture if 64 bit
125 though it is not a 64 bit architecture.
154 inline assembler that the architecture code provides in the
164 Any architecture with load-and-swap or store-and-swap
199 of correct one. If the architecture stacktrace code and
339 This symbol should be selected by an architecture if it
926 An architecture implements exit_thread.
1211 An architecture can select this if it provides an
[all …]
|
| /linux/Documentation/vm/ |
| A D | memory-model.rst | 18 FLATMEM and SPARSEMEM. Each architecture defines what
45 To allocate the `mem_map` array, architecture specific setup code should
50 An architecture may free parts of the `mem_map` array that do not cover the
51 actual physical pages. In such case, the architecture specific
77 `MAX_PHYSMEM_BITS` constants defined by each architecture that
79 physical address that an architecture supports, the
102 The architecture setup code should call sparse_init() to
121 To use vmemmap, an architecture has to reserve a range of virtual
124 the architecture should implement :c:func:`vmemmap_populate` method
126 virtual memory map. If an architecture does not have any special
|
| /linux/arch/mips/jazz/ |
| A D | Kconfig | 9 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
20 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
30 the MIPS architecture, check out the Linux/MIPS FAQ on the WWW at
|
| /linux/Documentation/x86/x86_64/ |
| A D | machinecheck.rst | 29 For more details about the x86 machine check architecture
30 see the Intel and AMD architecture manuals from their developer websites.
32 For more details about the architecture
|
| /linux/Documentation/core-api/irq/ |
| A D | irqflags-tracing.rst | 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/Documentation/ABI/stable/ |
| A D | sysfs-devices-system-cpu | 29 socket number, but the actual value is architecture and platform
36 architecture and platform dependent.
42 architecture and platform dependent.
48 architecture and platform dependent.
54 architecture and platform dependent. it's only used on s390.
60 architecture and platform dependent. it's only used on s390.
|
| A D | syscalls | 7 Note that this interface is different for every architecture
8 that Linux supports. Please see the architecture-specific
|
| /linux/tools/perf/pmu-events/ |
| A 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/Documentation/usb/ |
| A D | linux.inf | 19 ; Decoration for x86 architecture
23 ; Decoration for x64 architecture
27 ; Decoration for ia64 architecture
|
| /linux/Documentation/arm64/ |
| A 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
|
| A D | amu.rst | 19 ARMv8.4 CPU architecture.
26 Version 1 of the Activity Monitors architecture implements a counter group
39 The Activity Monitors architecture provides space for up to 16 architected
40 event counters. Future versions of the architecture may use this space to
|
| A D | tagged-pointers.rst | 63 Due to architecture limitations, bits 63:60 of the fault address
67 future architecture revisions which may preserve the bits.
76 The architecture prevents the use of a tagged PC, so the upper byte will
|
| A D | cpu-feature-registers.rst | 15 The ARM architecture defines a set of feature registers, which describe
31 architecture defines a canonical format for representing features
33 representing all valid architecture variations.
106 value as defined by the architecture.
110 the feature is missing (as defined by the architecture).
|
| /linux/lib/crypto/ |
| A D | Kconfig | 14 Declares whether the architecture provides an arch-specific
39 Declares whether the architecture provides an arch-specific
65 Declares whether the architecture provides an arch-specific
100 Declares whether the architecture provides an arch-specific
|
| /linux/Documentation/core-api/ |
| A 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
173 The interrupt flow handlers (either pre-defined or architecture
174 specific) are assigned to specific interrupts by the architecture either
321 which have no platform-specific IRQ handling quirks. If an architecture
385 The locking of chip registers is up to the architecture that defines the
|
| /linux/Documentation/nios2/ |
| A 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/Documentation/timers/ |
| A 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/drivers/clk/bcm/ |
| A D | Kconfig | 30 based on the ARM architecture
38 based on the MIPS architecture
53 based on the iProc architecture
|
| /linux/Documentation/devicetree/bindings/arm/ti/ |
| A D | k3.yaml | 7 title: Texas Instruments K3 Multicore SoC architecture device tree bindings
13 Platforms based on Texas Instruments K3 Multicore SoC architecture
|
| /linux/Documentation/arm/samsung/ |
| A 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/Documentation/powerpc/ |
| A D | associativity.rst | 17 Hypervisor indicates the type/form of associativity used via "ibm,architecture-vec-5 property".
18 Bit 0 of byte 5 in the "ibm,architecture-vec-5" property indicates usage of Form 0 or Form 1.
20 bit 2 of byte 5 in the "ibm,architecture-vec-5" property is used.
57 "ibm,architecture-vec-5" property.
|
| /linux/Documentation/devicetree/bindings/powerpc/fsl/ |
| A D | cpus.txt | 17 Freescale Power Architecture) defines the architecture for Freescale
18 Power CPUs. The EREF defines some architecture categories not defined
|
| /linux/Documentation/kbuild/ |
| A D | makefiles.rst | 88 architecture-specific information to the top Makefile.
913 for the target architecture (i.e. the same architecture as you are building
923 built for the target architecture.
1067 for said architecture.
1143 Append or modify as required per architecture.
1154 Append or modify as required per architecture.
1244 architecture itself.
1271 machinery is all architecture-independent.
1450 architecture-specific files.
1522 When a header is exported where the architecture uses
[all …]
|