Searched refs:SError (Results 1 – 9 of 9) sorted by relevance
| /linux-6.12.1/drivers/ata/ |
| D | sata_fsl.c | 1057 u32 hstatus, dereg=0, cereg = 0, SError = 0; in sata_fsl_error_intr() local
1076 sata_fsl_scr_read(&ap->link, SCR_ERROR, &SError); in sata_fsl_error_intr()
1077 if (unlikely(SError & 0xFFFF0000)) in sata_fsl_error_intr()
1078 sata_fsl_scr_write(&ap->link, SCR_ERROR, SError); in sata_fsl_error_intr()
1081 hstatus, cereg, ioread32(hcr_base + DE), SError); in sata_fsl_error_intr()
1185 u32 SError; in sata_fsl_host_intr() local
1191 sata_fsl_scr_read(&ap->link, SCR_ERROR, &SError); in sata_fsl_host_intr()
1212 SError); in sata_fsl_host_intr()
1222 if (unlikely(SError & 0xFFFF0000)) { in sata_fsl_host_intr()
1223 ata_port_dbg(ap, "serror @host_intr : 0x%x\n", SError); in sata_fsl_host_intr()
|
| /linux-6.12.1/Documentation/translations/zh_CN/arch/arm64/ |
| D | booting.txt | 160 所有形式的中断必须在 PSTATE.DAIF 中被屏蔽（Debug、SError、IRQ
|
| /linux-6.12.1/Documentation/translations/zh_TW/arch/arm64/ |
| D | booting.txt | 164 所有形式的中斷必須在 PSTATE.DAIF 中被屏蔽（Debug、SError、IRQ
|
| /linux-6.12.1/arch/arm64/boot/dts/qcom/ |
| D | sdm850-samsung-w737.dts | 393 /* No idea why it causes an SError when enabled */
|
| D | sdm850-lenovo-yoga-c630.dts | 917 /* FIXME: qce_start triggers an SError */
|
| /linux-6.12.1/Documentation/arch/arm64/ |
| D | booting.rst | 169 All forms of interrupts must be masked in PSTATE.DAIF (Debug, SError,
|
| /linux-6.12.1/Documentation/virt/kvm/ |
| D | api.rst | 1178 such a way that a real device would generate a physical SError, KVM may make
1179 a virtual SError pending for that VCPU. This system error interrupt remains
1182 Running the VCPU may cause it to take a pending SError, or make an access that
1183 causes an SError to become pending. The event's description is only valid while
1189 guest-visible registers. It is not possible to 'cancel' an SError that has been
1192 A device being emulated in user-space may also wish to generate an SError. To do
1194 should be read first, to ensure no existing SError is pending. If an existing
1195 SError is pending, the architecture's 'Multiple SError interrupts' rules should
1199 SError exceptions always have an ESR value. Some CPUs have the ability to
1200 specify what the virtual SError's ESR value should be. These systems will
[all …]
|
| /linux-6.12.1/arch/arm64/tools/ |
| D | sysreg | 2173 0b0010 SError
|
| /linux-6.12.1/Documentation/driver-api/ |
| D | libata.rst | 856 For SATA, it's strongly recommended to clear at least SError register
|