-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M2+ desktop dcp/dptx HDMI output support #329
Conversation
716e435
to
d82b20c
Compare
I'm curious, is this work also help DP Alt for laptops? |
dc81c87
to
340ea0d
Compare
I can confirm it working for my |
yes, linux need further changes not turn the dptx-phy power domain off. You can add |
iboot uses this and it's simpler. m1n1 doesn't need to swap surfaces for tear free display. Signed-off-by: Janne Grunau <j@jannau.net>
Required non-blocking handling of multiple AFK endpoints for the same mailbox. Signed-off-by: Janne Grunau <j@jannau.net>
Required for t602x dcp*. Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
Phy "implementation" is simplified a replay of a macos trace with on t8112 with a 1920x1080 display. Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
This needs to ensure that the data processing does not block on message retrieval from the mailbox. Command processing must not block and have to ensure that afk_epic_command() receives the reply to its command. DCP's dptx-port endpoint (endpoint 0x2a) can send notifies at any time which needs to be processed in the right context. Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
To be used on the dptx-port endpoint. Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
Used on dptx-port endpoint. Signed-off-by: Janne Grunau <j@jannau.net>
They exceed 256 with repeated chainloading of m1n1.bin on j473. Do not hold a service for every possible channel but keep a fixed array of 8 services identified by the channel number. Signed-off-by: Janne Grunau <j@jannau.net>
This allows forward declarations in other headers. Signed-off-by: Janne Grunau <j@jannau.net>
Based on the linux kernel implementation with updates for the macOS 13.5 based DCP firmware. Signed-off-by: Janne Grunau <j@jannau.net>
Signed-off-by: Janne Grunau <j@jannau.net>
This on is boring but allows turning additional logging on. Signed-off-by: Janne Grunau <j@jannau.net>
Will be used by SMC. Signed-off-by: Janne Grunau <j@jannau.net>
Only supported operation is smc_write_u32() for turning the dp2hdmi converter on M2 desktop systems on. Signed-off-by: Janne Grunau <j@jannau.net>
340ea0d
to
ff1a4dd
Compare
On M2* desktop systems the HDMI output is not managed by dcp/dcp0. This allows more flexibility, for example dcp on the M2 Mac mini can be routed to the USB-C/ThunderBolt ports. For m1n1 this adds quite ab bit of complexity. In addition to the DCP iboot endpoint/protocol two additional endpoints have to be started. Only the dptx-port endpoint has a meaningful AP <=> DCP communication. In addition we start the system endpoint to optionally enable more verbose syslog messages (if RTKIT_SYSLOG is defined). In addition the dptx-phy or lpdptx-phy has to be programmed. Those two phy look mostly identical. MacOS seems to use a static DP configuration (4 lanes, HBR3*) regardless of the connected display. The added SMC gpio support is used to power the MCDP29xx DP to HDMI converter on. Config is unfortunately a mess since Apple can't name the device tree nodes consistently. On M2 Ultra devices only the four dcpext*/dispext* on each die are used. M2 Ultra support is untested. * link rate might differ on t602x based devices for 8k60 support Signed-off-by: Janne Grunau <j@jannau.net>
ff1a4dd
to
ae41be1
Compare
Initialize the HDMI output of M2+ desktop Macs releases in 2023.