Re: COM_PowerUp & COM_PowerDown APIs



wrong forum, this is not a forum for wince.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Kovilpattian" <ramesh.kvp@xxxxxxxxx> wrote in message news:0a48a5a0-3339-4401-8a2c-55d712ff0734@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am developing the Power Management APIs in my SDIO-UART
serial driver for Windows Mobiles in WinCE 5.0 platform builder.

Here is my code for PowerDown case:


BOOL
COM_PowerDown(
HANDLE pHead /*@parm Handle to device. */
)
{
PHW_INDEP_INFO pHWIHead = (PHW_INDEP_INFO)pHead;

DbgPrint(" COM_PowerDown \r\n");

if ( pHWIHead ) {
PHWOBJ pHWObj = (PHWOBJ)pHWIHead->pHWObj;
return(pHWObj->pFuncTbl->HWPowerOff(pHWIHead->pHWHead));
} else {
return(1);
}

}

And the " HWPowerOff() " is mapped into " SerPowerOff()"

static
BOOL
SerPowerOff(
PVOID pHead // @parm PVOID returned by SerInit.
)
{
PSER_INFO pHWHead = (PSER_INFO)pHead;

DbgPrint(" + SerPowerOff \r\n");
// First, power down the UART
SL_PowerOff( pHWHead );

// And then disable our IR and 9 Pin interface
#ifdef WAKEUPONTHISDEVICE
if (pHWHead->LastDx != D3) // If we are wakeup sources do not
turn it off.
SerSetOutputMode( pHWHead, FALSE, FALSE );
#else
SerSetOutputMode( pHWHead, FALSE, FALSE );
#endif
DbgPrint(" - SerPowerOff \r\n");
return (TRUE);
}

Here I called the API " SL_PowerOff() "

in such case, i don't know what to write for this API...

VOID SL_PowerOff(PVOID pHead )
{
// --- Need to write
}


When we testing with these APIs( by putting debug messages), the
COM_PowerUp & COM_PowerDown APIs itself is not called by the OS/
Kernel. Am I need to register these APIs with any interface APIs?

If any one of you have ideas on power management APIs, please help on
this issue.

Here the problem is while sleep-mode and soft-reset , and the SDIO
card is also
inserted in SD-Slot condition, the driver is not getting loaded.

If you give any hint/document/link/code-snippet, I will be thankful.

I gone through the Microsoft Documentation.
It did not helped me.

Regards,

.



Relevant Pages

  • Re: WinCE equivalent of kernel32.lib advapi32.lib shell32.lib
    ... WinCE does support both ASCII and UNICODE string manipulation. ... Most Win32 APIs, though, only have UNICODE variant. ... >>> WinCE doesn't have any of these librararies. ...
    (microsoft.public.windowsce.app.development)
  • Re: WinCE equivalent of kernel32.lib advapi32.lib shell32.lib
    ... Most user32/kernel32/advapi32 APIs are exported from coredll for WinCE. ... The exact set of APIs is determined by the actual configuration of the OS built be the device OEM. ... You should use an SDK built for that device. ... WinCE doesn't have any of these librararies. ...
    (microsoft.public.windowsce.app.development)
  • Re: WinCE COM port APIs problem.... Its urgent.....
    ... As you might imagine, this is *very* annoying to those who read ... multiple groups. ... to implement it for WinCE device. ... The APIs which i found not supported ...
    (microsoft.public.windowsce.embedded)
  • Re: How can RS-232 communication in WDM?
    ... the mouser example does not create a handle nor does it call these apis, it creates the read/write irp on its own. ... Please do not send e-mail directly to this alias. ... ReadFile and WriteFile is WinAPI function? ...
    (microsoft.public.development.device.drivers)
  • Re: Print Fax by cmd
    ... Fax APIs - Fax Extended COM APIs. ... Look into MSDN (search for FaxDocument ... Please do not send email directly to this alias. ... > There is a command line or macro solution for print TIF file instead using ...
    (microsoft.public.windowsxp.print_fax)