Repository navigation
Conversation
The revised PCI power-control path requires regulator-wlan, which the historical controller overlay cannot enable. Add a separately named reviewed controller overlay so the older pinned bring-up path stays reproducible. Document the w0/w1/w2 overlay combinations and their runtime limits. Offline property comparisons against both silicon DTs in each saved trial image confirm exactly the intended status changes, with the historical overlay as a negative control. No descriptor or automatic startup is changed. Assisted-by: OpenAI Codex
e34a930 to
7341c49
Compare
|
Thank you, Chris, this is what I asked for on kernel #230. The reviewed controller overlay enables For the next hardware run, the runbook will need the usual Expect/Pass, stop condition, rollback and risk for each of the three stages. Your new section already lists the gates it should carry. |
What and why
The reviewed GS101 PCI power-control path needs
regulator-wlan, but the historicalwifi-controlleroverlay enables only the PHY and PCIe controller. Addwifi-reviewed-controllerwith the regulator, PHY and controller status switches, and document the w0/w1/w2 combinations with the existing pool and endpoint overlays. This follows the request on kernel #230.Keep the separately pinned historical path reproducible: kernel
c934e316bhas no regulator-wlan node, so the historical controller overlay's behavior remains unchanged. No descriptor, package or automatic startup enables the new overlay.The November 13 trials edited DT status properties directly. These source overlays reproduce those exact DT changes; the new overlay file itself has not been booted.
Device and build
7.3.0-rc6-omamobile-bluejay-review-20261111, signed integration720a495233734e4328a09c33c095d72a8291e1c4.Checks (no phone needed)
git diff --checkpass.dtc -@; descriptor overlay checks pass.tests/allandtests/packagespass locally. Independent review found no remaining blocker. Hosted CI will run on the published head.On the phone: prior evidence and limits
The recorded w0 pool check passed; w1 linked on try 1 to
14e4:4441with the endpoint unbound and no firmware loaded. The separate w2 trial verified restricted DMA below 4 GiB, DHCP and interface-bound HTTPS (200, 16,932 bytes), with IRQ 725 to 744 and zero observed oversize drops. These existing reports are on kernel #227 and #228.No fresh phone-smoke or hardware run was performed for this reproducibility-only change. Future runs require their own exact module/root/recovery/watchdog/logging gates; the historical startup helpers still refuse this revised kernel. No suspend, roaming, hotspot, endurance, native-panel or release-installer qualification is inferred. No images, firmware, captures or identifying data are included.
Upstream baseline refresh
The first hosted run hit the stale upstream named-only test introduced by #775. Upstream #776 fixed it. Rebased onto that fixed base (
259be39), with the overlay patch unchanged by range-diff. Policy, the corrected stage suite, all overlay compilation and exact packed-DT comparisons pass again locally. Fresh PR-event CI passed on7341c494beeaedaed8b644d763d04f7b2c19776dagainst the fixed base (Policy and complete Tests: tests/all plus every package). The failed old run was not reused.