Lines Matching full:modem
21 * DOC: AP/Modem QMI Handshake
23 * The AP and modem perform a "handshake" at initialization time to ensure
26 * using a service on the modem, and server to service modem requests (and
28 * complete, the AP and modem may begin IPA operation. This occurs
29 * only when the AP IPA driver, modem IPA driver, and IPA microcontroller
32 * The QMI service on the modem expects to receive an INIT_DRIVER request from
33 * the AP, which contains parameters used by the modem during initialization.
34 * The AP sends this request as soon as it is knows the modem side service
35 * is available. The modem responds to this request, and if this response
36 * contains a success result, the AP knows the modem IPA driver is ready.
38 * The modem is responsible for loading firmware on the IPA microcontroller.
39 * This occurs only during the initial modem boot. The modem sends a
42 * ready and remain so (even if the modem reboots) once it has received
46 * on the initial modem boot, but optional (but in practice does occur) on
47 * subsequent boots. The modem expects to receive a final INIT_COMPLETE
50 * and responded to an INDICATION_REGISTER request from the modem.
53 * - Whenever the AP learns the modem has booted and its IPA QMI service
54 * is available, it sends an INIT_DRIVER request to the modem. The
55 * modem supplies a success response when it is ready to operate.
56 * - On the initial boot, the modem sets up the IPA microcontroller, and
58 * - When the modem is ready to receive an INIT_COMPLETE indication from
60 * - On the initial modem boot, everything is ready when:
63 * - AP has responded to an INDICATION_REGISTER request from the modem
64 * - AP has sent an INIT_COMPLETE indication to the modem
65 * - On subsequent modem boots, everything is ready when:
69 * optional for non-initial modem boots, and have no bearing on the
83 /* Send an INIT_COMPLETE indication message to the modem */
119 * the modem is ready, and the microcontroller is ready.
121 * When the modem boots (or reboots), the handshake sequence starts
122 * with the AP sending the modem an INIT_DRIVER request. Within
131 /* We aren't ready until the modem and microcontroller are */ in ipa_qmi_ready()
143 /* The initial modem boot completed successfully */ in ipa_qmi_ready()
151 dev_err(&ipa->pdev->dev, "error %d starting modem\n", ret); in ipa_qmi_ready()
154 /* All QMI clients from the modem node are gone (modem shut down or crashed). */
161 /* The modem client and server go away at the same time */ in ipa_server_bye()
164 /* initial_boot doesn't change when modem reboots */ in ipa_server_bye()
165 /* uc_ready doesn't change when modem reboots */ in ipa_server_bye()
176 * modem. This informs the AP that the modem is now ready to receive the
207 /* Respond to a DRIVER_INIT_COMPLETE request message from the modem. */
236 /* The server handles two request message types sent by the modem. */
255 /* Handle an INIT_DRIVER response message from the modem. */
264 /* The client handles one response message type sent by the modem. */
276 /* Return a pointer to an init modem driver request structure, which contains
277 * configuration parameters for the modem. The modem may be started multiple
403 /* Send an INIT_DRIVER request to the modem, and wait for it to complete. */
446 /* The modem server is now available. We will send an INIT_DRIVER request
447 * to the modem, but can't wait for it to complete in this callback thread.
479 * request on the first modem boot. It also receives the in ipa_qmi_setup()
496 * to the modem, and receiving its response message. in ipa_qmi_setup()