/** @file\r
Abstraction for hardware based interrupt routine\r
- \r
+\r
On non IA-32 systems it is common to have a single hardware interrupt vector\r
and a 2nd layer of software that routes the interrupt handlers based on the\r
- interrupt source. This protocol enables this routing. The driver implementing \r
- this protocol is responsible for clearing the pending interrupt in the \r
- interrupt routing hardware. The HARDWARE_INTERRUPT_HANDLER is responsible \r
+ interrupt source. This protocol enables this routing. The driver implementing\r
+ this protocol is responsible for clearing the pending interrupt in the\r
+ interrupt routing hardware. The HARDWARE_INTERRUPT_HANDLER is responsible\r
for clearing interrupt sources from individual devices.\r
\r
\r
@param Source Source of the interrupt. Hardware routing off a specific platform defines\r
what source means.\r
@param SystemContext Pointer to system register context. Mostly used by debuggers and will\r
- update the system context after the return from the interrupt if \r
+ update the system context after the return from the interrupt if\r
modified. Don't change these values unless you know what you are doing\r
\r
**/\r
VOID\r
(EFIAPI *HARDWARE_INTERRUPT_HANDLER) (\r
IN HARDWARE_INTERRUPT_SOURCE Source,\r
- IN EFI_SYSTEM_CONTEXT SystemContext \r
+ IN EFI_SYSTEM_CONTEXT SystemContext\r
);\r
\r
\r
(EFIAPI *HARDWARE_INTERRUPT_INTERRUPT_STATE) (\r
IN EFI_HARDWARE_INTERRUPT_PROTOCOL *This,\r
IN HARDWARE_INTERRUPT_SOURCE Source,\r
- IN BOOLEAN *InterruptState \r
+ IN BOOLEAN *InterruptState\r
);\r
\r
/**\r
- Signal to the hardware that the End Of Intrrupt state \r
+ Signal to the hardware that the End Of Intrrupt state\r
has been reached.\r
\r
@param This Instance pointer for this protocol\r