Lines Matching refs:subchannel
42 get irq (subchannel) from device number and vice versa.
117 single device is uniquely identified to the system by a so called subchannel,
137 of those devices is uniquely defined by a so called subchannel by the ESA/390
138 channel subsystem. While the subchannel numbers are system generated, each
139 subchannel also takes a user defined attribute, the so called device number.
140 Both subchannel number and device number can not exceed 65535. The
153 it calls request_irq() with the device's subchannel id serving as pseudo irq
195 irq - defines the subchannel to start scanning with. This must be
196 a valid subchannel or an error is returned.
231 irq - defines the subchannel status information is to be
238 int irq; /* irq, aka. subchannel */
244 irq - subchannel.
300 -ENODEV - irq or devno don't specify a known subchannel or device
323 While some device drivers act on the irq (subchannel) only, others take user
364 irq - specifies the subchannel the device characteristic
374 -ENODEV - irq doesn't specify a valid subchannel number
409 irq - Specifies the subchannel the configuration data is to be
421 -ENODEV - irq doesn't specify a valid subchannel number
434 request_irq() to request ownership for it. This call causes the subchannel to
448 irq : specifies the subchannel the ownership is requested for
482 -EBUSY - device (subchannel) already owned
499 device, and subchannel are used interchangeably in Linux/390.
530 irq : specifies the subchannel the ownership is
595 -EBUSY - device (subchannel) already owned
611 sharing. Remember, the term interrupt level (irq), device, and subchannel are
642 irq : specifies the subchannel the ownership is requested for
656 The call to free_irq() will also cause the device (subchannel) be disabled for
667 the specified irq. However, as Linux/390 maps irqs to the device (subchannel)
669 especially if an interrupt status is found pending on the subchannel that
674 irq : specifies the subchannel to be disabled
679 -EBUSY - device (subchannel) is currently processing an I/O
682 valid subchannel
688 line can be disabled. Instead the subchannel logically representing the device
710 This function is used to enable a previously disabled device (subchannel).
715 irq : specifies the subchannel to be enabled
720 -EBUSY - device (subchannel) is currently processing an I/O
724 valid subchannel
745 irq : irq (subchannel) the I/O request is destined for
798 -ENODEV - irq doesn't specify a valid subchannel, the device is
860 The devi_id->cstat field provides the (accumulated) subchannel status :
936 may prevent the execution of any other channel program at the subchannel.
987 and dev_id->dstat that represent the accumulated subchannel and device status
1005 irq : irq (subchannel) the halt operation is requested for
1011 -ENODEV - invalid or not-operational subchannel
1023 a halt subchannel (HSCH) I/O command. For those purposes the halt_IO() command
1026 int halt_IO( int irq, /* subchannel number */
1030 irq : irq (subchannel) the halt operation is requested for
1043 -ENODEV - the irq specified doesn't specify a valid subchannel, the
1114 irq : subchannel identifying the system console device
1120 specified subchannel (irq) - status pending
1121 -ENODEV - irq doesn't specify a valid subchannel or the devive is
1137 irq : subchannel identifying the system console device