Repository navigation
Conversation
astaff
force-pushed
the
t6041/j616c-gpu-audio-video-20261027
branch
from
November 3, 2026 20:33
c048e0e to
3d0938d
Compare
astaff
force-pushed
the
t6041/j616c-disp
branch
from
November 3, 2026 20:37
ecf6bd9 to
ecab47d
Compare
astaff
force-pushed
the
t6041/j616c-gpu-audio-video-20261027
branch
from
November 4, 2026 00:40
3d0938d to
84612a4
Compare
astaff
force-pushed
the
t6041/j616c-disp
branch
from
November 4, 2026 00:40
ecab47d to
ac1e69f
Compare
The external display processors, their mailboxes, the fixed DP PHY of ATC3 and the ATC display crossbars are the same hardware on every T604x, at the same addresses. Move them out of the J616s files, all disabled, so that the next board can share them instead of describing them again. The J616s keeps its wiring and the power it runs on. The J614s and J616s DTBs do not change. Assisted-by: LLM Signed-off-by: Artyom Astafurov <artyom.astafurov@gmail.com>
The J616c has no PMP to wait for: iBoot leaves the external display chains powered, and the boot loader fills each external display processor's firmware memory. Enable a chain from the display gate, as for the J616s, once its processor has that memory: its power domains, pins, PHY, crossbar, DARTs, mailbox and processor, and the Type-C route of dcpext1, in one changeset before any device exists, with the chain's display DART appended to the display subsystem's iommus. A chain whose processor has no firmware memory, or that is not all there and disabled, is left as it is, and so is the other chain. The display subsystem's status is never written, so the internal display stays as the boot loader left it. The KUnit tests run the gate on a test tree of the J616c's chains. Assisted-by: LLM Signed-off-by: Artyom Astafurov <artyom.astafurov@gmail.com>
dcpext0 drives the HDMI port through the ATC3 display crossbar, atcphy3 and the on-board DP-to-HDMI converter, as on J616s; the J616c ADT gives the same addresses, interrupts, GPIOs and power states, and atcphy3 gets this board's tunables. With no PMP to acknowledge DISPEXT0, the chain runs as iBoot left it powered: no DISPEXT0 power domain is named and ATC3_COMMON is always-on. Everything stays disabled until the boot loader has filled dcpext0's firmware memory and the display gate enables it. Assisted-by: LLM Signed-off-by: Artyom Astafurov <artyom.astafurov@gmail.com>
…t-front port dcpext1 drives DP alt mode on typec1 through the ATC1 display crossbar and atcphy1, as on J616s: a Type-C display route on dcpext1, the connector's SuperSpeed and route ports, and the Type-C orientation and mode switches of atcphy1 with this board's tunables. atcphy1 has no pipehandler tunable, so it keeps USB2 and takes the DP-only path for DP. dcpext1, its DARTs, mailbox, crossbar and route stay disabled until the boot loader has filled dcpext1's firmware memory and the display gate enables them. Assisted-by: LLM Signed-off-by: Artyom Astafurov <artyom.astafurov@gmail.com>
astaff
force-pushed
the
t6041/j616c-gpu-audio-video-20261027
branch
from
November 5, 2026 02:49
84612a4 to
18ca0a6
Compare
astaff
force-pushed
the
t6041/j616c-disp
branch
from
November 5, 2026 02:49
ac1e69f to
99c9355
Compare
J616c and J616s carried the same six ATC3 PHY tables and the same crossbar power domains. Move them to t604x-extdisp.dtsi. Drop J616s's copy of ps_atc3_usb, which t604x-pmgr.dtsi has, reduce ps_fab7_soc to the parent J616s gives it, and drop status lines the shared files already imply. The J616s files keep what J616c doesn't use: the PMP-ordered power chain, the routes to all three Type-C ports and the ATC3 tables that differ. The J614s, J616s, J616s tether and J616c DTBs are byte-identical before and after. Assisted-by: LLM Signed-off-by: Artyom Astafurov <artyom.astafurov@gmail.com>
Owner
Author
|
Closing superseded fork-internal stack PR; T6041/J616c SEP/Touch ID and 26.x external display support are upstream in aurora-silicon/linux. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stacked view of aurora-silicon#749: its three commits on top of aurora-silicon#525's branch, so the diff shows only what aurora-silicon#749 adds. Review and discussion happen on aurora-silicon#749.
🤖 Generated with Claude Code