Changes between Version 9 and Version 10 of ioc_device_api

Timestamp:

Jan 21, 2020, 1:18:11 PM (4 years ago)

Author:

alain

Comment:

--

ioc_device_api

@@ -20 +20 @@
 In the IOC-RDK implementation the IOC block device is actually implemented as physical memory. This IOC-RDK implementation does not use DMA, and does not use an IRQ. The data transfer is directly executed by the ''ioc_driver_cmd()''  software function.
 
-To access the various drivers, this FBF device defines a lower-level ''driver'' API, that is detailed in section D below.
+To access the various drivers, the IOC device defines a lower-level ''driver'' API, that is detailed in section D below.
 
 All IOC device structures and access functions are defined in the [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/devices/dev_ioc.c  dev_ioc.c] et [https://www-soc.lip6.fr/trac/almos-mkh/browser/trunk/kernel/devices/dev_ioc.h dev_ioc.h] files.
@@ -27 +27 @@
 
 The IOC device '''dev_ioc_init()''' function makes the following initializations :
- * It selects a core in cluster containing the IOC chdev to execute the IOC server thread.
- * it links the IOC IRQ to the core executing the IOC server thread. 
+ * It selects a core in cluster containing the IOC chdev to execute the  server thread.
+ * it links the IOC IRQ to the core executing the server thread. 
  * it initialises the IOC specific fields of the chdev descriptor.
  * it initialises the implementation specific IOC hardware device, 
- * it initializes the specific software data structures required by a given hardware implementation.
+ * it initializes the specific software data structures required by the hardware implementation.
 It must be called by a local thread.