Lines Matching refs:device

23 In this example, device 0815 is accessed via subchannel 0 in subchannel set 0,
24 device 4711 via subchannel 1 in subchannel set 0, and subchannel 2 is a non-I/O
29 if they are displaced by another ccw device becoming operational on their
33 You should address a ccw device via its bus id (e.g. 0.0.4711); the device can
40 devtype:    The device type / model, if applicable.
42 availability: Can be 'good' or 'boxed'; 'no path' or 'no device' for
45 online:     An interface to set the device online and offline.
46 	    In the special case of the device being disconnected (see the
48 	    the device.
50 The device drivers can add entries to export per-device data and interfaces.
55 chpids:	    Via which chpids the device is connected.
62 1.1 Bringing up a ccw device
69 b. After a. has been performed, if necessary, the device is finally brought up
85 	struct device dev;		
105 is not available to the device driver.
108 and/or device types/models it is interested. This information can later be found
123 probe:   This function is called by the device layer for each device the driver
130 Parameters:  cdev     - the device to be probed.
133 remove:  This function is called by the device layer upon removal of the driver,
134 	 the device or the module. The driver should perform cleanups here.
138 Parameters:   cdev    - the device to be removed.
141 set_online: This function is called by the common I/O layer when the device is
143 	    setup and activate the device here.
147 Parameters:   cdev	- the device to be activated. The common layer has
148 			  verified that the device is not already online.
151 set_offline: This function is called by the common I/O layer when the device is
153 	     down the device, but not de-allocate its private data.
157 Parameters:   cdev       - the device to be deactivated. The common layer has
158 			   verified that the device is online.
162 	of the device.
164 	* In online state, device detached (CIO_GONE) or last path gone
165 	  (CIO_NO_PATH). The driver must return !0 to keep the device; for
166 	  return code 0, the device will be deleted as usual (also when no
168 	  device, it is moved into disconnected state.
169 	* In disconnected state, device operational again (CIO_OPER). The
170 	  common I/O layer performs some sanity checks on device number and
171 	  Device / CU to be reasonably sure if it is still the same device.
172 	  If not, the old device is removed and a new one registered. By the
173 	  return code of the notify function the device driver signals if it
174 	  wants the device back: !0 for keeping, 0 to make the device being
179 Parameters:   cdev    - the device whose state changed.
184 handler for the device. In order to accommodate drivers which use several 
194 Parameters:	dev	- the device the handler is called for
195 		intparm - the intparm which allows the device driver to identify
201 The device driver is called from the common ccw_device layer and can retrieve 
212 this attributes creates a ccwgroup device consisting of these ccw devices (if
213 possible). This ccwgroup device can be set online or offline just like a normal
214 ccw device.
216 Each ccwgroup device also provides an 'ungroup' attribute to destroy the device
220 A ccw device which is a member of a ccwgroup device carries a pointer to the
221 ccwgroup device in the driver_data of its device struct. This field must not be
222 touched by the driver - it should use the ccwgroup device's driver_data for its