40 | | WARNING 1 : The PIC device in this list has a special role: it does NOT perform I/O operations, but is used as a configurable interrupt router to dynamically link a peripheral channel interrupt to a given core. Therefore, the functions defined by the PIC API are service functions, called by the other devices functions. These PIC functions don't use the waiting queue implemented in the generic device descriptor, but call directly the PIC driver. |
41 | | |
42 | | WARNING 2 : The MMC and DMA devices are ''internal'' peripherals, replicated in all cluster. They are can be used by the kernel - when available in the hardware architecture - for instrumentation purposes, or to accelerate the memory copies. |
| 40 | * The '''PIC''' device has a special role: it does NOT perform I/O operations, but is used as a configurable interrupt router to dynamically link a peripheral channel interrupt to a given core. Therefore, the functions defined by the PIC API are service functions, called by the other devices functions. The PIC access functions don't use the waiting queue implemented in the generic device descriptor, but call directly the PIC driver. |
| 41 | * The '''MMC''' devices are ''internal'' peripherals, replicated in all cluster. They are can be used by the kernel - when available in the hardware architecture - for instrumentation purposes, The MMC access functions don't use the waiting queue implemented in the generic device descriptor, but call directly the MMC driver. |
| 42 | * The '''DMA''' devices are ''internal'' peripherals, replicated in all cluster. They are can be used by the kernel - when available in the hardware architecture - to accelerate the memory copies. |