Searched refs:SError (Results 1 – 8 of 8) sorted by relevance
| /linux/drivers/ata/ |
| H A 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/Documentation/translations/zh_CN/arch/arm64/ |
| H A D | booting.txt | 160 所有形式的中断必须在 PSTATE.DAIF 中被屏蔽(Debug、SError、IRQ
|
| /linux/Documentation/translations/zh_TW/arch/arm64/ |
| H A D | booting.txt | 164 所有形式的中斷必須在 PSTATE.DAIF 中被屏蔽(Debug、SError、IRQ
|
| /linux/arch/arm64/boot/dts/qcom/ |
| H A D | sdm850-samsung-w737.dts | 393 /* No idea why it causes an SError when enabled */
|
| H A D | sdm850-lenovo-yoga-c630.dts | 1011 /* FIXME: qce_start triggers an SError */
|
| H A D | sdm850-huawei-matebook-e-2019.dts | 477 /* FIXME: qce_start triggers an SError */
|
| /linux/Documentation/virt/kvm/ |
| H A D | api.rst | 1195 such a way that a real device would generate a physical SError, KVM may make 1196 a virtual SError pending for that VCPU. This system error interrupt remains 1199 Running the VCPU may cause it to take a pending SError, or make an access that 1200 causes an SError to become pending. The event's description is only valid while 1206 guest-visible registers. It is not possible to 'cancel' an SError that has been 1209 A device being emulated in user-space may also wish to generate an SError. To do 1211 should be read first, to ensure no existing SError is pending. If an existing 1212 SError is pending, the architecture's 'Multiple SError interrupts' rules should 1216 SError exceptions always have an ESR value. Some CPUs have the ability to 1217 specify what the virtual SError's ESR value should be. These systems will [all …]
|
| /linux/Documentation/driver-api/ |
| H A D | libata.rst | 863 For SATA, it's strongly recommended to clear at least SError register
|