Changes between Version 22 and Version 23 of ioc_device_api

Timestamp:

Jan 26, 2020, 9:28:09 PM (4 years ago)

Author:

alain

Comment:

--

ioc_device_api

@@ -56 +56 @@
 Almost-mkh uses the '''synchronous''' SYNC_READ and SYNC_WRITE operations  in the ''kernel_init()'' function, or to synchronously update the FAT (both the FAT mapper in memory, and the FAT on IOC device), or the directory files on IOC device. 
 
-These synchronous operations use neither the IOC device waiting queue, nor the DEV server thread. The client thread does not deschedules : it registers the arguments in the IOC command structure embedded in the client thread descriptor, and calls directly the blocking ''ioc_driver_cmd()'' function, that executes the command and returns only when the transfer is completed. For a synchronous request, and even if the  the hardware IOC controller has a DMA capability, the ioc_driver_cmd() function is supposed to use a polling strategy to wait the transfer completion, withoutdriver
+These synchronous operations use neither the IOC device waiting queue, nor the DEV server thread. The client thread does not deschedules : it registers the arguments in the IOC command structure embedded in the client thread descriptor, and calls directly the blocking ''ioc_driver_cmd()'' function, that executes the command and returns only when the transfer is completed. For a synchronous request, and even if the  the hardware IOC controller has a DMA capability, the ioc_driver_cmd() function is supposed to use a polling strategy to wait the transfer completion, without using the IOC_IRQ.
 
 == __D) The "driver" API__ ==