Changes between Version 6 and Version 7 of icu_device_api

Timestamp:

Nov 4, 2016, 11:58:40 AM (7 years ago)

Author:

alain

Comment:

--

icu_device_api

@@ -5 +5 @@
  == A) General principles ==
 
-The ICU (Interrupt Controller Unit) generic device describes an ''internal'' peripheral, acting in all clusters containing cores.
-He is in charge of concentrating all IRQs (interrupt request)  generated by the - internal or external - peripherals to signal the completion of the  I/O operation started by a core in a given cluster. Each IRQ should be routed to the core that started the I/O operation. The ICU device must also help the kernel to select the ISR (Interrupt Service Routine) that must be executed by the target core.
+The ICU (Interrupt Controller Unit) device describes an ''internal'' peripheral, acting in all clusters containing cores.
+He is in charge of concentrating all IRQs (interrupt requests)  generated by a peripheral to signal the completion of an  I/O operation. Each IRQ should be routed to the core that started the I/O operation. The ICU device must also help the kernel to select the ISR (Interrupt Service Routine) that must be executed by the target core.
 
 This component can be implemented as a dedicated hardware, centralized or distributed in all clusters, or emulated in software,
 as long as it implements the API defined below.
 
-ALMOS-MK defines three types of IRQs, that are concentrated by the generic ICU device:
+ALMOS-MK defines three types of IRQs, that are handled by this generic ICU device:
 
  * '''HWI''' : The HardWare Interrupts are generated by a local internal peripheral. They are connected to the local ICU, to be routed to a given local core.