Home
last modified time | relevance | path

Searched refs:erratum (Results 1 – 25 of 56) sorted by relevance

123

/linux-6.1.9/Documentation/devicetree/bindings/timer/
Darm,arch_timer.yaml71 allwinner,erratum-unknown1:
73 description: Indicates the presence of an erratum found in Allwinner SoCs,
77 fsl,erratum-a008585:
79 description: Indicates the presence of QorIQ erratum A-008585, which says
84 hisilicon,erratum-161010101:
86 description: Indicates the presence of Hisilicon erratum 161010101, which
/linux-6.1.9/arch/arm/mach-tegra/
Dreset-handler.S156 orr r0, r0, #1 << 14 @ erratum 716044
159 orr r0, r0, #1 << 4 @ erratum 742230
160 orr r0, r0, #1 << 11 @ erratum 751472
172 orr r0, r0, #1 << 6 @ erratum 743622
173 orr r0, r0, #1 << 11 @ erratum 751472
/linux-6.1.9/Documentation/admin-guide/hw-vuln/
Dmultihit.rst4 iTLB multihit is an erratum where some processors may incur a machine check
9 exploit this erratum to perform a denial of service attack.
15 Variations of this erratum are present on most Intel Core and Xeon processor
16 models. The erratum is not present on:
62 Attacks against the iTLB multihit erratum can be mounted from malicious
91 Enumeration of the erratum
107 This erratum can be mitigated by restricting the use of large page sizes to
/linux-6.1.9/arch/arm64/
DKconfig388 erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or
410 erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI
413 Under certain conditions this erratum can cause a clean line eviction
432 erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected
438 address, then this erratum might cause a clean cache line to be
455 erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache
460 maintenance operation to the same address, then this erratum might
476 erratum 832075 on Cortex-A57 parts up to r1p2.
495 erratum 834220 on Cortex-A57 parts up to r1p2.
516 workaround erratum 1742098 on Cortex-A57 and Cortex-A72.
[all …]
/linux-6.1.9/Documentation/arm64/
Dsilicon-errata.rst30 a Category A erratum into a Category C erratum. These are collectively
36 the erratum in question, a Kconfig entry is added under "Kernel
41 a way that the erratum will not be hit.
/linux-6.1.9/Documentation/devicetree/bindings/net/nfc/
Dti,trf7970a.yaml30 Specify that the trf7970a being used has the "EN2 RF" erratum
38 Specify that the trf7970a being used has the "IRQ Status Read" erratum
/linux-6.1.9/Documentation/devicetree/bindings/i2c/
Di2c-mpc.yaml49 fsl,i2c-erratum-a004447:
52 Indicates the presence of QorIQ erratum A-004447, which
/linux-6.1.9/arch/arm/
DKconfig627 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
636 r1p* erratum. If a code sequence containing an ARM/Thumb
653 erratum. For very specific sequences of memory operations, it is
667 erratum. Any asynchronous access to the L2 cache may encounter a
680 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
693 (r2p0..r2p2) erratum. Under certain conditions, specific to the
708 r1p0) erratum. On affected cores the LoUIS bit field of the CLIDR
718 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
720 As a consequence of this erratum, some TLB entries which should be
731 (r2p*) erratum. Under very rare conditions, a faulty
[all …]
/linux-6.1.9/arch/arm64/boot/dts/freescale/
Dfsl-ls1043-post.dtsi23 fsl,erratum-a050385;
/linux-6.1.9/arch/powerpc/boot/dts/fsl/
Dqoriq-fman3l-0.dtsi82 fsl,erratum-a009885;
90 fsl,erratum-a009885;
Dp2041si-post.dtsi375 fsl,i2c-erratum-a004447;
379 fsl,i2c-erratum-a004447;
384 fsl,i2c-erratum-a004447;
388 fsl,i2c-erratum-a004447;
Dp1010si-post.dtsi126 fsl,i2c-erratum-a004447;
131 fsl,i2c-erratum-a004447;
Dqoriq-fman3-0-1g-0.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-0-1g-1.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-0-1g-2.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-0-1g-3.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-0-1g-4.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-0-1g-5.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-1-1g-0.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-1-1g-1.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-1-1g-2.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
Dqoriq-fman3-1-1g-3.dtsi62 fsl,erratum-a011043; /* must ignore read errors */
/linux-6.1.9/Documentation/devicetree/bindings/net/
Dfsl-fman.txt113 - fsl,erratum-a050385
117 erratum A050385 which indicates that DMA transactions that are
297 - fsl,erratum-a009885
301 erratum describing that the contents of MDIO_DATA may
306 - fsl,erratum-a011043
309 Definition: Indicates the presence of the A011043 erratum
/linux-6.1.9/arch/x86/kernel/cpu/
Damd.c33 static bool cpu_has_amd_erratum(struct cpuinfo_x86 *cpu, const int *erratum);
1130 static bool cpu_has_amd_erratum(struct cpuinfo_x86 *cpu, const int *erratum) in cpu_has_amd_erratum() argument
1132 int osvw_id = *erratum++; in cpu_has_amd_erratum()
1152 while ((range = *erratum++)) in cpu_has_amd_erratum()
/linux-6.1.9/drivers/net/ethernet/freescale/fman/
DKconfig18 DPAA FMan erratum A050385 software workaround implementation:

123