1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>spi_register_board_info</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="spi.html" title="Chapter&#160;9.&#160;Serial Peripheral Interface (SPI)"><link rel="prev" href="API-struct-spi-board-info.html" title="struct spi_board_info"><link rel="next" href="API-spi-register-driver.html" title="spi_register_driver"></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">spi_register_board_info</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-struct-spi-board-info.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;9.&#160;Serial Peripheral Interface (SPI)</th><td width="20%" align="right">&#160;<a accesskey="n" href="API-spi-register-driver.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-spi-register-board-info"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>spi_register_board_info &#8212; 
2  register SPI devices for a given board
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">int <b class="fsfunc">spi_register_board_info </b>(</code></td><td>struct spi_board_info const * <var class="pdparam">info</var>, </td></tr><tr><td>&#160;</td><td>unsigned <var class="pdparam">n</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer">&#160;</div></div></div><div class="refsect1"><a name="idp1115028436"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>info</code></em></span></dt><dd><p>
4     array of chip descriptors
5    </p></dd><dt><span class="term"><em class="parameter"><code>n</code></em></span></dt><dd><p>
6     how many descriptors are provided
7    </p></dd></dl></div></div><div class="refsect1"><a name="idp1115031084"></a><h2>Context</h2><p>
8   can sleep
9</p></div><div class="refsect1"><a name="idp1115031700"></a><h2>Description</h2><p>
10   Board-specific early init code calls this (probably during arch_initcall)
11   with segments of the SPI device table.  Any device nodes are created later,
12   after the relevant parent SPI controller (bus_num) is defined.  We keep
13   this table of devices forever, so that reloading a controller driver will
14   not make Linux forget about these hard-wired devices.
15   </p><p>
16
17   Other code can also call this, e.g. a particular add-on board might provide
18   SPI devices through its expansion connector, so code initializing that board
19   would naturally declare its SPI devices.
20   </p><p>
21
22   The board info passed can safely be __initdata ... but be careful of
23   any embedded pointers (platform_data, etc), they're copied as-is.
24</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-struct-spi-board-info.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="spi.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="API-spi-register-driver.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">struct spi_board_info</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">spi_register_driver</span></td></tr></table></div></body></html>
25