Lines Matching full:modem
17 * DOC: AP/Modem QMI Handshake
19 * The AP and modem perform a "handshake" at initialization time to ensure
22 * using a service on the modem, and server to service modem requests (and
24 * complete, the AP and modem may begin IPA operation. This occurs
25 * only when the AP IPA driver, modem IPA driver, and IPA microcontroller
28 * The QMI service on the modem expects to receive an INIT_DRIVER request from
29 * the AP, which contains parameters used by the modem during initialization.
30 * The AP sends this request as soon as it is knows the modem side service
31 * is available. The modem responds to this request, and if this response
32 * contains a success result, the AP knows the modem IPA driver is ready.
34 * The modem is responsible for loading firmware on the IPA microcontroller.
35 * This occurs only during the initial modem boot. The modem sends a
38 * ready and remain so (even if the modem reboots) once it has received
42 * on the initial modem boot, but optional (but in practice does occur) on
43 * subsequent boots. The modem expects to receive a final INIT_COMPLETE
46 * and responded to an INDICATION_REGISTER request from the modem.
49 * - Whenever the AP learns the modem has booted and its IPA QMI service
50 * is available, it sends an INIT_DRIVER request to the modem. The
51 * modem supplies a success response when it is ready to operate.
52 * - On the initial boot, the modem sets up the IPA microcontroller, and
54 * - When the modem is ready to receive an INIT_COMPLETE indication from
56 * - On the initial modem boot, everything is ready when:
59 * - AP has responded to an INDICATION_REGISTER request from the modem
60 * - AP has sent an INIT_COMPLETE indication to the modem
61 * - On subsequent modem boots, everything is ready when:
65 * optional for non-initial modem boots, and have no bearing on the
79 /* Send an INIT_COMPLETE indication message to the modem */
115 * the modem is ready, and the microcontroller is ready.
117 * When the modem boots (or reboots), the handshake sequence starts
118 * with the AP sending the modem an INIT_DRIVER request. Within
127 /* We aren't ready until the modem and microcontroller are */ in ipa_qmi_ready()
139 /* The initial modem boot completed successfully */ in ipa_qmi_ready()
147 dev_err(ipa->dev, "error %d starting modem\n", ret); in ipa_qmi_ready()
150 /* All QMI clients from the modem node are gone (modem shut down or crashed). */
157 /* The modem client and server go away at the same time */ in ipa_server_bye()
160 /* initial_boot doesn't change when modem reboots */ in ipa_server_bye()
161 /* uc_ready doesn't change when modem reboots */ in ipa_server_bye()
172 * modem. This informs the AP that the modem is now ready to receive the
203 /* Respond to a DRIVER_INIT_COMPLETE request message from the modem. */
232 /* The server handles two request message types sent by the modem. */
251 /* Handle an INIT_DRIVER response message from the modem. */
260 /* The client handles one response message type sent by the modem. */
272 /* Return a pointer to an init modem driver request structure, which contains
273 * configuration parameters for the modem. The modem may be started multiple
400 /* Send an INIT_DRIVER request to the modem, and wait for it to complete. */
443 /* The modem server is now available. We will send an INIT_DRIVER request
444 * to the modem, but can't wait for it to complete in this callback thread.
476 * request on the first modem boot. It also receives the in ipa_qmi_setup()
493 * to the modem, and receiving its response message. in ipa_qmi_setup()