Lines Matching refs:do_IO

66 do_IO()	
80    initiation with do_IO().
85 callable interface. Instead, the functional description of do_IO() also
159 In order to allow for easy I/O initiation the CDS layer provides a do_IO()
162 an I/O request on behalf of the device driver. The do_IO() routine allows for
166 to allow for overlapped I/O processing. See do_IO() for more details. A device
475 won't be used during request_irq() processing. See do_IO() for a functional
559 won't be used during request_irq() processing. See do_IO() for a functional 
728 do_IO() - Initiate I/O Request
730 The do_IO() routines is the I/O request front-end processor. All device driver
732 ESA/390 I/O commands itself. Instead the do_IO() routine provides all
737 with the associated I/O request when calling do_IO().
739 int do_IO( int            irq,
793 The do_IO() function returns :
815 do_IO() returned with successful completion.
822                            call to do_IO()
828                            delayed, after do_IO() or halt_IO() have
892 Prior to call do_IO() the device driver must assure disabled state, i.e. the 
898 environment an interrupt might be presented prior to the do_IO() routine
915 The device driver is allowed to issue the next do_IO() call from within its
920 must not try to obtain it again when calling do_IO() or we end in a deadlock
922 do_IO() if the handler itself can be entered recursively if do_IO() e.g. finds
976 successful completion for all overlapping do_IO() requests that have been
988 information gathered since do_IO() request initiation.
1016 Please have a look at the do_IO()  usage notes for more details on suspended 
1040           operation : do_IO() with flag DOIO_WAIT_FOR_INTERRUPT
1071 do_IO() or halt_IO() from anywhere but the device interrupt handler (where
1084 do_IO() or halt_IO() from anywhere but the device interrupt handler (where