Lines Matching +full:build +full:- +full:only +full:- +full:delayed +full:- +full:rules
9 - Ingo Adlung
10 - Cornelia Huck
12 Copyright, IBM Corp. 1999-2002
21 processing, shared versus non-shared interrupt processing, DMA versus port
30 Operation manual (IBM Form. No. SA22-7201).
32 In order to build common device support for ESA/390 I/O interfaces, a
42 described in Documentation/arch/s390/driver-model.rst.
49 * All drivers must define a ccw_driver (see driver-model.txt) and the associated
79 interrupt handler according to the rules (flags) defined during I/O request
84 first level interrupt handler only and does not comprise a device driver
96 -------------------
110 ----------------------------------
137 device drivers should use the new calling interface via the ccw_device only.
145 imply specific I/O commands (channel command words - CCWs) in order to operate
160 only. See ccw_device_start() for more details. A device driver must never issue
169 get_ciw() - get command information word
193 ccw_device_start() - Initiate I/O Request
195 The ccw_device_start() routines is the I/O request front-end processor. All
201 driver's interrupt handler as this is related to the rules (flags) defined
245 with ERR_PTR(-ETIMEDOUT) as irb.
293 -EBUSY The device is currently processing a previous I/O request, or there is
295 -ENODEV cdev is invalid, the device is not operational or the ccw_device is
303 intparm will be set to 0 (zero). This may happen during I/O initiation or delayed
305 current (last) I/O request. In case of a delayed status notification no special
313 -ETIMEDOUT the common I/O layer terminated the request after the specified
315 -EIO the common I/O layer terminated the request due to an error state
320 sense bytes available in the extended control word irb->scsw.ecw[]. No device
339 The irb->scsw.cstat field provides the (accumulated) subchannel status :
352 The irb->scsw.dstat field provides the (accumulated) device status :
374 bottom-half, unless a non deterministically long running error recovery procedure
382 CCW_CMD_NOOP to the end of the submitted CCW chain. This will force Channel-End
383 and Device-End status to be presented together, with a single interrupt.
390 DOIO_REPORT_ALL only if the device can report intermediate interrupt
391 information prior to device-end the device driver urgently relies on. In this
397 devices always report channel-end and device-end together, with a single
398 interrupt, others present primary status (channel-end) when the channel is
399 ready for the next I/O request and secondary status (device-end) when the data
406 exploiting this feature will cause only primary status interrupts to be
418 ccw_device_resume() - Resume Channel Program Execution
437 -EBUSY status pending
438 -ENODEV cdev invalid or not-operational subchannel
439 -EINVAL resume function not applicable
440 -ENOTCONN there is no I/O request pending for completion
448 ccw_device_halt() - Halt I/O Request Processing
451 a long-running channel program or the device might require to initially issue
464 intparm interruption parameter; value is only used if no I/O
473 -EBUSY the device is currently busy, or status pending.
474 -ENODEV cdev invalid.
475 -EINVAL The device is not operational or the ccw device is not online.
480 A device driver may write a never-ending channel program by writing a channel
491 ccw_device_clear() - Terminage I/O Request Processing
511 -ENODEV cdev invalid
512 -EINVAL The device is not operational or the ccw device is not online.
516 ------------------------------