1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>mpt_interrupt</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Linux Device Drivers"><link rel="up" href="message_devices.html#idp1111130356" title="Fusion message devices"><link rel="prev" href="API-mpt-fault-reset-work.html" title="mpt_fault_reset_work"><link rel="next" href="API-mptbase-reply.html" title="mptbase_reply"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">mpt_interrupt</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-mpt-fault-reset-work.html">Prev</a> </td><th width="60%" align="center">Fusion message devices</th><td width="20%" align="right"> <a accesskey="n" href="API-mptbase-reply.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-mpt-interrupt"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>mpt_interrupt — 2 MPT adapter (IOC) specific interrupt handler. 3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" class="funcprototype-table" summary="Function synopsis" style="cellspacing: 0; cellpadding: 0;"><tr><td><code class="funcdef">irqreturn_t <b class="fsfunc">mpt_interrupt </b>(</code></td><td>int <var class="pdparam">irq</var>, </td></tr><tr><td> </td><td>void * <var class="pdparam">bus_id</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer"> </div></div></div><div class="refsect1"><a name="idp1111450332"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>irq</code></em></span></dt><dd><p> 4 irq number (not used) 5 </p></dd><dt><span class="term"><em class="parameter"><code>bus_id</code></em></span></dt><dd><p> 6 bus identifier cookie == pointer to MPT_ADAPTER structure 7 </p></dd></dl></div></div><div class="refsect1"><a name="idp1111452996"></a><h2>Description</h2><p> 8 This routine is registered via the <code class="function">request_irq</code> kernel API call, 9 and handles all interrupts generated from a specific MPT adapter 10 (also referred to as a IO Controller or IOC). 11 This routine must clear the interrupt from the adapter and does 12 so by reading the reply FIFO. Multiple replies may be processed 13 per single call to this routine. 14 </p><p> 15 16 This routine handles register-level access of the adapter but 17 dispatches (calls) a protocol-specific callback routine to handle 18 the protocol-specific details of the MPT request completion. 19</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-mpt-fault-reset-work.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="message_devices.html#idp1111130356">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="API-mptbase-reply.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">mpt_fault_reset_work</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> <span class="phrase">mptbase_reply</span></td></tr></table></div></body></html> 20