Searched refs:erratum (Results 1 – 17 of 17) sorted by relevance
/linux-4.4.14/Documentation/devicetree/bindings/net/nfc/ |
D | trf7970a.txt | 18 "IRQ Status Read" erratum. 20 erratum. 21 - t5t-rmb-extra-byte-quirk: Specify that the trf7970a has the erratum
|
/linux-4.4.14/arch/arm/mach-tegra/ |
D | reset-handler.S | 131 orr r0, r0, #1 << 14 @ erratum 716044 134 orr r0, r0, #1 << 4 @ erratum 742230 135 orr r0, r0, #1 << 11 @ erratum 751472 147 orr r0, r0, #1 << 6 @ erratum 743622 148 orr r0, r0, #1 << 11 @ erratum 751472
|
/linux-4.4.14/arch/arm64/ |
D | Kconfig | 221 erratum 826319 on Cortex-A53 parts up to r0p2 with an AMBA 4 ACE or 242 erratum 827319 on Cortex-A53 parts up to r0p2 with an AMBA 5 CHI 245 Under certain conditions this erratum can cause a clean line eviction 263 erratum 824069 on Cortex-A53 parts up to r0p2 when it is connected 269 address, then this erratum might cause a clean cache line to be 285 erratum 819472 on Cortex-A53 parts up to r0p1 with an L2 cache 290 maintenance operation to the same address, then this erratum might 306 erratum 832075 on Cortex-A57 parts up to r1p2. 325 erratum 834220 on Cortex-A57 parts up to r1p2. 346 erratum 845719 on Cortex-A53 parts up to r0p4. [all …]
|
/linux-4.4.14/include/linux/ |
D | amd-iommu.h | 49 extern void amd_iommu_enable_device_erratum(struct pci_dev *pdev, u32 erratum);
|
/linux-4.4.14/arch/arm/mach-iop33x/include/mach/ |
D | entry-macro.S | 24 mrceq p6, 0, \irqstat, c14, c0, 0 @ erratum 63 workaround
|
/linux-4.4.14/arch/x86/kernel/cpu/ |
D | amd.c | 584 static bool cpu_has_amd_erratum(struct cpuinfo_x86 *cpu, const int *erratum); 892 static bool cpu_has_amd_erratum(struct cpuinfo_x86 *cpu, const int *erratum) in cpu_has_amd_erratum() argument 894 int osvw_id = *erratum++; in cpu_has_amd_erratum() 914 while ((range = *erratum++)) in cpu_has_amd_erratum()
|
/linux-4.4.14/arch/arm/ |
D | Kconfig | 1046 fail. This erratum is present in 1136 (before r1p4), 1156 and 1176. 1055 r1p* erratum. If a code sequence containing an ARM/Thumb 1072 erratum. For very specific sequences of memory operations, it is 1086 erratum. Any asynchronous access to the L2 cache may encounter a 1099 (r1p0..r2p2) erratum. Under rare circumstances, a DMB instruction 1112 (r2p0..r2p2) erratum. Under certain conditions, specific to the 1127 r1p0) erratum. On affected cores the LoUIS bit field of the CLIDR 1137 r2p0) erratum. A faulty ASID can be sent to the other CPUs for the 1139 As a consequence of this erratum, some TLB entries which should be 1150 (r2p*) erratum. Under very rare conditions, a faulty [all …]
|
/linux-4.4.14/Documentation/devicetree/bindings/serial/ |
D | 8250.txt | 52 erratum A-004737 (relating to incorrect BRK handling).
|
/linux-4.4.14/Documentation/devicetree/bindings/usb/ |
D | dwc3.txt | 21 - snps,has-lpm-erratum: true when DWC3 was configured with LPM Erratum enabled
|
/linux-4.4.14/Documentation/hwmon/ |
D | k10temp | 52 the sensor may return inconsistent values (erratum 319). The driver
|
/linux-4.4.14/arch/powerpc/platforms/8xx/ |
D | Kconfig | 135 This enables a workaround for erratum CPU15 on MPC8xx chips.
|
/linux-4.4.14/arch/m68k/ifpsp060/ |
D | CHANGES | 46 4) Beta B.2 version had the following erratum:
|
/linux-4.4.14/arch/powerpc/boot/dts/fsl/ |
D | mpc8536si-post.dtsi | 173 /* mark compat w/8572 to get some erratum treatment */
|
/linux-4.4.14/arch/arm/kernel/ |
D | entry-header.S | 329 @ We must avoid clrex due to Cortex-A15 erratum #830321
|
/linux-4.4.14/arch/arm/boot/dts/ |
D | armada-370.dtsi | 350 * The Armada 370 has an erratum preventing the use of
|
/linux-4.4.14/drivers/iommu/ |
D | amd_iommu.c | 270 static bool pdev_pri_erratum(struct pci_dev *pdev, u32 erratum) in pdev_pri_erratum() argument 276 return dev_data->errata & (1 << erratum) ? true : false; in pdev_pri_erratum() 3502 void amd_iommu_enable_device_erratum(struct pci_dev *pdev, u32 erratum) in amd_iommu_enable_device_erratum() argument 3510 dev_data->errata |= (1 << erratum); in amd_iommu_enable_device_erratum()
|
/linux-4.4.14/arch/arm/mm/ |
D | Kconfig | 936 rare circumstances, due to this erratum, write data can be lost when 944 This option enables the workaround for the 753970 PL310 (r3p0) erratum.
|