LTE modem + GPS bring-up #4

Open
opened 2026-08-20 13:19:58 +00:00 by kit · 1 comment
Owner

Feasibility assessment (2026-08-20): decent odds overall; data path is the risk.

Modem boot (good odds):

  • SM8150 integrated X24 boots via remoteproc (qcom,sm8150-mpss-pas); enable the node in the DTS.
  • Firmware: Samsung-signed modem fw + NV/EFS from existing partitions (modem, apnhlos, modemst1/2, fsg, fsc, efs) — extend the no-blob firmware link-farm.
  • QRTR/QMI already present on the rootfs (modules load).

Data path (the risk):

  • Packet data needs the IPA driver; check mainline coverage for SM8150's IPA version (neighbors sdm845/sc7180/sm8350 are supported — SM8150 may be a gap). If absent, this is a porting project.

GPS (easy once modem runs):

  • GNSS is a QMI LOC service inside the modem subsystem; ModemManager supports it natively. Config exercise, not a driver project.

Userspace: ModemManager (+ libqmi); test SIM presence, registration, then bearer.

Feasibility assessment (2026-08-20): decent odds overall; data path is the risk. **Modem boot (good odds):** - SM8150 integrated X24 boots via remoteproc (`qcom,sm8150-mpss-pas`); enable the node in the DTS. - Firmware: Samsung-signed modem fw + NV/EFS from existing partitions (`modem`, `apnhlos`, `modemst1/2`, `fsg`, `fsc`, `efs`) — extend the no-blob firmware link-farm. - QRTR/QMI already present on the rootfs (modules load). **Data path (the risk):** - Packet data needs the IPA driver; check mainline coverage for SM8150's IPA version (neighbors sdm845/sc7180/sm8350 are supported — SM8150 may be a gap). If absent, this is a porting project. **GPS (easy once modem runs):** - GNSS is a QMI LOC service inside the modem subsystem; ModemManager supports it natively. Config exercise, not a driver project. **Userspace:** ModemManager (+ libqmi); test SIM presence, registration, then bearer.
Author
Owner

Tree check (6.17):

  • remoteproc_mpss already exists upstream in sm8150.dtsi (@4080000) — modem boot really is just enable-the-node + firmware link-farm.
  • ipa_fw_mem/ipa_gsi_mem reserved-memory regions are already in sm8150.dtsi too — someone prepared for IPA.
  • IPA driver gap confirmed: drivers/net/ipa/data/ covers v3.1, v3.5.1, v4.2, v4.5, v4.7, v4.9, v4.11, v5.0, v5.5 — SM8150's v4.0 is missing. The data files are per-version config tables (~1k lines); the realistic path is transcribing a ipa_data-v4.0.c from downstream's IPA v4.0 config using v4.2 as the structural template, plus the sm8150 IPA DT node.

Order of attack: modem remoteproc boot + QMI/QRTR sanity → GPS via ModemManager QMI LOC (no IPA needed) → IPA v4.0 port for data.

Tree check (6.17): - `remoteproc_mpss` already exists upstream in sm8150.dtsi (@4080000) — modem boot really is just enable-the-node + firmware link-farm. - `ipa_fw_mem`/`ipa_gsi_mem` reserved-memory regions are already in sm8150.dtsi too — someone prepared for IPA. - **IPA driver gap confirmed**: `drivers/net/ipa/data/` covers v3.1, v3.5.1, v4.2, v4.5, v4.7, v4.9, v4.11, v5.0, v5.5 — SM8150's v4.0 is missing. The data files are per-version config tables (~1k lines); the realistic path is transcribing a `ipa_data-v4.0.c` from downstream's IPA v4.0 config using v4.2 as the structural template, plus the sm8150 IPA DT node. Order of attack: modem remoteproc boot + QMI/QRTR sanity → GPS via ModemManager QMI LOC (no IPA needed) → IPA v4.0 port for data.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
kit/linux-gts6l#4
No description provided.