->
->
RIL also uses flow interface, including
RIL_INIT, RIL_OPEN, etc. Ten standard flow interfaces. Most of the operations are completed in ril_ioctrl
Queuecmd joins the request queue requesting the AT command, and is executed by the executor thread.
Similarly, there is a RESPONED queue.
The CRESPONSE class assumes the work in 858 At_Parser, each response as an instance of CRESPONSE.
Thread:
Cmdthreadproc
Responsible to take the command from the command queue and send it to the serial port and read the response.
ReadthreadProc, READHREADPROC
Responsible for reading parsing from serial ports to GRSPQ queue
SIMUNLOCKTHREADPROC
Handlersp sends setevent (g_hsimunlockevent);
Thread WaitForsingleObject (g_hsimunlockevent, infinite), responsible for the initialization work after Sim Ready, exiting after completion
SimReadythreadproc
Start this thread when the module is started
Launch a thread to see reason the sim is ready or not
Handlersp setEvent (M_HSIMReadyevent);
After the thread is started, the SIM Staus is READY, otherwise WaitForsingleObject (M_HSIMReadyEvent, APIIIIIIIII.dwtimeout), completes a part of the initial work.
Rhaeventthreadproc
Handle the hardware message .g_hrhaevent triggered by the underlying RHA Driver.
SwitchportsthreadProc
May be the switching and use of Multipliex Mode
ClosecomportthreadProc
Close the serial port
Acksmsthreadproc
SMS ACK. Some modules require manual ACK SMS.
RequeueThreadproc
// Place The Command Into the Command Queue
// (This May Block if the queue is full)
Wcetimeoutthread
// We Timed Out - Cancel Waitcommmevent () in Progress
HANGuPthreadproc
// EXATTIMEOUTTHREADPROC
Shutdowntimeoutthread
MonitorThreadProc
Thread Responsible for Monitoring RIL
SIMTKTHREADPROC
C wrapper for the Sim Toolkit Thread
PromptforsimandRequeueCmdproc
It seems to be used to check SIM card PIN
Datacmdtimeoutthread
When I arrived, I reminded the DATA timeout?
