Changes between Version 17 and Version 18 of io_operations

Timestamp:

Nov 3, 2016, 2:59:13 PM (8 years ago)

Author:

alain

Comment:

--

io_operations

@@ -71 +71 @@
 This function  is called by the server thread. It access to the peripheral hardware registers to start the I/O operation. Depending on the hardware peripheral implementation, can be blocking or non-blocking for the server thread. 
  * It is blocking on the THREAD_BLOCKED_DEV_ISR condition, if the hardware peripheral supports only one simultaneous I/O operation. Examples are a simple disk controller, or a text terminal controller. The blocked server thread must be re-activated by the ISR signaling completion of the current I/O operation.
- * It is non-blocking if the hardware peripheral supports several simultaneous I/O operations. Example is an AHCI compliant disk controller. It blocks only if the number of simultaneous I/O operations becomes is larger than the max number supported by the hardware.
+ * It is non-blocking if the hardware peripheral supports several simultaneous I/O operations. Example is an AHCI compliant disk controller. It blocks only if the number of simultaneous I/O operations becomes larger than the max number of concurrent operations supported by the hardware.
 The ''thread'' argument is the extended pointer on the client thread, containing the embedded command descriptor. The ''device'' argument
 is the local pointer on the device descriptor.
 
-'''diver_isr( xptr_t device )'''
+'''driver_isr( xptr_t device )'''
 
 This function is executed in the client cluster, on the core running the client thread.  It access the peripheral hardware register to get the I/O operation error status, acknowledge the IRQ, and unblock the client thread.