Sophie: kernel-doc-3.11.10-100.fc18 noarch

kernel-doc-3.11.10-100.fc18.noarch.rpm

<?xml version="1.0" encoding="ANSI_X3.4-1968" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968" /><title>i2c_new_dummy</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="i2c.html" title="Chapter&#160;10.&#160;I2C and SMBus Subsystem" /><link rel="prev" href="API-i2c-unregister-device.html" title="i2c_unregister_device" /><link rel="next" href="API-i2c-verify-adapter.html" title="i2c_verify_adapter" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">i2c_new_dummy</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-i2c-unregister-device.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;10.&#160;I<sup>2</sup>C and SMBus Subsystem</th><td width="20%" align="right">&#160;<a accesskey="n" href="API-i2c-verify-adapter.html">Next</a></td></tr></table><hr /></div><div class="refentry"><a id="API-i2c-new-dummy"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>i2c_new_dummy &#8212; 
     return a new i2c device bound to a dummy driver
 </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">struct i2c_client * <strong class="fsfunc">i2c_new_dummy </strong>(</code></td><td>struct i2c_adapter * <var class="pdparam">adapter</var>, </td></tr><tr><td>&#160;</td><td>u16 <var class="pdparam">address</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer">&#160;</div></div></div><div class="refsect1"><a id="idm140404952662400"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>adapter</code></em></span></dt><dd><p>
     the adapter managing the device
    </p></dd><dt><span class="term"><em class="parameter"><code>address</code></em></span></dt><dd><p>
     seven bit address to be used
    </p></dd></dl></div></div><div class="refsect1"><a id="idm140404952657168"></a><h2>Context</h2><p>
   can sleep
</p></div><div class="refsect1"><a id="idm140404952655952"></a><h2>Description</h2><p>
   This returns an I2C client bound to the <span class="quote">&#8220;<span class="quote">dummy</span>&#8221;</span> driver, intended for use
   with devices that consume multiple addresses.  Examples of such chips
   include various EEPROMS (like 24c04 and 24c08 models).
   </p><p>

   These dummy devices have two main uses.  First, most I2C and SMBus calls
   except <code class="function">i2c_transfer</code> need a client handle; the dummy will be that handle.
   And second, this prevents the specified address from being bound to a
   different driver.
   </p><p>

   This returns the new i2c client, which should be saved for later use with
   <code class="function">i2c_unregister_device</code>; or NULL to indicate an error.
</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-i2c-unregister-device.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="i2c.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="API-i2c-verify-adapter.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">i2c_unregister_device</span>&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;<span class="phrase">i2c_verify_adapter</span></td></tr></table></div></body></html>