[PATCH] s390: documentation.

minor changes to s390 documentation

Documentation/s390/driver-model.txt

@@ -51,13 +51,10 @@ There also might be additional data, for example for block devices.
 
 This is done in several steps.
 
-a. Some drivers need several ccw devices to make up one device. This drivers
-   provide a 'chaining' interface (driver dependend) which allows to specify
-   which ccw devices form a device.
-b. Each driver provides one or more parameter interfaces where parameters can
+a. Each driver can provide one or more parameter interfaces where parameters can
    be specified. These interfaces are also in the driver's responsibility.
-c. After a. and b. have been performed, if neccessary, the device is finally
-   brought up via the 'online' interface.
+b. After a. has been performed, if neccessary, the device is finally brought up
+   via the 'online' interface.
 
 
 1.2 Writing a driver for ccw devices
@@ -84,7 +81,6 @@ struct ccw_driver {
 	struct ccw_device_id *ids;	
 	int (*probe) (struct ccw_device *); 
 	int (*remove) (struct ccw_device *);
-	void (*release) (struct ccw_driver *); 
 	int (*set_online) (struct ccw_device *);
 	int (*set_offline) (struct ccw_device *);
 	struct device_driver driver;
@@ -170,38 +166,56 @@ The device driver is called from the common ccw_device layer and can retrieve
 information about the interrupt from the irb parameter.
 
 
-2. System devices
------------------
+1.3 ccwgroup devices
+--------------------
+
+The ccwgroup mechanism is designed to handle devices consisting of multiple ccw
+devices, like lcs or ctc.
+
+The ccw driver provides a 'group' attribute. Piping bus ids of ccw devices to
+this attributes creates a ccwgroup device consisting of these ccw devices (if
+possible). This ccwgroup device can be set online or offline just like a normal
+ccw device.
+
+To implement a ccwgroup driver, please refer to include/asm/ccwgroup.h. Keep in
+mind that most drivers will need to implement both a ccwgroup and a ccw driver
+(unless you have a meta ccw driver, like cu3088 for lcs and ctc).
+
 
-2.1 Channel paths
+2. Channel paths
 -----------------
 
-Every channel path is represented under sys/ as channel_path<nr>. (Unfortunately,
-<nr> is in decimal, which may look unfamiliar.)
+Channel paths show up, like subchannels, under the channel subsystem root (css0)
+and are called 'chp<chpid>'. They have no driver and do not belong to any bus.
 
 status - Can be 'online', 'logically offline' or 'n/a'.
 	 Piping 'on' or 'off' sets the chpid logically online/offline.
 
 
-2.2 xpram 
----------
+3. System devices
+-----------------
 
-xpram shows up under sys/ as 'xpram'.
+Note: cpus may yet be added here.
 
+3.1 xpram 
+---------
 
-3. 'Legacy' devices
--------------------
+xpram shows up under sys/ as 'xpram'.
 
-The 'legacy' bus is for devices not detected, but specified by the user.
 
+4. Other devices
+----------------
 
-3.1 Netiucv
+4.1 Netiucv
 -----------
 
-Netiucv connections show up under legacy/ as "netiucv<ifnum>". The interface
-number is assigned sequentially at module load.
+The netiucv driver creates an attribute 'connection' under
+bus/iucv/drivers/NETIUCV. Piping to this attibute creates a new netiucv
+connection to the specified host.
 
-user			  - the user the connection goes to.
+Netiucv connections show up under devices/iucv/ as "netiucv<ifnum>". The interface
+number is assigned sequentially to the connections defined via the 'connection'
+attribute. 'name' shows the connection partner.
 
 buffer			  - maximum buffer size.
 			    Pipe to it to change buffer size.