mirror of
https://github.com/torvalds/linux.git
synced 2024-11-02 18:21:49 +00:00
bcb1a87a8b
Use pandoc to convert documentation to ReST by calling Documentation/sphinx/tmplcvt script. Acked-by: Cornelia Huck <cornelia.huck@de.ibm.com> Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
112 lines
3.6 KiB
ReStructuredText
112 lines
3.6 KiB
ReStructuredText
===================================
|
|
Writing s390 channel device drivers
|
|
===================================
|
|
|
|
:Author: Cornelia Huck
|
|
|
|
Introduction
|
|
============
|
|
|
|
This document describes the interfaces available for device drivers that
|
|
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.
|
|
|
|
The document assumes a familarity with the technical terms associated
|
|
with the s390 channel I/O architecture. For a description of this
|
|
architecture, please refer to the "z/Architecture: Principles of
|
|
Operation", IBM publication no. SA22-7832.
|
|
|
|
While most I/O devices on a s390 system are typically driven through the
|
|
channel I/O mechanism described here, there are various other methods
|
|
(like the diag interface). These are out of the scope of this document.
|
|
|
|
Some additional information can also be found in the kernel source under
|
|
Documentation/s390/driver-model.txt.
|
|
|
|
The ccw bus
|
|
===========
|
|
|
|
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 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.
|
|
|
|
I/O functions for channel-attached devices
|
|
------------------------------------------
|
|
|
|
Some hardware structures have been translated into C structures for use
|
|
by the common I/O layer and device drivers. For more information on the
|
|
hardware structures represented here, please consult the Principles of
|
|
Operation.
|
|
|
|
.. kernel-doc:: arch/s390/include/asm/cio.h
|
|
:internal:
|
|
|
|
ccw devices
|
|
-----------
|
|
|
|
Devices that want to initiate channel I/O need to attach to the ccw bus.
|
|
Interaction with the driver core is done via the common I/O layer, which
|
|
provides the abstractions of ccw devices and ccw device drivers.
|
|
|
|
The functions that initiate or terminate channel I/O all act upon a ccw
|
|
device structure. Device drivers must not bypass those functions or
|
|
strange side effects may happen.
|
|
|
|
.. kernel-doc:: arch/s390/include/asm/ccwdev.h
|
|
:internal:
|
|
|
|
.. kernel-doc:: drivers/s390/cio/device.c
|
|
:export:
|
|
|
|
.. kernel-doc:: drivers/s390/cio/device_ops.c
|
|
:export:
|
|
|
|
The channel-measurement facility
|
|
--------------------------------
|
|
|
|
The channel-measurement facility provides a means to collect measurement
|
|
data which is made available by the channel subsystem for each channel
|
|
attached device.
|
|
|
|
.. kernel-doc:: arch/s390/include/asm/cmb.h
|
|
:internal:
|
|
|
|
.. kernel-doc:: drivers/s390/cio/cmf.c
|
|
:export:
|
|
|
|
The ccwgroup bus
|
|
================
|
|
|
|
The ccwgroup bus only contains artificial devices, created by the user.
|
|
Many networking devices (e.g. qeth) are in fact composed of several ccw
|
|
devices (like read, write and data channel for qeth). The ccwgroup bus
|
|
provides a mechanism to create a meta-device which contains those ccw
|
|
devices as slave devices and can be associated with the netdevice.
|
|
|
|
ccw group devices
|
|
-----------------
|
|
|
|
.. kernel-doc:: arch/s390/include/asm/ccwgroup.h
|
|
:internal:
|
|
|
|
.. kernel-doc:: drivers/s390/cio/ccwgroup.c
|
|
:export:
|
|
|
|
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.
|
|
|
|
.. kernel-doc:: drivers/s390/cio/airq.c
|
|
:export:
|