X-Git-Url: http://pileus.org/git/?a=blobdiff_plain;f=Documentation%2FDocBook%2Fs390-drivers.tmpl;h=4acc73240a6d536ef044bf1dfc5a2abd6ae4296f;hb=7dc9719682ce8c46215bc9a1bdc7ee0c38ada94b;hp=254e769282a46ed98ca6b8ddd1e5935fca70c933;hpb=2843483d2eb02ad104edbe8b2429fb6a39d25063;p=~andy%2Flinux
diff --git a/Documentation/DocBook/s390-drivers.tmpl b/Documentation/DocBook/s390-drivers.tmpl
index 254e769282a..4acc73240a6 100644
--- a/Documentation/DocBook/s390-drivers.tmpl
+++ b/Documentation/DocBook/s390-drivers.tmpl
@@ -59,7 +59,7 @@
Introduction
This document describes the interfaces available for device drivers that
- drive s390 based channel attached devices. This includes interfaces for
+ drive s390 based channel attached I/O devices. This includes interfaces for
interaction with the hardware and interfaces for interacting with the
common driver core. Those interfaces are provided by the s390 common I/O
layer.
@@ -86,9 +86,10 @@
The ccw bus typically contains the majority of devices available to
a s390 system. Named after the channel command word (ccw), the basic
command structure used to address its devices, the ccw bus contains
- so-called channel attached devices. They are addressed via subchannels,
- visible on the css bus. A device driver, however, will never interact
- with the subchannel directly, but only via the device on the ccw bus,
+ so-called channel attached devices. They are addressed via I/O
+ subchannels, visible on the css bus. A device driver for
+ channel-attached devices, however, will never interact with the
+ subchannel directly, but only via the I/O device on the ccw bus,
the ccw device.
@@ -146,4 +147,15 @@
+
+ Generic interfaces
+
+ Some interfaces are available to other drivers that do not necessarily
+ have anything to do with the busses described above, but still are
+ indirectly using basic infrastructure in the common I/O layer.
+ One example is the support for adapter interrupts.
+
+!Edrivers/s390/cio/airq.c
+
+