Lines Matching refs:be

7 All devices which can be addressed by means of ccws are called 'CCW devices' -
30 former subchannel. The ccw devices will be moved again to a proper subchannel
34 be found under bus/ccw/devices/.
42 availability: Can be 'good' or 'boxed'; 'no path' or 'no device' for
59 There also might be additional data, for example for block devices.
68    be specified. These interfaces are also in the driver's responsibility.
76 The basic struct ccw_device and struct ccw_driver data structures can be found
108 and/or device types/models it is interested. This information can later be found
122 The functions in ccw_driver should be used in the following way:
126 	 the interrupt handler (see below) should be set here.
130 Parameters:  cdev     - the device to be probed.
138 Parameters:   cdev    - the device to be removed.
147 Parameters:   cdev	- the device to be activated. The common layer has
157 Parameters:   cdev       - the device to be deactivated. The common layer has
166 	  return code 0, the device will be deleted as usual (also when no
171 	  Device / CU to be reasonably sure if it is still the same device.
180 	      event   - the event that happened. This can be one of CIO_GONE,
183 The handler field of the struct ccw_device is meant to be set to the interrupt
213 possible). This ccwgroup device can be set online or offline just like a normal
221 ccwgroup device in the driver_data of its device struct. This field must not be
237 latter consistently due to lacking machine support (we don't need to be aware
240 status - Can be 'online' or 'offline'.
243 	 the chpid connects to. This can be used to force the kernel to re-use
244 	 a channel path the user knows to be online, but the machine hasn't
265 attribute 'online' which can be 0 or 1.