Sophie

Sophie

distrib > CentOS > 6 > i386 > by-pkgid > 2c51d8eb79f8810ada971ee8c30ce1e5 > files > 1013

kernel-doc-2.6.32-71.14.1.el6.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>struct i2c_board_info</title><meta name="generator" content="DocBook XSL Stylesheets V1.75.2" /><link rel="home" href="index.html" title="Linux Device Drivers" /><link rel="up" href="ch10.html" title="Chapter&#160;10.&#160;I2C and SMBus Subsystem" /><link rel="prev" href="re755.html" title="struct i2c_client" /><link rel="next" href="re757.html" title="I2C_BOARD_INFO" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span>struct i2c_board_info</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="re755.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="re757.html">Next</a></td></tr></table><hr /></div><div class="refentry" title="struct i2c_board_info"><a id="API-struct-i2c-board-info"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>struct i2c_board_info &#8212; 
     template for device creation
 </p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><pre class="programlisting">
struct i2c_board_info {
  char type[I2C_NAME_SIZE];
  unsigned short flags;
  unsigned short addr;
  void * platform_data;
  struct dev_archdata * archdata;
  int irq;
};  </pre></div><div class="refsect1" title="Members"><a id="id2708791"></a><h2>Members</h2><div class="variablelist"><dl><dt><span class="term">type[I2C_NAME_SIZE]</span></dt><dd><p>
   chip type, to initialize i2c_client.name
      </p></dd><dt><span class="term">flags</span></dt><dd><p>
   to initialize i2c_client.flags
      </p></dd><dt><span class="term">addr</span></dt><dd><p>
   stored in i2c_client.addr
      </p></dd><dt><span class="term">platform_data</span></dt><dd><p>
   stored in i2c_client.dev.platform_data
      </p></dd><dt><span class="term">archdata</span></dt><dd><p>
   copied into i2c_client.dev.archdata
      </p></dd><dt><span class="term">irq</span></dt><dd><p>
   stored in i2c_client.irq
      </p></dd></dl></div></div><div class="refsect1" title="Description"><a id="id2708871"></a><h2>Description</h2><p>
   I2C doesn't actually support hardware probing, although controllers and
   devices may be able to use I2C_SMBUS_QUICK to tell whether or not there's
   a device at a given address.  Drivers commonly need more information than
   that, such as chip type, configuration, associated IRQ, and so on.
   </p><p>

   i2c_board_info is used to build tables of information listing I2C devices
   that are present.  This information is used to grow the driver model tree.
   For mainboards this is done statically using <code class="function">i2c_register_board_info</code>;
   bus numbers identify adapters that aren't yet available.  For add-on boards,
   <code class="function">i2c_new_device</code> does this dynamically with the adapter already known.
</p></div></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="re755.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="ch10.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="re757.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span>struct i2c_client</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>I2C_BOARD_INFO</span></td></tr></table></div></body></html>