Lines Matching +full:layer +full:- +full:primary
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).
33 functional layer was introduced that provides generic I/O access methods to
36 The common device support layer comprises the I/O support routines defined
42 described in Documentation/arch/s390/driver-model.rst.
49 * All drivers must define a ccw_driver (see driver-model.txt) and the associated
56 * The channel device layer is gone.
96 -------------------
110 ----------------------------------
136 For internal use of the common I/O layer, these are still there. However,
145 imply specific I/O commands (channel command words - CCWs) in order to operate
154 In order to allow for easy I/O initiation the CDS layer provides a
158 ccw_device_start() routine allows to specify whether it expects the CDS layer
163 For long running I/O request to be canceled, the CDS layer provides the
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
243 expires timeout value in jiffies. The common I/O layer will terminate
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
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
324 the primary unit check source coded in sense byte 0 :
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.
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
422 is suspended. In order to resume channel program execution the CIO layer
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
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 ------------------------------