Home
last modified time | relevance | path

Searched full:arm32 (Results 1 – 25 of 32) sorted by relevance

12

/linux-6.8/drivers/soc/renesas/
DKconfig62 bool "ARM32 Platform support for Emma Mobile EV2"
67 bool "ARM32 Platform support for R-Car E2"
73 bool "ARM32 Platform support for R-Car H1"
82 bool "ARM32 Platform support for R-Car H2"
90 bool "ARM32 Platform support for R-Car M1A"
95 bool "ARM32 Platform support for R-Car M2-N"
102 bool "ARM32 Platform support for R-Car M2-W"
109 bool "ARM32 Platform support for R-Car V2H"
115 bool "ARM32 Platform support for R-Mobile A1"
121 bool "ARM32 Platform support for R-Mobile APE6"
[all …]
/linux-6.8/drivers/gpu/drm/ci/
Dbuild.yml12 .build:arm32:
46 igt:arm32:
47 extends: .build:arm32
63 testing:arm32:
64 extends: .build:arm32
102 build:arm32:
103 extends: .build:arm32
Dtest.yml21 .lava-igt:arm32:
23 - .lava-test:arm32
28 - testing:arm32
33 - testing:arm32
34 - igt:arm32
140 - .lava-igt:arm32
/linux-6.8/arch/arm64/boot/dts/qcom/
Dmsm8916-samsung-e7.dts8 * NOTE: The original firmware from Samsung can only boot ARM32 kernels on some
14 * However, it is possible to use this device tree by compiling an ARM32 kernel
Dmsm8916-samsung-e5.dts8 * NOTE: The original firmware from Samsung can only boot ARM32 kernels on some
14 * However, it is possible to use this device tree by compiling an ARM32 kernel
Dmsm8916-samsung-grandmax.dts9 * NOTE: The original firmware from Samsung can only boot ARM32 kernels on some
15 * However, it is possible to use this device tree by compiling an ARM32 kernel
Dmsm8916-samsung-serranove.dts16 * NOTE: The original firmware from Samsung can only boot ARM32 kernels.
21 * However, it is possible to use this device tree by compiling an ARM32 kernel
/linux-6.8/arch/arm/mach-qcom/
DKconfig34 The ARM32 option is intended for a few devices with signed firmware
/linux-6.8/Documentation/devicetree/bindings/tpm/
Dmicrosoft,ftpm.yaml25 https://github.com/Microsoft/ms-tpm-20-ref/tree/main/Samples/ARM32-FirmwareTPM
/linux-6.8/include/crypto/
Dnhpoly1305.h17 /* Stride: 2 words (optimal on ARM32 NEON; works okay on other CPUs too) */
/linux-6.8/include/linux/
Dmbus.h75 * On all ARM32 MVEBU platforms with MBus support, this stub in mvebu_mbus_get_io_win_info()
/linux-6.8/tools/arch/arm64/include/asm/
Dbarrier.h10 * a case like for arm32 where we do things differently in userspace?
/linux-6.8/drivers/char/tpm/
Dtpm_ftpm_tee.c9 * https://github.com/microsoft/ms-tpm-20-ref/tree/master/Samples/ARM32-FirmwareTPM/optee_ta/fTPM
27 …* https://github.com/microsoft/ms-tpm-20-ref/blob/master/Samples/ARM32-FirmwareTPM/optee_ta/fTPM/i…
/linux-6.8/Documentation/arch/arm/nwfpe/
Dnwfpe.rst34 port of SoftFloat version 1 by Neil Carson for NetBSD/arm32.
/linux-6.8/Documentation/admin-guide/
Defi-stub.rst13 drivers/firmware/efi/libstub/arm32-stub.c. EFI stub code that is shared
/linux-6.8/drivers/firmware/efi/libstub/
DMakefile88 lib-$(CONFIG_ARM) += arm32-stub.o
/linux-6.8/arch/arm64/include/asm/
Delf.h105 *              CPU*: | arm32    | arm64 |
/linux-6.8/arch/arm64/kernel/
Dtopology.c6 * Based on the arm32 version written by Vincent Guittot in turn based on
/linux-6.8/arch/arm/mm/
Dkasan_init.c152 * directories since we believe ARM32 will never gain four in kasan_pgd_populate()
/linux-6.8/Documentation/devicetree/bindings/edac/
Dsocfpga-eccmgr.txt241 are treated as SErrors in ARM64 instead of IRQs in ARM32.
/linux-6.8/include/linux/firmware/intel/
Dstratix10-smc.h35 * a0..a7 is used as register names in the descriptions below, on arm32
/linux-6.8/drivers/tee/optee/
Doptee_smc.h34 * a0..a7 is used as register names in the descriptions below, on arm32
/linux-6.8/drivers/interconnect/qcom/
Dicc-rpm.c388 /* ARM32 caps clk_set_rate arg to u32.. Nothing we can do about that! */ in qcom_icc_set()
/linux-6.8/Documentation/admin-guide/sysctl/
Dnet.rst66 - arm32
/linux-6.8/Documentation/filesystems/
Dfscrypt.rst428 - arm32: CONFIG_CRYPTO_CHACHA20_NEON
429 - arm32: CONFIG_CRYPTO_NHPOLY1305_NEON

12