platform/surface: re-lift SP11 battery-provider containment

[ooaklee]

Summary

Keep Qualcomm battmgr as the authoritative battery and mains provider on Surface Pro 11 by omitting duplicate SAM battery and AC nodes.

Containment and provenance

• only ssam_node_group_sp11 changes
• no shared battery driver or non-SP11 registry group changes
• other Surface devices retain their SAM battery and AC nodes
• the battery commit preserves Justin White as author and his original sign-off; the AC correction retains Leon Silcott as author
• stable patch IDs match the focused platform/surface: omit duplicate SP11 SAM power supplies jglathe/linux_ms_dev_kit#90 commits

Historical pre-sync focused software evidence

At 9cc0b14b6ed7:

• beta integration validator: pass
• strict checkpatch: 0 errors
• git diff --check: pass
• clean case-sensitive ARM64 ubuntu_x1e_defconfig W=1 build of surface_aggregator_registry.o: pass

Current re-lift verification

The two-commit series was re-lifted unchanged onto current beta bf631f9, producing head 4eadf8d. Ordered stable patch IDs, author identities, and subjects match the pre-sync series, and git range-diff pairs both commits exactly. GitHub CI and a local detached-head rerun of the exact-current-head integration check pass. A fresh case-sensitive ARM64 W=1 build of surface_aggregator_registry.o passes at exact head 4eadf8d and tree e970d92e3744.

Blocking hardware gates

Both SP11 variants must expose only Qualcomm battery/AC providers with live telemetry across plug/unplug, suspend/resume, and reboot. A non-SP11 Surface must retain SAM battery and AC providers.

This PR intentionally remains draft.

Qualified-source replacement note

The hardware-qualified source achieved the same provider outcome with an of_machine_is_compatible("microsoft,denali") early return inside the shared surface_battery probe. This relift deliberately does not carry that shared-driver change: removing only the SP11 registry nodes prevents those SAM devices from being created while leaving every other Surface probe path untouched. The final-tree coverage audit therefore classifies drivers/power/supply/surface_battery.c as a guarded replacement, not a lost behavior.

[ooaklee]

WITHDRAWN: aggregate qualification candidate

Do not install or hardware-test 7.2.2-sp11beta1 or candidate
80ecee88b749d7324e1274c0a1cf6dfd752fddfa.

A final-tree comparison against the hardware-qualified
sp11/integration-7.2.x source found active camera behavior missing from that
candidate: VFE680 MIPI RAW write-client mode, CSID680 crop/drop-engine
containment, and CAMSS partial stream-start unwind. Compile, schema, and package
success did not detect this runtime-semantic gap. A focused repair and a new,
uniquely named candidate are required before hardware testing.

This correction supersedes the build notice below; the old results are retained
only as reproducibility evidence.

---

Historical aggregate build record (withdrawn)

The held qualification branch sp11/ubuntu-qcom-x1e-7.2.y-beta-qualification
at 80ecee88b749 combined the provisional beta with draft PRs #36–#39 in
dependency order.

• clean full ARM64 ubuntu_x1e_defconfig build: passed through modules,
  MODPOST, vmlinux, Image, vmlinuz, and vmlinuz.efi
• aggregate touched-object W=1 build: passed
• X1E/OLED, X1P/LCD, and representative non-SP11 DTBs: passed
• all six changed binding families: passed; only two unrelated pre-existing
  schema warnings remained
• complete bindeb-pkg: passed with unique kernel release
  7.2.2-sp11beta1
• image package SHA-256:
  acc6368a15b5fcb4e0eb2059e5c401b14e87a5c2b3178fea73acdeed11f75ee4

The #37/#38 registry overlap was combined without simplifying either feature:
SP11 SAM battery/AC nodes remained omitted, and only the SP11 profile/fan nodes
were added.

These are historical composition and packaging results, not hardware
acceptance. They do not change any PR's draft status or waive any listed device,
non-SP11, userspace, provenance, or contributor-attestation gate.

[ooaklee]

Aggregate hardware qualification is tracked in #41 at exact candidate
08249986a3f4efd7e0826c29e830601bfde928ed (tree
da7479fbffe997cdc980a147b4cb929d71253185).

This topic remains draft. A green aggregate build or CI result does not satisfy
its topic-specific hardware, dependency, provenance, or non-SP11 gates. Record
full-system evidence in #41 and link the relevant result back here before this
topic leaves draft state.

PR #41 is a test-only aggregate and must close without merge.