1<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> 2<HTML> 3<HEAD> 4<META http-equiv="Content-Type" content="text/html; charset=windows-1252"> 5<META name="GENERATOR" content="IBM WebSphere Studio Homepage Builder Version 7.0.1.0 for Windows"> 6<META http-equiv="Content-Style-Type" content="text/css"> 7<TITLE>PM_SetAmp*</TITLE> 8<LINK rel="stylesheet" href="../../css/nitro.css" type="text/css"> 9</HEAD> 10<BODY> 11<H1 align="left">PM_SetAmp* <IMG src="../../image/NTR.gif" width="24" height="12" border="0" align="middle"><IMG src="../../image/TWL.gif" width="24" height="12" border="0" align="middle"></H1> 12<H2>Syntax</H2> 13<DL> 14 <DD> 15 <PRE><CODE>#include <nitro/spi.h></CODE></PRE> 16 <PRE><CODE>u32 PM_SetAmp( PMAmpSwitch sw ); 17 18u32 PM_SetAmpAsync( PMAmpSwitch sw, PMCallback callback, void* arg ); 19 </CODE></PRE> 20</DL> 21<H2>Arguments</H2> 22<TABLE border="1" width="100%"> 23 <TBODY> 24 <TR> 25<TD width="13%"><SPAN class="argument">sw</SPAN></TD> 26<TD width="87%">Amp switch.</TD> 27 </TR> 28 <TR> 29<TD><SPAN class="argument">callback</SPAN></TD> 30<TD>Callback that is called when the command finishes.</TD> 31 </TR> 32 <TR> 33<TD><SPAN class="argument">arg</SPAN></TD> 34<TD>Argument that is used when calling the callback.</TD> 35 </TR> 36 </TBODY> 37</TABLE> 38<H2>Return Values</H2> 39<P>If <CODE>PM_RESULT_SUCCESS</CODE>, the command execution has succeeded (for synchronous functions), or the command was successfully sent to the ARM7 processor (for asynchronous functions).</P> 40<P>If <CODE>PM_RESULT_BUSY</CODE>, the SPI was occupied by other processing and unable to process this function.</P> 41<H2>Description</H2> 42<P>Toggles the switch of the programmable gain amp.</P> 43<P>The <SPAN class="argument">sw</SPAN> argument is a <code>PMAmpSwitch</code> enumerator type and can contain either one of the following values. 44</P> 45<TABLE border="1"> 46 <TBODY> 47 <TR> 48<TH>Value of <SPAN class="argument">sw</SPAN></TH> 49<TH>Amp Operation</TH> 50 </TR> 51 <TR> 52<TD><CODE>PM_AMP_ON</CODE></TD> 53<TD>Turns the amp ON.</TD> 54 </TR> 55 <TR> 56<TD><CODE>PM_AMP_OFF</CODE></TD> 57<TD>Turns the amp OFF.</TD> 58 </TR> 59 </TBODY> 60</TABLE> 61<P><BR>Before you use this function, initialize the PM library with the <A href="PM_Init.html"><CODE>PM_Init</CODE></A> function. (The <code>PM_Init</code> function has to be called only once. Also, when you call the <a href="../../os/init/OS_Init.html"><code>OS_Init</code></a> function, there is no need to call the <a href="PM_Init.html"><code>PM_Init</code></a> function separately because it is called from inside <code>OS_Init</code>.)</P> 62<P><FONT color="#ff0000">This function can be used from an interrupt handler. This function cannot be used in interrupt-prohibited states other than interrupt handlers.</FONT></P> 63<P> <B>Asynchronous Functions</B></P> 64<P>This function uses PXI to send the command that performs the corresponding operation in the ARM7 processor. The ARM7 side that receives that command is executed by operating the PMIC. Therefore, this function may not operate instantly after you call it. A synchronous function that waits for the operation to finish, as well as an asynchronous function that only sends commands to the ARM7, are provided. Use either of the functions depending on your operational requirements. (The asynchronous function has "Async" appended to the function name.)</P> 65<P>When an asynchronous function is called, the specified <SPAN class="argument">callback</SPAN> is called when processing on the ARM7 side finishes. The callback type <CODE>PMCallback</CODE> is defined by: </P> 66<BLOCKQUOTE> <CODE><code>typedef void ( *PMCallback )( u32 result, void* arg )</code>;</CODE></BLOCKQUOTE> 67<P> This callback is called from within the PXI interrupt handler.</P> 68<P>The callback's first argument, <SPAN class="argument">result</SPAN>, indicates the result of the command. This is either <code>PM_RESULT_SUCCESS</code> or <code>PM_RESULT_BUSY</code>. The second argument in the callback returns the value <SPAN class="argument">arg</SPAN>.</P> 69<P><B>About <CODE>PM_RESULT_BUSY</CODE></B></P> 70<P>The SPI is used for various other processes besides power management. If you call this function while another process is using it, this function sends a command to the ARM7; there, the SPI is determined to be BUSY, and <CODE>PM_RESULT_BUSY</CODE> is notified to the ARM9 without actually processing this function. Likewise, if you call this function while another PM process is running, that fact is determined on the ARM9 side and this function returns <CODE>PM_RESULT_BUSY</CODE>. (In this case, the determination is made before notification is sent to the ARM7.)</P> 71<P>Accordingly, if you want to make certain that this function will succeed, make it loop until it succeeds as shown below. (This example does not take into account mistakes such as wrong arguments.)</P> 72<BLOCKQUOTE style="background-color:#ffffcc"><B>Example:</B><BR> <CODE>while( PM_SetAmp( ... ) != PM_RESULT_SUCCESS )<BR> {<BR> }</CODE></BLOCKQUOTE> 73<P>When using the <CODE>Async</CODE> version of this function, you could do this with code similar to the following.</P> 74<BLOCKQUOTE style="background-color:#ffffcc"><B>Example</B><CODE><BR> void setResult( u32 result, void* arg )<BR> {<BR> if ( arg )<BR> {<BR> *(u32*)arg = result;<BR> }<BR> }<BR> <BR> while(1)<BR> {<BR> volatile u32 result = PM_RESULT_NONE; //A value that will not be returned<BR> <BR> while ( PM_SetAmpAsync(..., setResult, (void*)&result ) != PM_RESULT_SUCCESS )<BR> {<BR> }<BR> <BR> // Some other process<BR> otherProcess();<BR> <BR> // Wait for completion<BR> while( result == PM_RESULT_NONE )<BR> {<BR> }<BR> <BR> // Exit the loop on success<BR> if ( result == PM_RESULT_SUCCESS )<BR> {<BR> break;<BR> }<BR> }</CODE></BLOCKQUOTE> 75<H2>Internal Operation</H2> 76<P>Operates the <CODE>OP_CTL</CODE> register of the PMIC.</P> 77<H2>See Also</H2> 78<P><a href="PM_Init.html"><code>PM_Init</code></a><BR> <a href="PM_SetAmpGain.html"><code>PM_SetAmpGain*</code></a></P> 79<H2>Revision History</H2> 80<P>2008/08/23 Ended the use of <CODE>PM_RESULT_ERROR</CODE> and elaborated on <CODE>PM_RESULT_BUSY</CODE>.<BR> 2005/07/07 Elaborated on the return value <CODE>PM_RESULT_ERROR</CODE>.<BR> 2005/06/02 Clarified the origin of the call to the callback.<BR> 2004/07/31 Initial version.</P> 81<hr><p>CONFIDENTIAL</p></body> 82</HTML>