| /kernel/linux/linux-5.10/arch/mips/include/asm/ |
| D | war.h | 18 * erratum #28
19 * "MIPS R4000MC Errata, Processor Revision 2.2 and 3.0", erratum
30 * erratum #52
43 * "MIPS R4400MC Errata, Processor Revision 1.0", erratum #10
44 * "MIPS R4400MC Errata, Processor Revision 2.0 & 3.0", erratum #4
57 * erratum #23
61 * erratum #41
62 * "MIPS R4000MC Errata, Processor Revision 2.2 and 3.0", erratum
64 * "MIPS R4400PC/SC Errata, Processor Revision 1.0", erratum #7
65 * "MIPS R4400MC Errata, Processor Revision 1.0", erratum #5
|
| /kernel/linux/linux-6.6/arch/arm64/kernel/ |
| D | cpu_errata.c | 101 /* ... or if the system is affected by an erratum */ in cpu_enable_trap_ctr_access()
498 .desc = "ARM erratum 832075",
508 .desc = "ARM erratum 834220",
517 .desc = "ARM erratum 843419",
526 .desc = "ARM erratum 845719",
541 .desc = "Cavium erratum 27456",
548 .desc = "Cavium erratum 30115",
562 .desc = "Qualcomm Technologies Falkor/Kryo erratum 1003",
571 .desc = "Qualcomm erratum 1009, or ARM erratum 1286807, 2441009",
581 .desc = "ARM erratum 858921",
[all …]
|
| /kernel/linux/linux-5.10/arch/arm64/kernel/ |
| D | cpu_errata.c | 101 /* ... or if the system is affected by an erratum */ in cpu_enable_trap_ctr_access()
379 .desc = "ARM erratum 832075",
389 .desc = "ARM erratum 834220",
398 .desc = "ARM erratum 843419",
407 .desc = "ARM erratum 845719",
415 .desc = "Cavium erratum 23154",
422 .desc = "Cavium erratum 27456",
429 .desc = "Cavium erratum 30115",
443 .desc = "Qualcomm Technologies Falkor/Kryo erratum 1003",
452 .desc = "Qualcomm erratum 1009, or ARM erratum 1286807",
[all …]
|
| /kernel/linux/linux-6.6/arch/arm64/ |
| D | Kconfig | 427 implementation suffers from an additional erratum where hardware
445 erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or
467 erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI
470 Under certain conditions this erratum can cause a clean line eviction
489 erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected
495 address, then this erratum might cause a clean cache line to be
512 erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache
517 maintenance operation to the same address, then this erratum might
533 erratum 832075 on Cortex-A57 parts up to r1p2.
552 erratum 834220 on Cortex-A57 parts up to r1p2.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer.yaml | 54 allwinner,erratum-unknown1:
56 description: Indicates the presence of an erratum found in Allwinner SoCs,
60 fsl,erratum-a008585:
62 description: Indicates the presence of QorIQ erratum A-008585, which says
67 hisilicon,erratum-161010101:
69 description: Indicates the presence of Hisilicon erratum 161010101, which
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/timer/ |
| D | arm,arch_timer.yaml | 71 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
|
| /kernel/linux/linux-5.10/arch/arm64/ |
| D | Kconfig | 369 erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or
391 erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI
394 Under certain conditions this erratum can cause a clean line eviction
413 erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected
419 address, then this erratum might cause a clean cache line to be
436 erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache
441 maintenance operation to the same address, then this erratum might
457 erratum 832075 on Cortex-A57 parts up to r1p2.
476 erratum 834220 on Cortex-A57 parts up to r1p2.
497 workaround erratum 1742098 on Cortex-A57 and Cortex-A72.
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/ |
| D | Kconfig | 630 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
639 r1p* erratum. If a code sequence containing an ARM/Thumb
656 erratum. For very specific sequences of memory operations, it is
672 erratum. Any asynchronous access to the L2 cache may encounter a
687 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
703 (r2p0..r2p2) erratum. Under certain conditions, specific to the
721 r1p0) erratum. On affected cores the LoUIS bit field of the CLIDR
731 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
733 As a consequence of this erratum, some TLB entries which should be
744 (r2p*) erratum. Under very rare conditions, a faulty
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-omap2/ |
| D | dma.c | 89 * Erratum ID: Not Available in configure_dma_errata()
98 * Erratum ID: Not Available in configure_dma_errata()
119 * Erratum ID: i378: OMAP2+: sDMA Channel is not disabled in configure_dma_errata()
127 * Erratum ID: i541: sDMA FIFO draining does not finish in configure_dma_errata()
138 * Erratum ID: i88 : Special programming model needed to disable DMA in configure_dma_errata()
147 * Erratum 3.2/3.3: sometimes 0 is returned if CSAC/CDAC is in configure_dma_errata()
153 * Erratum ID: Not Available in configure_dma_errata()
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | dma.c | 88 * Erratum ID: Not Available in configure_dma_errata()
97 * Erratum ID: Not Available in configure_dma_errata()
118 * Erratum ID: i378: OMAP2+: sDMA Channel is not disabled in configure_dma_errata()
126 * Erratum ID: i541: sDMA FIFO draining does not finish in configure_dma_errata()
137 * Erratum ID: i88 : Special programming model needed to disable DMA in configure_dma_errata()
146 * Erratum 3.2/3.3: sometimes 0 is returned if CSAC/CDAC is in configure_dma_errata()
152 * Erratum ID: Not Available in configure_dma_errata()
|
| /kernel/linux/linux-5.10/arch/arm/ |
| D | Kconfig | 853 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176.
862 r1p* erratum. If a code sequence containing an ARM/Thumb
879 erratum. For very specific sequences of memory operations, it is
893 erratum. Any asynchronous access to the L2 cache may encounter a
906 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction
919 (r2p0..r2p2) erratum. Under certain conditions, specific to the
934 r1p0) erratum. On affected cores the LoUIS bit field of the CLIDR
944 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the
946 As a consequence of this erratum, some TLB entries which should be
957 (r2p*) erratum. Under very rare conditions, a faulty
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 4 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
|
| /kernel/linux/linux-6.6/Documentation/admin-guide/hw-vuln/ |
| D | multihit.rst | 4 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
|
| /kernel/linux/linux-6.6/drivers/iommu/arm/arm-smmu/ |
| D | arm-smmu-impl.c | 61 * Cavium CN88xx erratum #27704. in cavium_cfg_probe()
66 dev_notice(smmu->dev, "\tenabling workaround for Cavium erratum 27704\n"); in cavium_cfg_probe()
154 * Marvell Armada-AP806 erratum #582743. in mrvl_mmu500_readq()
164 * Marvell Armada-AP806 erratum #582743. in mrvl_mmu500_writeq()
174 * Armada-AP806 erratum #582743. in mrvl_mmu500_cfg_probe()
|
| /kernel/linux/linux-5.10/drivers/iommu/arm/arm-smmu/ |
| D | arm-smmu-impl.c | 61 * Cavium CN88xx erratum #27704. in cavium_cfg_probe()
66 dev_notice(smmu->dev, "\tenabling workaround for Cavium erratum 27704\n"); in cavium_cfg_probe()
154 * Marvell Armada-AP806 erratum #582743. in mrvl_mmu500_readq()
164 * Marvell Armada-AP806 erratum #582743. in mrvl_mmu500_writeq()
174 * Armada-AP806 erratum #582743. in mrvl_mmu500_cfg_probe()
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | amd-iommu.h | 36 * amd_iommu_enable_device_erratum() - Enable erratum workaround for device
39 * @erratum: The erratum workaround to enable
42 * Possible values for the erratum number are for now:
51 extern void amd_iommu_enable_device_erratum(struct pci_dev *pdev, u32 erratum);
|
| /kernel/linux/linux-6.6/drivers/clocksource/ |
| D | Kconfig | 330 bool "Workaround for Freescale/NXP Erratum A-008585"
335 This option enables a workaround for Freescale/NXP Erratum
338 fsl,erratum-a008585 property is found in the timer node.
341 bool "Workaround for Hisilicon Erratum 161010101"
346 This option enables a workaround for Hisilicon Erratum
347 161010101. The workaround will be active if the hisilicon,erratum-161010101
351 bool "Workaround for Cortex-A73 erratum 858921"
362 bool "Workaround for Allwinner A64 erratum UNKNOWN1"
369 allwinner,erratum-unknown1 property is found in the timer node.
|
| /kernel/linux/linux-5.10/drivers/clocksource/ |
| D | Kconfig | 352 bool "Workaround for Freescale/NXP Erratum A-008585"
357 This option enables a workaround for Freescale/NXP Erratum
360 fsl,erratum-a008585 property is found in the timer node.
363 bool "Workaround for Hisilicon Erratum 161010101"
368 This option enables a workaround for Hisilicon Erratum
369 161010101. The workaround will be active if the hisilicon,erratum-161010101
373 bool "Workaround for Cortex-A73 erratum 858921"
384 bool "Workaround for Allwinner A64 erratum UNKNOWN1"
391 allwinner,erratum-unknown1 property is found in the timer node.
|
| /kernel/linux/linux-6.6/arch/arm/mach-tegra/ |
| D | reset-handler.S | 158 orr r0, r0, #1 << 14 @ erratum 716044
161 orr r0, r0, #1 << 4 @ erratum 742230
162 orr r0, r0, #1 << 11 @ erratum 751472
174 orr r0, r0, #1 << 6 @ erratum 743622
175 orr r0, r0, #1 << 11 @ erratum 751472
|
| /kernel/linux/linux-5.10/arch/arm/mach-tegra/ |
| D | reset-handler.S | 156 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/net/nfc/ |
| D | trf7970a.txt | 16 "IRQ Status Read" erratum.
18 erratum.
|
| /kernel/linux/linux-6.6/tools/perf/util/ |
| D | amd-sample-raw.c | 47 * Erratum #1238 workaround is to ignore MSRC001_1030[IbsIcMiss] in pr_ibs_fetch_ctl()
48 * Erratum #1347 workaround is to use table provided in erratum in pr_ibs_fetch_ctl()
162 * Erratum #1293 in pr_ibs_op_data3()
205 * Erratum #1293: ignore op_data2 if DcMissNoMabAlloc or SwPf are set in amd_dump_ibs_op()
|
| /kernel/linux/linux-6.6/arch/arm64/include/asm/ |
| D | arch_gicv3.h | 45 * Cavium ThunderX erratum 23154
51 * Erratum 38545
63 * erratum 23154 is not applicable.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/net/nfc/ |
| D | ti,trf7970a.yaml | 30 Specify that the trf7970a being used has the "EN2 RF" erratum
38 Specify that the trf7970a being used has the "IRQ Status Read" erratum
|
| /kernel/linux/linux-6.6/drivers/hwtracing/coresight/ |
| D | coresight-trbe.c | 73 * TRBE erratum list
78 * a given CPU is affected by the erratum. Unlike the other erratum
85 * TRBE erratum. We map the given cpucap into a TRBE internal number
90 * - Streamlined detection of erratum across the system
375 * When the TRBE is affected by an erratum that could make it in trbe_min_trace_buf_size()
693 * erratum which forces the PAGE_SIZE alignment on the TRBPTR, and thus in trbe_get_trace_size()
695 * 64bytes. Thus we ignore the potential triggering of the erratum in trbe_get_trace_size()
716 * If the TRBE is affected by the following erratum, we must fill in trbe_get_trace_size()
884 * beginning of the ring-buffer (normal-BASE). But with the erratum, in trbe_apply_work_around_before_enable()
910 * driver to move it, assuming that the erratum was triggered and in trbe_apply_work_around_before_enable()
[all …]
|