s390 fixes (4/12).

s390 fixes (4/12).

Post by Martin Schwidefsk » Tue, 04 Feb 2003 17:10:23



minor changes to s390 documentation
diff -urN linux-2.5.59/Documentation/s390/driver-model.txt
linux-2.5.59-s390/Documentation/s390/driver-model.txt
--- linux-2.5.59/Documentation/s390/driver-model.txt    Fri Jan 17 03:21:34 2003
+++ linux-2.5.59-s390/Documentation/s390/driver-model.txt       Mon Feb  3 15:02:46

 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.


        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 *);

 information about the interrupt from the irb parameter.

+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. System devices
 -----------------

 xpram shows up under sys/ as 'xpram'.

-3. 'Legacy' devices
--------------------
-
-The 'legacy' bus is for devices not detected, but specified by the user.
-
+3. Other devices
+----------------

 3.1 Netiucv
 -----------

-Netiucv connections show up under legacy/ as "netiucv<ifnum>". The interface
-number is assigned sequentially at module load.
-
-user                     - the user the connection goes to.
+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.
+
+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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

s390 fixes (4/12).

Post by Martin Schwidefsk » Tue, 04 Feb 2003 22:10:11


minor changes to s390 documentation
diff -urN linux-2.5.59/Documentation/s390/driver-model.txt linux-2.5.59-s390/Documentation/s390/driver-model.txt
--- linux-2.5.59/Documentation/s390/driver-model.txt    Fri Jan 17 03:21:34 2003

 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.


        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 *);

 information about the interrupt from the irb parameter.

+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. System devices
 -----------------

 xpram shows up under sys/ as 'xpram'.

-3. 'Legacy' devices
--------------------
-
-The 'legacy' bus is for devices not detected, but specified by the user.
-
+3. Other devices
+----------------

 3.1 Netiucv
 -----------

-Netiucv connections show up under legacy/ as "netiucv<ifnum>". The interface
-number is assigned sequentially at module load.
-
-user                     - the user the connection goes to.
+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.
+
+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.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/