Skip to content

phy: apple: Add T6050 fixed DP and four-clock crossbar support - #248

Closed
DjDeveloperr wants to merge 1 commit into
apif-smcfrom
apif-display
Closed

DjDeveloperr wants to merge 1 commit into
apif-smcfrom
apif-display

Conversation

@DjDeveloperr

Copy link
Copy Markdown
Contributor

Add the missing T6050 fixed DisplayPort PHY and the five-output, four-clock crossbar layout used by T6050/T8142. Preserve the newer public crossbar routing and tunnel helpers for older hardware.

The PHY gets register banks, power domains, tunables and optional drive tables from DT. Every static register sequence is validated before enabling domains. Link rate and voltage requests are checked before changing a running transmitter. The crossbar requires an explicit live pixel clock/coding configuration before activation, rejects conflicting shared clock coding, and reports bounded status timeouts instead of WARN_ON. A timeout poisons further routing operations.

This is display plumbing, with no GPU accelerator or mailbox changes. DCP firmware adoption and the consumer of the new direct-link API are a separate follow-up PR; this PR alone does not complete the M5 Pro display path.

Validation: native arm64 PHY/crossbar objects, binding validation, production-function tests of every register sequence and crossbar admission/timeout handling, and whitespace checks passed. Hardware display qualification remains pending.

Stacked on #247 for review ordering; these drivers do not depend on SMC changes.

Keep newer public routing helpers intact and add the matched five-output
crossbar layout. Require an explicit live PHY clock before activation,
reject conflicting coding, and return bounded status errors.

Validate all fixed PHY register steps before enabling power domains.
Expose named resources and tunables through bindings and exercise the
production register admission and failure paths in host tests.

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

Copy link
Copy Markdown
Contributor Author

Superseded by #480, 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