Skip to content

arm64: dts: apple: t8132: give the scaler and JPEG DARTs their power domains - #1668

Merged
DjDeveloperr merged 1 commit into
aurora-silicon:integration/aurorafrom
niteria:j713/t8132-dart-pd
Nov 12, 2026
Merged

DjDeveloperr merged 1 commit into
aurora-silicon:integration/aurorafrom
niteria:j713/t8132-dart-pd

Conversation

@niteria

@niteria niteria commented Nov 12, 2026

Copy link
Copy Markdown
Contributor

#1616 and #1617 enabled the T8132 scaler and JPEG engines, and their DARTs with them. Only the engines name their power domains (ps_msr, ps_jpg); the DARTs (dart_scaler0, dart_jpeg00, dart_jpeg10) don't. A DART probes as a device of its own, and on the J713 (MacBook Air M4) those blocks are off when it does. The probe's first register read takes an SError, and the boot panics before the root filesystem is up:

Kernel panic - not syncing: Asynchronous SError Interrupt
Hardware name: Apple Inc. MacBook Air (13-inch, M4)/J713, BIOS aura 1.0.0b11 / U-Boot 2026.07
Call trace:
 ...
 apple_dart_readl+0xc/0x40 (P)
 platform_probe+0x5c/0xa4
 really_probe+0xbc/0x2ac
 ...
 apple_dart_driver_init+0x24/0x30

This gives each DART its engine's domain, as the T6031 and T8112 scaler and JPEG DARTs have. With it, the J713 boots integration/aurora (with #1314 on top) to the desktop under Aura 1.0.0b11, and both JPEG engines and the scaler bind.

Only tested on the J713. Other T8132 Macs get the same DT change; it should only matter where iBoot leaves these blocks off.

🤖 Generated with Claude Code

…domains

The T8132 scaler and JPEG engines are enabled now, and their DARTs with
them, but only the engines name their power domains (ps_msr, ps_jpg).
A DART probes as a device of its own, and on the J713 those blocks are
off when it does: the probe's first register read takes an SError, and
the boot panics before the root filesystem is up:

  Kernel panic - not syncing: Asynchronous SError Interrupt
  ...
   apple_dart_readl+0xc/0x40 (P)
   platform_probe+0x5c/0xa4
   ...
   apple_dart_driver_init+0x24/0x30

Give each DART its engine's domain, as the T6031 and T8112 scaler and
JPEG DARTs have.

Fixes: d34ed1e ("media: apple: scaler: add the M1, M1 Max/Ultra and M4 engines")
Fixes: fd4b396 ("media: apple: jpeg: add the M1 Max/Ultra, M3 and M4 engines")
Assisted-by: LLM
Signed-off-by: Bartosz Nitka <niteria@gmail.com>
@niteria
niteria marked this pull request as ready for review November 12, 2026 10:21
@DjDeveloperr
DjDeveloperr merged commit ec71436 into aurora-silicon:integration/aurora Nov 12, 2026
2 checks passed
fbalazsy pushed a commit to fbalazsy/linux that referenced this pull request Nov 12, 2026
…their power domains

The M3, M3 Pro and M3 Ultra JPEG engines are enabled, and their DARTs
with them, but only the engines name their power domains. A DART
probes as a device of its own, so when iBoot leaves the JPEG block off
the probe's first register read takes an SError and the boot panics.
This is the T8132 failure fixed in aurora-silicon#1668, on the other SoCs whose
JPEG DARTs were enabled at the same time.

Give each JPEG DART its engine's domain, as the T6031, T8112 and
T8132 DARTs have. Do the same for the scaler DARTs on these SoCs:
they are still disabled, but they would fail the same way once
enabled.

DTBs for all other boards are unchanged.

Fixes: fd4b396 ("media: apple: jpeg: add the M1 Max/Ultra, M3 and M4 engines")
Reported-by: Bartosz Nitka <niteria@gmail.com>
Link: aurora-silicon#1668
Assisted-by: LLM
Signed-off-by: Ryan Murray <ryan@aurorasilicon.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants