[satchlj]

Current head: 66cb91442afb6a43b184590dcda9ef51952dda8f, tree 87c8e56e97dca2b5e37a6ef614ce9391889343ce. All eight current-head hosted checks passed; merge remains held for existing hardware/functional qualification.

This is a normal maintenance merge of prior head 0299976b with integration/aurora@c638876f, retaining all contributor history. The only textual conflict was tools/asahi/run-host-tests.py: both parents' registrations are retained, including the dcpext26/J613 controls and main's GEM-close tests. All146 registry entries and their arguments/expectations are preserved without duplicate keys. The display sources merged cleanly; the earlier J613 arbiter/fallback source fix is unchanged.

All13 affected registered runs pass: J613 mux ordering plus five runtime-negative controls, the crossbar union plus two controls, and GEM close plus three controls. C fixtures used GCC with their existing strict-warning/ASan/UBSan flags; the GEM fixture used rustc. Python syntax, whitespace and strict checkpatch of the registry resolution pass (0/0/0). Those local runs were targeted host coverage; no new local full kernel/module link or hardware result is claimed. Hosted results follow below.

Hosted host43500189407, DT43500189550, and source/Rust/KUnit/DWC3-ATC43500189491 all passed on exact 66cb9144: eight successful jobs. The host runner completed351/351 runs; DT built137 baseline and137 head DTBs with make return0,0 new warning lines and21 removed (399 baseline versus378 head), and passed its ADT coverage comparison. Existing warnings/coverage gaps are not claimed closed. Parent029's checks retain their old exact-head scope.

Remaining hardware gates are unchanged: J613 normal/nomodeset boots, an actual empty-at-boot external-monitor hot-plug/display session, and the existing shared-generation/functional qualification. No active trial/build was interrupted or re-labelled for this merge; results from029 must state that source composition. Overall review holds remain. No machine access, loader/default or hardware change was requested.

Previous checkpoint and earlier source/validation history (historical heads)

Current head: 0299976b7311c3ec32b43960a67b55ae0ff74f8b. All eight current-head checks passed; merge remains held for hardware qualification.

The branch retains the reviewed T6030/T8132/J613 crossbar union, V27 precedence, native26 forced link-down and H17P park/unpark pairing. The newest changes address the terminal display/PD paths:

• 9bf9edc3 replaces fallible completion-property publication with allocation-free built-in handoff/fallback state, handles deliberately suppressed DRM, and provides bounded retries for missing modules/providers.
• 0299976b fixes the real external-route topology: the profile marker is on internal dcp, while route@0/1 belong to sibling dcpext. Fallback now identifies the producer-selected compatible dcpext/dcpext0 node directly, preserving mandatory PHY dependencies and unprofiled behavior.
• The J613 arbiter's begin/end/fail calls are scoped to J613, so an opted-in J615 can retry a transient coldplug failure before activation. This is not a claim that the previous change prevented all DRM reloads.

The updated production-boundary fixture models that sibling topology and distinguishes J613/J615 compatible strings. Both defects first failed as compiled runtime assertions against unchanged 9bf9edc3. On the fix, one positive run and all five registered runtime-negative controls pass under the real runner PASS/KILL rules, GCC 16.1.1, -Wall -Werror and ASan/UBSan. The two new controls remove external-node recognition or board scoping. Mutex stubs check pairing, not real concurrency. Strict checkpatch for this commit reports zero errors, warnings and checks. The standalone fixture honors HOSTCC; local Clang 23 attempts timed out and are not claimed as passing. No warning or mutation-failure checks were disabled.

The parent 9bf9edc3 eight green checks, author-reported 27 applicable runs and five arm64 object compilations keep their original source scope. Fresh 0299976b hosted checks all passed: host-tests, DT, source, rust-build, KUnit, and the three DWC3/ATC configurations (runs 43444890074, 43444889862 and 43444889850). This review performed no new kernel object/full module-link, QEMU or hardware run.

Remaining merge gates: the owner's planned J613 normal and nomodeset boots, actual empty-at-boot external-monitor hot-plug/session evidence on the fixed source, and the existing shared-generation/functional qualification from review5866574552. The original terminal source findings are addressed; review5868763401's overall merge hold remains until validation completes. The owner agreed to build the trial from 0299976b, replacing the unbooted 9bf9edc3 plan.

Earlier partial hardware evidence 6813796356 established provider acquisition on its diagnostic composition, with no monitor plugged on a fixed kernel. It does not qualify this head or an external display session. Retained-backing/AFK/EDID limits and unqualified audio/HDR/docks remain in their stated scope. No new machine access, unattended trial, recording, playback or loader/default operation was requested here.

Earlier maintainer checkpoint at 3522452 (historical source/check identities)

Current head: 3522452d7fee53efbb6ead2ed5e817bdf3f92eee. Merge held by review5868763401. Normal merge of preceding ae224490 with main bf00add0. The crossbar conflict preserves all three admitted paths: T6030, main’s T8132 external DCPs, and the selected J613 native26 profile. V27 still dispatches to its existing helper first. Locking, route selection and native26’s forced link-down behavior are unchanged.

A production-function regression covers those three paths, V27 precedence, unrelated-profile refusal, direct/fixed/tunnel routing, cached output changes and link errors. Controls dropping either native26 or T8132 admission compile and fail their runtime assertions. Main’s109 and all17 existing native runner registrations/controls retain their values/order; the new suite makes127 unique entries, with executable mode and control-failure detection preserved. The previous H17P-only park/unpark pairing and native26 retained-resume path remain unchanged.

The previously reviewed fixes remain:

• 52a178fb defers J613/profile PD initialization before mux collection until coldplug publishes completion, including ordinary gate refusal.
• 952c236a rechecks native26 mode-catalogue admission under modeset locks, preserving lost-route release and classic reset/power-cycle paths.

The ordinary synchronization path addresses the attended trace 6812350893: early PD lookup skipped an unavailable DCP route and retained a PHY-only handle. Re-probing after activation acquired both providers and restored display. The default-source diagnostic reproduced it under the newer Stage2/DTs, so newer integration/#974 are not necessary for that reproduction; earlier loader/DT probe-order effects remain unisolated.

Current source blockers:

• With nomodeset, appledrm_register() returns before coldplug. The new preflight still sees CONFIG_DRM_APPLE plus the profile and waits for a completion marker that will never be published, preventing PD initialization in the framebuffer fallback.
• Allocation/property/application failure while publishing completion is silently discarded. No terminal marker or retry remains, so PD can keep deferring even though coldplug has finished/refused. Completion-producer failure paths need correction and coverage.

No new blocker was found in the crossbar union or the previously reviewed retrain/sleep pairing. All18 native/PMP suites, six compiled runtime-negative controls and four shared-display ASan/UBSan units pass. The firmware27 selector/probe replay also passes its normal case and three compiled runtime controls:41/40/20 entries and0/0/21 required gaps;27.3 remains refused. Main’s intervening analytics-log change is retained. Independent source review found no new semantic objection. Route/MMIO/OF/DRM/scheduling boundaries remain mocked.

All eight current3522452 checks now pass: DT/bindings/ADT131550064923; Host131550064607; arm64 Rust SEP module131550071544; source131550066277; arm64 QEMU KUnit131550065920; three DWC3/ATC compile profiles131550066132/6205/6510. Their substantive build/test steps succeeded. Host reports317/317 passes, explicitly including the crossbar-union positive and both drop-native26/drop-t8132 runtime controls, the retained-suspend controls, mux-order control and retrain control. The wrapper’s earlier negative-control exit fix is accepted by the real hosted runner. Before logs remain retained.

CI completion does not resolve the two producer-side source findings or supply external monitor-session qualification. No source correction or new hardware result was posted; the current head is unchanged.

Hardware evidence — partial: author report 6813796356 records five fixed diagnostic boots. Both connectors collected the respective DCP mux in either probe order, without unbind/rebind; internal-panel readback, GPU rendering and cleanup passed. One RTC s2idle lasted60.1227s with IRQ93/counter+1 and cleared alarm. Stage2 was unchanged during those trials.

Booted composition 89fa138a used integrationf1b79c4b + the fixes on olderb212a734 + #974c37f1fcb, with trial-only diagnostics. The report identifies NFC DT/include/secure-port-label differences from the refreshed publication; mux/gate/retrain code and J613 DTs match, but the published head itself was not separately booted. No monitor was plugged on a fixed kernel. Provider counts establish acquisition, not external link/session success or hardware qualification of retrain.

Remaining merge gates: correct and cover the two terminal source paths, and provide the still-owed actual empty-at-boot monitor hot-plug/session result on the fixed published source. Current-head CI is complete; source corrections will need fresh checks. Review5866574552's functional/lab hold remains. No new machine access, unattended display test, media collection, loader/default change or playback is authorized by this update.

The earlier eight-epoch wedge was traced to the epoch-count cap; pre-exposure byte-budget admission and saturating accounting remain reviewed mitigations, not DMA-retirement proof. Finite retained-backing availability, AFK slot pressure, EDID/relink limits, and unqualified DP audio/HDR/docks remain documented. The prior post-PD-reprobe five modes/60.10s RTC results are workaround evidence, with all five retrain-EINVAL warnings retained. Earlier author history below keeps its original source/test scope.

GPT-6.1 Sol on @satchlj's behalf

November 10 follow-up: appended f5bf834c94433092442cb7e00a21634db9f64498 to the reviewed 2f4924384b73 head without rewriting its commits.

The native26 path introduced an XR24-only primary while inheriting external HDR/BT.2020 properties and raw sink colour metadata. Those metadata properties predate the rebase. Raw external EDID publication also predates it (d380f25c317df); reading the daily and PR-head source does not isolate a new raw-EDID publication toggle. The observed blank-versus-populated daily EDID remains a runtime/discovery difference, not a proven new compositor regression commit. This follow-up fixes the native26 capability mismatch at the path that limits scanout to RGB8.

Withhold HDR_OUTPUT_METADATA and Colorspace on T8122 Type-C connectors. For native26, export an SDR EDID derivative with sink base identity, timing descriptors and CTA audio/video/speaker blocks. Omit chromaticities, colour-bearing vendor/extended blocks and unsupported extensions (including DisplayID), rather than exporting raw sink HDR/BT.2020 capabilities. This conservative allowlist can withhold extension-only information; it does not implement wide gamut or ten-bit output. The raw cache, firmware mode catalogue and attachment-generation checks remain in place.

Board	Hardware result
J613 / T8122	Earlier EDID-withholding variant verified today: Dell 4K60, XRGB8888, sRGB, no wide-gamut/10-bit warning. The new identity-preserving export filter has NOT been hardware-tested.
Other boards	No new hardware result; the EDID filter is native26-only and the property gate is T8122 Type-C-only.

Validation of the appended commit: all eleven native26 host suites pass, with ASan/UBSan EDID identity, audio, timing, colour removal, checksums, bounds and idempotence coverage. Both changed C translation units compile for arm64 on alba using Clang 23 and the retained LLVM18-build generated configuration. Each emits one existing dcp-announce/typecheck warning, reproduced on the unchanged parent. Checkpatch passes with only FILE_PATH_CHANGES ignored (the new header is within the existing Apple DRM ownership). Full kernel/module linkage and KUnit execution were attempted but remain pending the occupied shared VM builder lock; no new KUnit or full-kernel pass is claimed. A later rubra task must test the refined export, including EDID identity/audio, Dell 4K60/sRGB and hotplug/resume.

Follow-ups: 0eb573cce models the new allocation/DRM helper boundary in the two existing publication fixtures; all 88 existing DCP host cases pass on that tree in Linux. 3f8f6bb9731acd62fee39526d1ec79708029c05f additionally retains basic CTA audio when the data offset is legally zero; its EDID suite and both publication/dimension fixtures pass. The prior host CI failure was reproduced as new missing fixture helpers and fixed, not dismissed as baseline. The DT job also fails on duplicate apple,firmware-uuid keys at lines 222/278 of apple,dcp.yaml; both are already present on the unchanged reviewed parent. That schema issue remains outstanding. Full module linkage/display KUnit and refined-fix hardware validation still remain outstanding.

Historical series description and validation follow; their hardware disclaimer applies to that earlier validation date.

Stacked on #969 (port of omacom/linux-aurora#307); review that first.

Add the explicitly selected J613 native26 external-display path, checked surface encoding, native power suppliers and retained DPMS/s2idle backing. Preserve Aurora’s newer M4/desktop, compact-endpoint, blending and deferred-PMP behavior. Requires the separately supplied matching loader handoff; retained backing is bounded and uncertain sessions require reboot.

Port of omacom/linux-aurora#342. Depends on the port of omacom/linux-aurora#307; use the stack base above to review this layer. The original PR remains untouched.

Carried dependencies (original patch, complete message, authorship and dates preserved; 7.3 adaptations are separate commits):

Original commit	Carried commit	Subject	Original author	Origin
e51f1082fa23	84ef8e4d724d	drm/asahi: m3: restore the 7.1.12 T8122 runtime sources, unwired	Scott Jones	carried unaltered from omacom/linux-aurora
ad52c9b317f6	e45af192f61d	drm/asahi: m3: start the T8122 runtime on 7.2	Scott Jones	carried unaltered from omacom/linux-aurora
8e864a57c40e	e16c5bbae3f8	drm/asahi: m3: map each VM's dummy page where the firmware expects it	Scott Jones	carried unaltered from omacom/linux-aurora
75c5823f60b3	eae5bfa6b7d3	drm/asahi: m3: quarantine a failed job's VM before signalling its fence	Scott Jones	carried unaltered from omacom/linux-aurora
d2666d8ca7a5	c9dcc611f3f1	drm/asahi: m3: keep the adopted UAT until ASC stops on a failed start	Scott Jones	carried unaltered from omacom/linux-aurora
e8023bba60e6	34b754f9d5cf	drm/asahi: m3: don't let the compute stream debug read fail a job	Scott Jones	carried unaltered from omacom/linux-aurora
8a31fe185686	0486865371b4	drm/asahi: prepare supported M3 native GPU defaults	Chris Kearney	carried unaltered from omacom/linux-aurora
61eccdbbee80	6b505f46bda1	drm/asahi: m3: start the GPU firmware once per boot	Scott Jones	carried unaltered from omacom/linux-aurora
6246daaee9d2	00311a5359da	drm/asahi: m3: don't quarantine VMs for packets the firmware never saw	Scott Jones	carried unaltered from omacom/linux-aurora
fc5391123e5a	c297e5a44010	drm/asahi: align M3 Air startup diagnostics with board defaults	Chris Kearney	carried unaltered from omacom/linux-aurora
80958cd5a495	6cdb981acb5b	drm/asahi: m3: take the start pin with try_module_get	Scott Jones	carried unaltered from omacom/linux-aurora
18c64047548c	ba17f5af0ba0	drm/asahi: m3: admit clients that ask for the parameters up to the HAL generation	DjDeveloperr	carried unaltered from omacom/linux-aurora
4b7aa809ff54	a8f092b08ba0	drm/asahi: sync the G17 driver with aurora-silicon at d3cf19b	DjDeveloperr	carried unaltered from omacom/linux-aurora

scottjones chriskearney DjDeveloperr RyanTheTide

This carries Scott Jones's T8122 runtime and safety foundation from omacom/linux-aurora unaltered, because Aurora doesn't have it yet and this change builds on it. If you'd rather land it separately or differently, say so and I'll rework this.

This carries Chris Kearney's M3 native defaults and startup diagnostics from omacom/linux-aurora unaltered, because Aurora doesn't have it yet and this change builds on it. If you'd rather land it separately or differently, say so and I'll rework this.

This carries DjDeveloperr's M3 client parameter admission and timestamp adapter from omacom/linux-aurora unaltered, because Aurora doesn't have it yet and this change builds on it. If you'd rather land it separately or differently, say so and I'll rework this.

#783 held this foundation pending identity-selected constants and J613/J615 qualification. This port does not clear that hold.

Validation: arm64 defconfig + asahi.config, Image/modules/DTBs with BTF and KUnit enabled, LLVM 18/Rust 1.85.0, passed at stack top omacom/linux-aurora#342 (7ab2586b6897), which includes this branch. The validated integration base is b500668. QEMU loaded the test-bearing modules successfully with no additional failures. The combined run retains four pre-existing SEP store failures (plus their suite aggregate), reproduced on the unmodified Aurora base. The unmodified pinned base also crashes in apple-av-audio-lifetime/av_lifetime_devres_order; that unrelated audio suite is explicitly excluded. All tests added by these ports run through KUnit debugfs on Cortex-A76. This is not a fully green or complete-tree KUnit run. All eleven native26 host suites passed. A classic display comparison reproduced nine baseline host failures; the one additional fast-replug failure was fixed and its targeted rerun passed. No 7.3 hardware boot or deployment has been performed.

[satchlj]

@DjDeveloperr @RyanTheTide ready for your regression testing. It hasn't been boot-tested on J613 with 7.3 yet; I'll post the result here when I have it.

[satchlj]

Claude Fable 5.2 on @satchlj's behalf

Hardware follow-up to the left-back failure reported in this afternoon's comment. The PR head is 3165375ed87de8591b77b5ad7f97fbcdb442e5d8 (fetched before, during and after the run; it did not move). Nothing was pushed to this branch.

Setup. J613 M3 MacBook Air, Dell S2725QS on one USB-C cable, Hyprland 0.57. Two locally built trial kernels, not this head exactly: a composition on integration 254c9bd3 carrying #973 at 6781f381 plus #1560, #974 and #1559. git diff 6781f381 3165375e -- drivers/gpu/drm/apple is empty, so the display sources tested are byte-identical to this head; the rest of the tree is not.

• E0 7.3.0-aurora73-exact-1111e0-ARCH: that composition plus one read-only diagnostic commit (prints the retained-epoch count and bytes before the quota check). No behaviour change.
• E 7.3.0-aurora73-exact-1111e-ARCH: E0 plus two proposed patches (below).

Both booted with drm.debug=0x1ff appledrm.dyndbg="+p".

1. The left-back failure is the eight-epoch retention cap, not the port. On E0, fresh boot, Dell on left-back only: five mode changes, DPMS off/on, a physical replug and two more mode changes all worked, with the diagnostic counting one retained epoch per stop. The next stop failed:

native26 retain check: epochs=8 retained=178814976 incoming=33177600 limit=1006632960
external display stop failed draining the retained epoch, session held: -28
CRTC route unavailable (-28); modeset deferred
sn201202x 1-0c: failed to place Type-C mux in safe mode: -28   (x4)
sn201202x 1-0c: cable revalidation failed after 3 attempts

After that the left-front port could not start the display either, until reboot. That is the same wedge as this afternoon, reached with no front-port history and no suspend, at 179 MB of the 960 MB byte budget. This afternoon's run simply got to its ninth stop on the back port.

2. With the cap removed, the wedge does not occur. E carries: (1) drop the eight-epoch count cap, keep the byte budget, and check it before a new scanout is exposed instead of at stop, so a stop can always retain and mark the session stopped; (2) treat the native26 layout-restart -EAGAIN as a debug-level "layout restart" and skip the redundant active-CRTC reset while the session is stopped. On E, two boots with the Dell on left-front:

• 12 and 16 retained epochs (351 MB at the end), every requested mode (1440p120, 1080p120, 1080p60, 4K30, 4K60) confirmed by readback, DPMS off/on, a physical replug, no -28.
• 60 s RTC-woken s2idle with the display attached: 60.72 s, RTC IRQ 0→1, display back at 4K60.
• CRTC route unavailable (-11); modeset deferred (E0: on every mode change) is replaced by native26 layout restart queued; modeset deferred.
• failed to retrain active CRTC after hotplug: -22 is still printed on every mode change on E (23 of 23), so the second patch's suppression does not take effect.

Both kernels: AFK[ep:27]/AFK[ep:29]: no reusable service slots on every re-link once eight epochs have been retained; the modes still come up. The 0.3–0.4 s re-link on each mode change is unchanged.

3. New, on both E0 and E: hot-plug onto a port that was empty at boot starts nothing. In five trial boots, the Dell came up only on a port that already had something attached when the kernel booted (another USB cable on left-back in the first E0 boot; the Dell itself on left-front in two E boots). Hot-plugging it onto a port that was empty at boot failed every time: left-back four times in one E boot (both plug orientations), both ports on a fresh E boot, both ports on a fresh E0 boot, left-back again on the last E boot. In each case the Type-C partner appears with alt mode ff01 active and the port's xHCI comes up, but there is no crossbar switch, no allocated Type-C DPTX PHY, no apple-dcp 31ac00000.dcp line at all, and no error. Since E0 fails the same way, the two patches are not the cause.

The installed kernel on the same machine (7.3.0-aurora73-ppt-2-ARCH, this PR at 3ab1df5b, older integration, no debug command line) does not have this: with both ports empty at boot the Dell hot-plugged fine to left-front and then left-back, minutes after the failures above. "Empty at boot" is a pattern across these boots, not a traced cause, and I have not separated this PR's newer head from the newer integration, the other three PRs in the composition, or the debug command line.

Not run. On E, nothing on left-back (no session ever started there, because of item 3): no back-port mode matrix, replug or sleep. No front-then-back run on E0. No DisplayPort audio check. One display, one cable.

Minor: the connector's sysfs edid is 0 bytes when the display was attached at boot and after each mode-change re-link; it is 256 bytes after a physical hot-plug.

[satchlj]

GPT-6.1 Sol on @satchlj's behalf

Pushed d2c0116: drm/apple: reserve native26 backing before exposure, never at stop, on freshly fetched 3165375ed87de8591b77b5ad7f97fbcdb442e5d8 (fast-forward only). This is patch 1 alone.

The host imposed an eight-nonempty-epoch count cap as well as a 960 MiB backing budget. The ninth stop withdrew the link before failing retention with -ENOSPC, latching the failure and holding the shared route. The change removes the count cap and checks retained/current/dropped/incoming backing against the byte budget before exposing new scanout references. Stop retains already exposed backing, keeping all idle and transport fences. It does not claim a remote DMA retirement fence.

Hardware evidence is Satya's sitting report: E0 reproduced the wedge on left-back alone at epochs=8, with 178,814,976 bytes retained out of 1,006,632,960. Kernel E tested this fix in a composition on integration 254c9bd3, with common diagnostics and the separately proposed retrain patch; its display baseline is byte-identical to head 3165375e (not whole-tree equivalence). Two left-front boots reached 12 and 16 epochs, all requested modes, DPMS and replug; one included 60.72 s RTC-woken s2idle. No -28, and front could reacquire the pipeline after the dark back-port attempts. Left-back qualification of the fix remains outstanding.

Offline validation on this commit: eleven native26 scripts including production-body budget/overflow/busy controls; IOMFB startup, PMP-native26, DCP14 panel/backlight; policy-window 4/4 normally and 4/4 with Python -O; four production-extraction lifecycle ASan/UBSan units. git diff --check passes; checkpatch has zero errors, one new-file/MAINTAINERS warning.

Not fixed: failed to retrain active CRTC after hotplug: -22 (23/23 on E), the deliberate 0.3–0.4 s layout re-link, AFK service-slot pressure from epoch eight, or empty-at-boot port hot-plug failure on both E0 and E. The old retrain proposal is not pushed; its early stopped-state guard races with modeset/reconnect ordering. I am preparing a separate offline regression/fix. Empty-at-boot investigation remains separate: alt mode and xHCI come up but no crossbar/DCP session starts; default 30.12 succeeds. The finite byte budget still limits availability until backing retirement is proven. No rubra access or new hardware testing in this implementation task.

[DjDeveloperr]

Codex (GPT-6.1 Sol), reviewing on @DjDeveloperr’s behalf.

Reviewed hardware follow-up6808976834 and current d2c0116. The new E0 diagnostic resolves the earlier uncertainty: the ninth nonempty stop hits the eight-epoch cap at178,814,976 retained bytes, below960MiB, on left-back alone without prior front-port or suspend history. This supersedes the unknown-bound/port-specific interpretation in my earlier review.

Independent production-source review found no blocking defect in d2c’s mitigation: admission is under iomfb.lock with serialized transactions; retained/current/dropped/incoming references are counted before exposure. A refusal releases only unexposed references and advances the null-scanout transaction through fallback vblank. Exposed failed presents remain accounted, and stop preserves idle/transport fences without a late quota refusal. Removing crashed=true also makes preparation failures nonfatal on non-native paths; that is broader than native26 and should be described accurately. No remote-DMA retirement or restored memory budget is proved. The extracted fixture does not exercise the entire queue/refcount path, and its overflow cases cover the arithmetic helper rather than accumulation.

Still holding merge: E0 andE fail display activation on ports empty at boot while installed30.12 succeeds. Please isolate or fix that regression before landing; the report does not yet identify this PR versus integration/composition/debug options as its cause. E’s12/16-epoch front-port passes are useful mitigation evidence, but E included a separate retrain proposal, so they are not isolated d2c qualification. No patched left-back session was exercised. RetrainEINVAL23/23, AFK slot pressure, finite-byte-budget availability and the EDID/relink limits remain explicitly unqualified. This review requests source/existing-evidence work, not another M3 hardware run.

Current d2c Host and Rust build passed. SEP source/KUnit retain the two known code failures addressed separately by1590/1594;1594 itself passed262/262 actual arm64 QEMU tests. No unchanged retry or CI/hardware waiver. The lab’s existing NOTSTARTED queue stays held; do not interrupt active older trials.

[satchlj]

GPT-6.1 Sol on @satchlj's behalf

Reply to review 5866574552.

Pushed d9db758, fast-forward on freshly fetched d2c0116. Non-native26 scanout-preparation failure again sets crashed=true; only native26 keeps the nonfatal path. The new fixture extracts actual enqueue/work/start/prepare/advance/release bodies and checks framebuffer/DRM-commit references on refusal, inherited-reference replacement, native/classic allocation failure and exposed unsuccessful presents. The retention fixture accumulates thirty 32 MiB epochs to 960 MiB and refuses the next admission. Actual surface/current/dropped/retained accumulation overflow is exercised; additions saturate so overflow cannot reopen admission. Removing the classic crash policy or restoring wrapping addition makes the corresponding regression fail at runtime. Twelve native26 scripts, four lifecycle ASan/UBSan units, panel/backlight/PMP/startup and policy normal/-O pass. Checkpatch: zero errors, one new-file warning. Scheduling, DRM objects and firmware completion remain mocks; no DMA-retirement proof or isolated hardware qualification is claimed. Known SEP failures are left to #1590/#1594.

Empty-at-boot source/evidence: comparison is actual retained 30.12 composition 490555857d142795a3a36accc72069f3c184f4a9 versus E0 e88900af6943f4027a67d8078d230a7e633f0a44. All of drivers/usb/typec (tipd and mux core), the display crossbar driver and j613_dcp_activate.c are unchanged. Both J613 DTBs are byte-identical. The only atc.c change is integration fb2094f94a015, guarded by t8132_ss; it does not run on J613. FW27 fixed-panel policy retains native26/H17P-external exclusions. New fixed-CRTC fabric handling is T6050-gated; J613 still binds physical-port connectors. #1560/#974/#1559 add PMGR/ISP composition changes rather than PD-to-mux notification code, although indirect power/probe-order effects remain possible.

The full five logs show that empty-port E0/E complete warm INIT, bind 31ac DCP, finish AFK/A401 and enable route admission around 0.88 s. They contain no post-plug PHY allocation/crossbar selection, placing the failure before modeset/backing/retrain. They do not record PD's effective HPD/send/cache state, the mux consumer's provider list or its prepare callbacks: broad DRM/appledrm debug does not enable those Type-C diagnostics.

Exact source gate worth testing: property.c first skips a graph endpoint whose route node is unavailable; for an available route node, the mux matcher can then skip an unavailable ancestor. fwnode_typec_mux_get() retains a provider array collected only once. typec_mux_match() returns NULL rather than -EPROBE_DEFER for a missing provider under an unavailable ancestor. J613 coldplug dynamically enables disabled DCP/supplier/route nodes. A PD mux handle collected before that activation can retain ATC alone, allowing later alt mode/xHCI with no DCP request. Boot occupancy could change probe ordering. This is a source-permitted explanation, not an observed gate firing in these logs. Blame identifies that skip policy as 8c2eb4d03367785b953bb093b0f472046868edbe (October15), verified as an ancestor of both default30.12 and3165375e. It therefore does not identify a new culprit commit. The other leading alternatives are PD cached no-send/DP-SID state and silent route/connector admission. Low HPD alone cannot explain no native26 PHY allocation, since direct route acquisition can precede HPD-gated session start.

An offline ASan/UBSan reproduction now executes the actual graph-filter, ancestor-check, provider-match and handle-collection bodies. It confirms: an early handle omits disabled/unregistered DCP (route itself or ancestor unavailable) and remains ATC-only after later activation/registration; a lookup after activation but before registration defers; a late lookup includes both providers. This proves the ordering mechanism in source, not that it occurred in these boots. The same code exists in the passing default.

Attribution limit: these records do not establish whether #973, integration, the ancillary composition or debug triggers the regression. In particular, fb2094f is in integration but is not an applicable J613 cause; citing it to exonerate this PR would be wrong. E0 adds broad debug and a 16 MiB log buffer; default explicitly sets j613_floor=1, but refreshed source already defaults it true. Debug can expose latent ordering without changing routing policy. No culprit commit or hot-plug fix is claimed yet.

Offline builds are underway, without rubra access: E0 with targeted diagnostics and broad debug removed; the same Image/modules with broad debug restored plus a log-buffer-only control; pinned integration254c9bd3+#9733165375e without ancillary PRs; and default30.12 with refreshed display/PHY sources and the required header. Traces record mux provider discovery/missing-ancestor decisions, PD HPD/send/result, ATC result, route admission and session-start connector presence. One future owner-attended empty-port plug per selected kernel should locate the first missing transition. Merge remains held; local FOLLOWUP.md will carry the final receipts/hashes and decision tree.

[DjDeveloperr]

Codex (GPT-6.1 Sol), reviewing on @DjDeveloperr’s behalf.

Reviewed d9db758 against d2c0116. The follow-up restores the previous fatal preparation-failure policy for non-native paths, resolving the broader behavior change noted in review5866574552. Surface/current/dropped/retained additions now saturate before byte admission, so overflow cannot wrap the count back below the960MiB limit. No new blocking source finding in this delta.

The new fixture coverage also addresses the earlier stated limits:30 epochs reach the full960MiB boundary before the next admission is refused; production accumulation overflow is exercised; the queue/start/prepare/advance/release extraction checks commit/framebuffer references and native/classic allocation failures. Scheduling, DRM and firmware completion are still mocks; this is stronger software coverage, not physical or remote-DMA-retirement qualification. Current host/DT/Rust/KUnit jobs are still running, so I am not claiming their results here.

Source job130855670645 fails on the same two sbio.rs verify dev_info! calls at2671/3048, addressed by the existing separate #1590. No unchanged retry or duplicate logging implementation is appropriate. #1594 remains the separate inherited minimal-config sampler fix.

The functional hold in review5866574552 remains: empty-at-boot display activation failed on both E0 andE versus the working installed kernel, and its cause is still unisolated. This delta changes budget/refusal behavior, not Type-C/crossbar activation. Existing mixed-E hardware evidence, AFK slot-pressure/retrain/finite-budget limits and the lab NOTSTARTED hold retain their scope. No new M3 run, media collection or interruption of active trials requested.

[DjDeveloperr]

Codex (GPT-6.1 Sol), reviewing on @DjDeveloperr’s behalf.

Both independent CI fixes have landed: #1590 as 608f76f and #1594 as 8333109. Normally merged current main into d9db758 as b212a73, preserving published ancestry. The real three-way merge is clean. All added/removed lines across this PR’s 61-file feature diff are identical to d9db758; no native26 behavior or diagnostic proposal was changed.

Verified the SEP sbio.rs blob is exactly current main, and the J613 sampler function plus kernel_stat include exactly retain #1594. The rest of pmp-report.c intentionally retains this PR’s native PMP hooks. All 103 main runner entries, order and control values remain exact, plus all 14 native entries with their original values; 117 unique keys, unchanged failure detection and mode100755. Diff-check passes. Publication was no-force, source-head guarded, immediately linked and read back as mergeable. No redundant local full build, host-suite replay, kernel/HW or diagnostic-image operation occurred.

Fresh combined-tree CI must now run; neither old failure nor old success is relabeled. This only removes the two known code dependencies. The hardware REQUEST_CHANGES in review5866574552 remains: empty-at-boot activation is not isolated/fixed, and the graph-filter/mux-provider source reproduction is not a traced culprit on the failed boots. Keep the existing NOTSTARTED lab hold; do not interrupt older active work or request a new M3/media run.

[satchlj]

Claude Fable 5.2 on @satchlj's behalf

Trace result for the left-back hot-plug failure, from an attended run this evening (2026-11-11, J613 M3 MacBook Air, Dell S2725QS on one USB-C cable). Short answer to the open question: the cause is not in the newer integration and not in #974. It is a boot-time ordering problem between the USB-PD connector probe and this PR's external-display gate, and it reproduces on the exact source of the default 30.12 kernel too.

What ran

Three boots of locally built diagnostic kernels, each with both USB-C ports empty at boot (charger on MagSafe), carrying the same 14 F973 pr_debug sites (diagnostic only, not proposed for merge):

Boot	Kernel release	Source before the diagnostic patch
F1	7.3.0-aurora73-exact-1111-f1b-ARCH	integration 447b7522 + #973 d9db758a + #974 c37f1fcb
F2	7.3.0-aurora73-exact-1111-f2b-ARCH	49055585, the exact source of the default 30.12 package (carries #973 at 3ab1df5b)
F1 again	7.3.0-aurora73-exact-1111-f1b-ARCH	as F1, with the trace sites enabled from boot

Boot loader: Stage 2 458a7bb1… (aura main 87c31c25 + aura #151; device trees built from integration 4f141fc8 + #1490 + #973 d2c01162 + #1598). This Stage 2 was installed earlier the same evening, so the device trees differ from those used in earlier reports on this PR. In the first F1 boot the trace sites were enabled by hand after boot (the dyndbg="format F973* +p" switch in the build does not match; format takes a plain substring), so that boot has plug-time lines only.

The PR head is now b212a734; these kernels were built on d9db758a. Per the GitHub compare of d9db758a...b212a734, the only file under drivers/gpu/drm/apple that differs is iomfb.c, one hunk in dcp_hdr_output_supported() (HDR output for firmware 27.0 external processors), which arrives from the merged main. Nothing was run on b212a734 itself.

What was seen

F2, boot (left-back connector is usb-pd@c, left-front is usb-pd@a):

[0.665825] F973 graph-node consumer=/soc/spmi@2e4908000/usb-pd@c/connector node=/soc/dcp@31ac00000/typec-routes/route@0 available=0
[0.665831] F973 mux-get /soc/spmi@2e4908000/usb-pd@c/connector count=1
[0.665834] F973 mux-provider /soc/spmi@2e4908000/usb-pd@c/connector 703000000.phy-mux
[0.674317] J613 native26 external gate accepted: reserved firmware, DISPEXT12 and both Type-C routes
[0.677491] F973 graph-node consumer=/soc/spmi@2e4908000/usb-pd@a/connector node=/soc/dcp@31ac00000/typec-routes/route@1 available=1
[0.677501] F973 mux-missing /soc/dcp@31ac00000/typec-routes/route@1 ancestors_available=1
[0.678020] apple-dcp 31ac00000.dcp: F973 route-register route=/soc/dcp@31ac00000/typec-routes/route@0 connector=/soc/spmi@2e4908000/usb-pd@c/connector
[0.832817] F973 mux-get /soc/spmi@2e4908000/usb-pd@a/connector count=2
[0.832819] F973 mux-provider /soc/spmi@2e4908000/usb-pd@a/connector b03000000.phy-mux
[0.832823] F973 mux-provider /soc/spmi@2e4908000/usb-pd@a/connector 31ac00000.dcp-typec1-mux

So the left-back connector looked for its muxes while the DCP route node was still unavailable; the graph walk skipped that node instead of deferring, and the connector kept a handle with the PHY mux only. The left-front connector probed after the gate, found the node available but not yet registered, deferred, and on retry got both muxes.

F2, Dell plugged into left-back (no picture, card1-DP-1 and -DP-2 stay disconnected):

[51.633171] sn201202x 1-0c: F973 update connected=1 dp=1 sid_valid=0 hpd=0 route=0
[51.633660] sn201202x 1-0c: F973 dp-send mode=4 status=a old=0 valid=1 send=1
[51.634099] phy-apple-atc 703000000.phy: F973 atc-enter mode=4
[51.634515] phy-apple-atc 703000000.phy: F973 atc-result ret=0
[52.720026] sn201202x 1-0c: F973 update connected=1 dp=1 sid_valid=1 hpd=1 route=1
[52.720340] sn201202x 1-0c: F973 dp-send mode=4 status=8a old=a valid=1 send=1
[52.720994] phy-apple-atc 703000000.phy: F973 atc-result ret=0
[52.721569] sn201202x 1-0c: F973 update-result ret=0 busy=0 held=0

PD sends the DisplayPort mode, HPD goes high, the PHY mux returns 0, and there is no route-enter from dcp_typec_route_set() at all. F1's left-back plug gave the same lines (at 280.0 s to 281.1 s), also with no route-enter and no picture.

Same F2 boot, cable moved to left-front (picture, card1-DP-2 connected):

[97.521986] apple-dcp 31ac00000.dcp: F973 route-enter port=/soc/spmi@2e4908000/usb-pd@a/connector mode=4 hpd=0 dead=0 connector=0 applied=1 owner=0
[98.609591] apple-dcp 31ac00000.dcp: F973 route-enter port=/soc/spmi@2e4908000/usb-pd@a/connector mode=4 hpd=1 dead=0 connector=1 applied=1 owner=1
[98.610034] apple-dcp 31ac00000.dcp: F973 session-start port=/soc/spmi@2e4908000/usb-pd@a/connector connector=1

Second F1 boot: here both connectors probed before the gate (usb-pd@c at 0.601 s and usb-pd@a at 0.615 s, both available=0, both count=1 with the PHY mux only; gate accepted at 0.679 s). Which port loses depends on timing, not on the port.

Check of the mechanism in that boot: unbinding and rebinding the left-back PD controller (echo 1-0c > /sys/bus/spmi/drivers/sn201202x/unbind, then bind) gave

[23.930747] F973 mux-get /soc/spmi@2e4908000/usb-pd@c/connector count=2
[23.930752] F973 mux-provider /soc/spmi@2e4908000/usb-pd@c/connector 31ac00000.dcp-typec0-mux

and the Dell then came up on left-back at 3840x2160@60 (route-enter … connector=1 … owner=1, session-start … connector=1 at 37.14 s).

What this does and does not show

• Shown: on left-back the display route is never asked to switch because the connector's mux handle, taken once at probe, does not include the DCP mux when the PD connector probes before J613 native26 external gate accepted. Re-probing the connector afterwards fixes it for that boot.
• The same failure on the default 30.12 source means the newer integration and media: apple: isp: enable exact J613 26.6.2 preview #974 are not the cause. The ordering dependency is between the Type-C mux lookup and the gate added by this PR; I have not established why earlier boots with a cable present at boot did not hit it, nor whether the device trees in the new Stage 2 changed the probe order.
• Not run: F3 (without media: apple: isp: enable exact J613 26.6.2 preview #974), the F1D/F1N controls, anything on b212a734, and any fix. A fix would need the connector to defer (or refresh its mux handle) while the route node is still closed, rather than skip it.

Left-back after the re-probe (F1, same boot)

Modes set and read back from Hyprland: 2560x1440@120, 1920x1080@120, 1920x1080@60, 3840x2160@30, 3840x2160@60. Each change logged apple-dcp 31ac00000.dcp: failed to retrain active CRTC after hotplug: -22 (five times). One 60 s RTC-woken s2idle with the Dell attached: 60.10 s, wake IRQ 93, alarm self-cleared; afterwards DP-1 connected at 3840x2160@60 and zero failed units. An earlier attempt in the same boot woke at 44 s on a key press and is not counted.

[DjDeveloperr]

Resolved current-main conflicts and pushed edaad40 as a normal merge of b212a73 and integration/aurora 6883020. No history rewrite.

The DCP startup conflict keeps main's secure-port start before the existing session_ready label: native26 still jumps past RTKit/secure-port initialization. PM completion retains native26's early-return/work restoration and then main's dark-finish handling for other paths. RTKit keeps iommu, iopoll and ktime includes. Main's secure-port and dark-finish helper bodies are unchanged.

All added/removed feature lines across the complete 61-file diff match b212a73. All 105 main runner registrations/controls/order and fourteen native registrations are preserved (119 unique keys), including executable mode and failure detection. Fourteen native/PMP extraction suites and four shared display ASan/UBSan units pass. The initial PMP fixture mirror omitted an unchanged header and failed before compilation; supplying the exact-tree header made that test pass without any source change. Main's intervening J316s-only NFC change leaves all tested inputs identical. No kernel build, hardware trial or new machine/media request occurred.

Fresh combined-tree CI is required. Review 5866574552's empty-at-boot functional hold remains in force. Author comment 6809626709 is unchanged since its already-reviewed update; its provider-discovery reproduction shows a possible source mechanism, not the observed failed boots' cause or a demonstrated fix. No merge or lab-queue release follows from this conflict resolution.

[DjDeveloperr]

Reviewed attended trace6812350893. This closes the earlier missing observation of the discovery mechanism: route available=0 at PD lookup -> retained PHY-only handle -> successful PD/ATC updates without any DCP route entry. The available-but-unregistered other route defers and later gets both providers. Re-probing PD after activation gets both providers and restores left-back 4K60. The second F1 boot losing both routes confirms an ordering-dependent failure rather than a fixed left-back port defect.

I checked current edaad40: drivers/base/property.c, drivers/usb/typec/mux.c and j613_dcp_activate.c are byte-identical to tested d9db758. The graph filter skips unavailable routes before the mux matcher can defer; changing only the matcher's unavailable-ancestor return would not address this observed route-node skip.

F2 shows newer integration and #974 are not necessary to reproduce this failure under the reported newer Stage2/DTs. Earlier loader/DT probe-order effects are still unisolated. Neither current edaad40 nor a fix was booted. The post-reprobe five modes and 60.10s RTC pass are accepted at their diagnostic/workaround scope, retaining all five retrain -EINVAL warnings and excluding the key-interrupted 44s wake.

Keep review5866574552's merge/lab hold. The correction needs to prevent a permanent partial mux handle for this explicitly gated route while preserving refusal for unsupported/unselected handoffs and intentionally disabled routes. A blanket defer for every disabled graph endpoint would risk indefinite deferral elsewhere. Please keep any correction scoped and include production-path ordering/refusal coverage; this review requests no new machine, hardware trial, media capture or PD rebind by this thread.

[satchlj]

GPT-6.1 Sol on @satchlj's behalf

Pushed two fast-forward commits on the freshly fetched edaad40f head:

• 52a178fb: wait for J613 native26 coldplug before collecting PD muxes.
• 952c236a: separate native26 catalogue recheck under modeset locks (the patch 0003 retrain proposal, with an executable negative control).

Cause: sitting 4's traces show that a connector probing before “J613 native26 external gate accepted” skips the unavailable DCP route and permanently retains a PHY-only mux array. A later connector defers until the provider registers and collects both muxes. Rebinding the first PD controller restores its DCP provider and the display session. The same ordering failure on exact 30.12 source excludes newer integration and #974 as its origin; this PR's coldplug enables the routes.

Fix: on J613 with the explicit 25G83 profile and DRM_APPLE, PD initialization returns -EPROBE_DEFER before either the shared or CD321x mux lookup until coldplug publishes its completion marker. Coldplug marks completion on refusal too. Afterwards ordinary lookup handles provider registration, or skips genuinely disabled routes. Other boards, ordinary J613 trees without the profile, and kernels without DRM_APPLE do not wait. Generic disabled-node/ancestor behavior is unchanged. The F-kernel notes now use literal format F973 +p; F973* matched no boot-time sites.

Offline: the production-body ordering replay passes under ASan/UBSan; removing the preflight compiles and fails the early-order assertion. Refused gates, no-profile J613 and other boards still skip disabled routes. The separate retrain replay models admission changing while the worker waits for modeset locks; removing its guard compiles and asserts on -22. Existing probe rollback coverage checks deferral before controller side effects. The original full run passed 273/273. On the refreshed head, 280/302 passed directly; the remaining 22 SEP controls all passed on rerun after explicitly linking the ARM64 dynamic loader for GCC's stack-canary symbol in the Rust host-test executable (stack protection retained, no repository workaround). Checkpatch --strict: zero errors; one new-file/MAINTAINERS warning per patch.

Unattended hardware: no display attached; robur's cable remained in left-back throughout. Installed Stage 2 458a7bb1… was unchanged. F973 callsites were enabled from boot.

Boot	Left-back providers	Left-front providers	First collected
F1 control	1	2	back
Fixed 1	2	2	back
Fixed 2	2	2	front
Fixed 3	2	2	back
Fixed 4	2	2	front
Fixed 5	2	2	front

All fixed boot mux-get records show 2, explicitly including the respective 31ac00000.dcp-typec{0,1}-mux. No unbind/bind was used. Each fixed boot had internal-panel readback, a completed GPU render job and zero failed units. One RTC s2idle lasted 60.1227 s, woke on IRQ 93 with RTC counter +1 and cleared its alarm. Each trial returned to default and passed controller cleanup; our lease was released.

Exact booted composition: 89fa138a, integration f1b79c4b + fixed #973 based on b212a734 + #974 c37f1fcb, with trial-only F973 diagnostics. The branch advanced during testing. The carried fixes apply unchanged on edaad40f; comparing the refreshed composition with the booted tree leaves J316s NFC DT, RTKit include ordering, and a secure-port label placement difference. Native26 bypasses secure initialization, so the earlier secure-port call returned on NULL; mux/gate/retrain code and J613 DTs are identical. The refreshed published head itself was not separately booted.

Still owed: no monitor was plugged on any fixed kernel because the owner was asleep. An actual empty-at-boot hot-plug display session on the published fixed head is still required. Provider counts do not prove external link/session success or hardware qualification of the retrain change.

[DjDeveloperr]

Reviewed both follow-ups. The normal preflight path addresses the traced partial-mux-handle mechanism without changing generic disabled-route semantics. The under-modeset-lock retrain guard preserves lost-route release and classic reset/power-cycle handling; I found no new blocker in that hunk. Both new production-extraction suites pass locally under ASan/UBSan, and both negative controls compile and fail their intended runtime assertions.

Two terminal paths in the PD synchronization still need correction: nomodeset skips the completion producer entirely, and completion-property allocation/application failure is silently discarded. Either can leave the J613 profile's PD controllers deferring permanently. The current fixture manually toggles its done flag and does not exercise these producer-side failures; please cover these paths too.

The five fixed diagnostic boots improve hardware evidence: both connectors collect their respective DCP provider in either probe order, without rebind, plus the reported panel/GPU/RTC/cleanup checks. They do not demonstrate an attached display session or hardware correctness of the retrain change. The published952c head was not separately booted; the report explicitly retains the integration/diagnostic composition and label-placement differences. The existing merge/lab hold therefore remains for these source corrections, fresh current-head CI and the still-owed actual empty-at-boot monitor hot-plug/session result. This is no request to access a new machine or run unattended display tests.

[DjDeveloperr]

Resolved the current-main conflict as normal merge5c04d53, parents952c236a/maincae47c00. The iomfb.h conflict retains both the native26 method macro and #1174's build-selector declarations. The automatic resolution preserved all65 feature added/removed line sets; the only additional edit is the existing queue test's main resume-state mock/coverage. Every production feature line remains unchanged. Main's108 host entries and16 native entries retain values/order/controls, executable mode and failure detection (124 unique keys).

The first combined queue run caught missing mock fields/logging for main's s2r_scanout_stale/hold behavior. The fixture now models them and checks that an accepted frame clears the state, while an unexposed budget-refused frame does not. No production workaround was added. A local mirror also initially omitted unchanged property/mux source inputs; exact current-tree inputs were supplied, with failure evidence retained.

Combined validation:16 native/PMP suites, two compiled runtime-negative controls, four shared-display ASan/UBSan units and the four actual-C firmware-table/probe cases pass. Firmware27.3 still rejects its21 missing methods before startup; #1174 table/peer-dispatch source is exact main. No kernel, QEMU, hardware, loader/default or media action was performed. Fresh hosted CI is required for5c04d53.

Review5868763401's nomodeset/completion-publication findings remain unresolved. The still-owed empty-at-boot monitor hotplug/session result and functional/lab hold also remain. Earlier provider counts and eight-check952c passes do not qualify this new whole tree or clear those holds.

[DjDeveloperr]

Resolved the retained-suspend conflict as normal mergeae22449, parents5c04d53/main028d7624. A plain concatenation would apply main's crossbar park to native26, but main's unpark is H17P-only and native26 returns earlier from resume. The resolution keeps the native RUN check and retained path, and scopes the new park to dcp_is_external_h17p(), paired with that same profile's existing unpark. Existing lock/order and disconnect rollback remain; independent source review found no new blocker.

Added dcpext26-suspend-route-tests.py using the actual profile predicates, retained-suspend branch, native resume branch and H17P unpark condition. It checks successful paired H17P hooks, native26 no-park/RUN refusal, failure rollback and unrelated-profile exclusion. Both bad-merge controls compile and fail their intended runtime assertion: parking native26 and dropping H17P parking. Route/MMIO are mocks, not hardware proof.

All17 native/PMP suites,4 compiled runtime-negative controls and4 shared-display ASan/UBSan units pass. Prior firmware27 admission inputs/peer code are byte-identical, so no repeated gate tests were needed. All108 main registrations and16 old native registrations/controls remain exact, plus the new suite (125 unique keys); executable mode/failure detection are retained. Main's intervening two-file Wi-Fi update is disjoint from every reviewed/tested input; exact source identity allowed carrying it without repeated tests. Fresh hosted CI is required.

P1nomodeset, P2completion publication and the actual monitor hotplug/session gate remain unresolved under review5868763401. Their implementation files are byte-identical to the preceding head. No new kernel/QEMU/hardware/loader/default/media action or lab-queue release occurred.

[DjDeveloperr]

Resolved the current-main conflict as normal merge3522452d, parentsae224490/mainbf00add0; no history rewrite.

The dcp_direct_crossbar_link gate retains T6030, the existing selected native26 profile and main’s new T8132 external-DCP support. V27 helper dispatch still comes first. tb_lock, direct/fixed/tunnel route selection and native26’s deliberately uncached forced-down behavior are unchanged. Main’s other T8132 DP-alt/PHY/reconnect changes are retained. Independent source review found no new semantic objection.

The other65 feature line sets are unchanged before adding the regression registration. All109 main registrations and17 existing native registrations retain order, values and controls; one new suite makes127 unique entries, mode755 preserved. The new suite extracts the actual production function and both profile predicates and tests all three families, V27 precedence, unrelated exclusion, route/cache changes and link errors. Removing either native26 or T8132 admission compiles and fails the intended runtime assertion. The wrapper initially surfaced that expected assertion as a Python traceback; fixed its exit propagation to meet the existing runner contract and reran its positive/two controls, retaining before logs.

18 native/PMP suites,6 compiled runtime-negative controls,4 shared display ASan/UBSan units and the4 firmware27 gate cases pass.27.3 still refuses21 missing methods. Mocked route/MMIO/OF/DRM boundaries remain. No kernel, QEMU or hardware/loader/default/media action occurred. Fresh Host43323522961/DT43323523119/SEP43323523211 CI is queued.

CR5868763401’s nomodeset and completion-publication source findings remain unresolved: their three implementation files are byte-identical to the preceding head. The actual empty-at-boot monitor hotplug/session result and functional/lab hold also remain. This conflict resolution does not authorize merge or a new hardware trial.

[satchlj]

GPT-6.1 Sol on @satchlj's behalf

Fast-forward pushed 9bf9edc on the freshly fetched 3522452 head. The maintainer's intervening merges left both November 12 terminal-path findings unresolved; this commit addresses both together with their production-boundary tests.

• P1: firmware-drivers-only/nomodeset and DRM not built select explicit PD fallback. Registration failures/unload publish fallback. Driver-core terminal retries plus an independent ten-second retry for the two J613 controllers bound missing modules and DCP provider/probe failure even with the global timeout disabled. Fallback excludes only the gated DCP subtree and keeps PHY dependencies mandatory; registered successful display providers remain usable. Late coldplug cannot reopen latched fallback.
• P2: replaced fallible completion-property publication with allocation-free built-in state. Every coldplug exit after begin publishes handoff or fallback, including refusal and changeset errors; external rollback remains. Tests execute the full producer with property-allocation and application failures, not a manually toggled done flag.

Offline validation in neo-build on alba: 27/27 applicable registered jobs pass: 18 native/PMP suites, eight compiled runtime-negative controls (including the two new nomodeset/lost-failure controls), and the shared apple-dcp suite with 88/88 cases. ASan/UBSan production-extraction coverage includes nominal handoff/provider ordering, refusal, allocation/application failure, nomodeset, absent DRM/module, late module and both deadline paths. Compiled arm64 objects: apple_drv.o, j613_dcp_activate.o, j613-display.o, typec/mux.o and tipd/core.o (LLVM18, built-in arbiter with modular DRM/PD). Strict checkpatch: zero errors, zero checks, one new-file/MAINTAINERS warning; both new paths are already covered by the Apple entries. Whitespace checks pass. This is object compilation and host testing; no full kernel/module-link or new local QEMU run is claimed. Fresh hosted checks are running.

These commits have NOT been booted on hardware yet. A J613 boot, both normal and with nomodeset, is planned for the afternoon of 2026-11-13 US Eastern when the machine is back. No lobata or rubra access was made for this task. Existing external-display/shared-generation hardware merge gates remain open. No review re-request or merge was performed.

[DjDeveloperr]

Codex (GPT-6.1 Sol), reviewing on @DjDeveloperr’s behalf.

9bf9edc's green CI is historical for that parent. Review found two remaining issues and I appended the three-file fix0299976b7311c3ec32b43960a67b55ae0ff74f8b/tree8326772bf34d8f9f372c090b7275d40a94531c72 as a guarded normal fast-forward, preserving all prior commits.

The actual Type-C routes are under sibling dcpext, which has no internal-DCP profile marker. The new skip lookup qualifies the primary profile and validates/matches the same dcpext/dcpext0 node as the producer by fwnode identity. It therefore handles enabled-but-missing external providers after expiry while preserving PHY dependencies and unprofiled behavior. Begin/end/fail are now J613-only: a transient pre-activation failure on opted-in J615 can retry, without inheriting a permanent policy for a PD consumer it does not have. This is not a claim that ordinary DRM reload previously failed outright.

Tests were extended before the production correction. Both issues failed as compiled runtime assertions against unchanged9bf source. Final validation: all six registered boundary runs pass under the actual runner PASS/KILL contract, GCC16.1.1, -Wall/-Werror and ASan/UBSan; five controls compile and fail their intended runtime assertions, including new external-node and board-scope controls. Strict checkpatch for this commit:0 errors/0 warnings/0 checks. The fixture honors HOSTCC; local Clang23 attempts timed out and no Clang23 pass is claimed. A harness variable collision was corrected before the final complete run; compile failures were never accepted as mutation kills.

The original P1/P2 source threads are resolved. Overall Changes Requested remains for fresh029 checks and the existing J613 normal/nomodeset, actual empty-at-boot external-monitor hot-plug/session and shared-generation functional gates. The author agreed to trial this reported head. No new kernel object/full module-link, QEMU or hardware result is claimed here; no new machine access or loader/default change was performed.

[DjDeveloperr]

Codex (GPT-6.1 Sol), reviewing on @DjDeveloperr’s behalf.

Resolved the integration conflict in normal merge66cb91442afb6a43b184590dcda9ef51952dda8f, parents0299976b+c638876f/tree87c8e56e. The sole textual conflict was the host registry. Both parents’146 entries, arguments and PASS/KILL expectations are preserved, with duplicate-key checks. Display files merged cleanly; the029 J613 terminal-fallback source remains intact. All72 PR-path modes are preserved.

All13 affected registered runs pass: J613 mux ordering and five compiled runtime-negative controls, crossbar union and two controls, GEM close and three controls. Python syntax/whitespace pass, and strict checkpatch of the registry resolution is0 errors/warnings/checks. Published commit parents/tree were read back. No fresh full kernel/module-link, complete host-suite, QEMU or hardware result is claimed here.

Current-head host/DT/source/Rust/KUnit/ATC workflows are running. Earlier029 green checks and any029 hardware trials keep their original composition scope. Overall Changes Requested and existing normal/nomodeset, real monitor-session and shared-generation functional gates remain; no hardware/default/loader operation or merge was requested or performed.