Repository navigation
arm64: dts: apple: t8132-laptop: describe the trackpad actuator on every M4 laptop - #2273
RyanTheTide wants to merge 1 commit into
Conversation
…ery M4 laptop The MTP firmware on every M4 MacBook offers the trackpad's haptic engine as its "actuator" interface (ADT /arm-io/dockchannel-mtp/mtp-transport/ actuator on the J604, J713 and J715). Only the J604's tree described it, so on the MacBook Airs the click stays firmware-driven and there is no Force Touch stage. Describe it in the shared laptop file and drop the J604 copy. The J604 tree is unchanged; the J713 and J715 gain the actuator node. Signed-off-by: Ryan <ryan@aurorasilicon.org>
|
No blockers. On current integration/aurora, J604, the iMacs and J773g are byte-identical, and J713/J715 gain only the empty HW row: J713 on the head: Assisted-by: LLM (Claude:Opus 5.5) |
|
J713 row (M4 Air 13, macOS 27.2): the J713's default Stage 2 with only its DTB changed, adding the empty
On the default without this node, the J713 has no actuator interface: dockchannel-hid ignores interfaces that have no DT node, so the click stays with the actuator's firmware. The J713 ADT has Still to run: a J715 row, if one is available. Assisted-by: LLM (Claude:Opus 5.5) |
|
J715 row at Build
Result: the driver binds. Force click is not felt, which matches the driver's default
Not covered:
|
Problem. The MTP firmware on every M4 MacBook offers the trackpad's haptic engine as its "actuator" interface; the ADT has
/arm-io/dockchannel-mtp/mtp-transport/actuatoron the J604, J713 and J715. Only the J604's tree described it (#1886), so on the M4 MacBook Airs the click stays firmware-driven and there is no Force Touch stage.Change. Describe the actuator in
t8132-laptop.dtsiand drop the J604 copy.Testing. cpp + dtc on all six T8132 boards: same warning counts. With phandles normalized:
actuatornode.Still to run. On a J713 or J715:
hid-apple-mtp-hapticbinds, and force click and haptic feedback work.Assisted-by: LLM (Claude:Opus 5.5)