Changes between Version 10 and Version 11 of icu_device_api

Timestamp:

Nov 4, 2016, 1:21:59 PM (8 years ago)

Author:

alain

Comment:

--

icu_device_api

@@ -23 +23 @@
  1. It is capable to return the highest priority active IRQ of each type. The priority scheme depends on the ICU device implementation.
 
-To select the ISR to be executed for a given IRQ routed to a given core, the ICU device uses three interrupts vectors, implemented as three arrays (HWI/WTI/PTI) stored in the core descriptor.
-Each entry in one interrupt vector array (defining one IRQ type and index) contains an extended pointer on the device descriptor that is the "source" of the interrupt. This device descriptor contains a link to the ISR to be executed to handle the interrupt event. 
+To select the ISR to be executed for a given IRQ routed to a given core, ALMOS-MK uses three interrupts vectors, implemented as three arrays (HWI/WTI/PTI) stored in the core descriptor.
+Each entry in one interrupt vector array contains an extended pointer on the device descriptor that is the "source" of the interrupt. This device descriptor contains a link to the ISR to be executed to handle the interrupt event. 
 
-As the generic ICU device works for a single client (the local kernel instance), it does not use the device descriptor  queue.
-All commands are immediately executed, using the device lock to get exclusive access to the ICU device state.
+As the generic ICU device works for a single client (the local kernel instance), it does not use the device descriptor  queue. All commands are immediately executed, using the device lock to get exclusive access to the ICU device state.
 
 == B) Access Functions ==