.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "Z8530_INTERRUPT" "" "06 October 2005" "" ""

.SH NAME
z8530_interrupt \- Handle an interrupt from a Z8530
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
irqreturn_t z8530_interrupt  (int \fIirq\fB, void * \fIdev_id\fB, struct pt_regs * \fIregs\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIirq\fB\fR
Interrupt number
.TP
\fB\fIdev_id\fB\fR
The Z8530 device that is interrupting.
.TP
\fB\fIregs\fB\fR
unused
.SH "DESCRIPTION"
.PP
A Z85[2]30 device has stuck its hand in the air for attention.
We scan both the channels on the chip for events and then call
the channel specific call backs for each channel that has events.
We have to use callback functions because the two channels can be
in different modes.
.PP
Locking is done for the handlers. Note that locking is done
at the chip level (the 5uS delay issue is per chip not per
channel). c->lock for both channels points to dev->lock