Skip to content

drm/apple: Add firmware-27 DCP display support - #254

Closed
DjDeveloperr wants to merge 2 commits into
apif-dcp-afkfrom
apif-dcp-firmware
Closed

DjDeveloperr wants to merge 2 commits into
apif-dcp-afkfrom
apif-dcp-firmware

Conversation

@DjDeveloperr

Copy link
Copy Markdown
Contributor

Adds firmware-27 DCP display and DPTX support for the T6050 providers. The private source predates public routing, framebuffer-lifetime and backlight fixes; this port keeps those public mechanisms and adds a separate wire serializer and callback table.

The driver validates message envelopes, default-surface allocation bounds, service-unit precedence and drive settings. It reuses the transaction queue and suspend drain, negotiates the inherited running RTKit session, and retains published DMA until a fresh firmware boot. The binding documents the required framebuffer, clock-table and coprocessor register metadata. No AGX acceleration changes.

Validation: native arm64 full Apple display-driver build, DT binding validation, and sanitized host tests of the production serializer, callback bounds and default-framebuffer sizing. Hardware boot, hotplug, brightness and suspend qualification remain pending.

Depends on #253. Bindings and driver changes are separate signed-off commits.

Describe the T6050 internal/external display providers, explicit
firmware ABI, ordered clock table and coprocessor physical register view.
Keep earlier providers' clock and power-table constraints.

Signed-off-by: Dj <hey@djdev.me>
Add firmware-27 method/callback tables and a separate present serializer.
Reuse the existing transaction queue, framebuffer retention, backlight
policy, routing and suspend drain rather than replacing the public driver
with the older private implementation.

Validate callback envelopes and framebuffer allocation limits. Preserve
explicit AFK service units, support nested asynchronous queries, and
connect protocol-27 DPTX drive settings to the live PHY/crossbar interface.

Require loader-provided firmware/clock/framebuffer metadata. Preserve
running RTKit sessions and retain published DMA until a fresh firmware
boot. No AGX acceleration or restart fallback is introduced.

Signed-off-by: Dj <hey@djdev.me>
@DjDeveloperr

Copy link
Copy Markdown
Contributor Author

Superseded by #485, refreshed from the current T6050 source onto Linux 7.3 integration. The new shared base is #472; all feature PRs now target t6050/base. Closing this stale chained version and keeping its branch for history.

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.

1 participant