Repository navigation
Conversation
|
Thank you, and agreed: one boot in this exact form first. Two notes from reading it now so they're fixed in the same push. I checked gpa8's SPIs 44-47 against stock's
|
0b29e3b to
3fe59dc
Compare
|
Booted in this form on the palmtop (round gt1: the integration kernel
|
3fe59dc to
0ea9c70
Compare
|
Thanks, both done in It sits on #106, so it lands after #106's layout question is settled (or after you move #106 to the top). It also needs the Makefile rebase described on #80. |
0ea9c70 to
617dc3d
Compare
617dc3d to
5727095
Compare
|
Unchanged and still merge-ready in content; it waits on the stack below it. The status is in my note on #105. |
5727095 to
5bf1ff9
Compare
|
Rebased onto #106's new head (one commit, unchanged). Compiles; checkpatch clean. |
5bf1ff9 to
6bbb335
Compare
|
Re-stacked onto #96 instead of #105, as asked: one commit of its own now. The context conflict next to |
…DT stack The gs201 Trusty, GSA and AoC drivers and bindings, on top of derekross#96 and derekross#119 (6bbb335). Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
|
Thanks, @W4HO-ham, for re-stacking it onto #96 so quickly. Your own commit's added and removed lines are identical to the version I checked before, so only the context moved. Dropping the It's ready, and it lands right after #96. Once #96 is merged, a One thing to know for the rebase: this PR and #105 add neighbouring blocks, so whichever of the two goes in second gets a small context conflict next to I built the 9a's DTB with this PR, #136, #105 and #122 combined that way. It compiles and passes dt-validate with no messages. #136 follows this one. |
…C port controller The Pixel 9a's MAX77779 sits on hsi2c6 (USI6, pins gpp12-0/1, 950 kHz as stock): its fuel gauge at 0x36 with the board's 2 mOhm shunt, and its USB-C port controller at 0x25, interrupting on gpa8-3 (active low, as stock's max77759tcpc@25). The port is described as a sink with a dual data role and is not linked to the USB controller's role switch yet: the USB controller stays a peripheral, as today. gpa8 becomes an interrupt controller with its four EINT SPIs (44-47). Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
6bbb335 to
810c4d3
Compare
|
Rebased onto today's
No content changed, only the base. #104 stays as it is, since it merges onto the base unchanged. For the |
Draft, stacked on #106 (the DT stack through ramoops); only the last commit is new. It needs a palmtop boot in this form before review: the palmtop runs both devices today, but its bring-up enables the bus at runtime rather than in the board DT, so this exact DT hasn't booted yet.
The 9a's MAX77779 sits on hsi2c6 (USI6, pins gpp12-0/1, 950 kHz as stock). Two of its parts have upstream drivers:
maxim,max77779-fg(kernel power: supply: max77779: temperature, charging status, current and time estimates #66), with the board's 2 mOhm shunt.maxim,max77779-tcpcontcpci_maxim(kernel usb: typec: tcpci_maxim: Add the MAX77779 (Pixel 9a) #97), interrupting on gpa8-3, active low, as stock'smax77759tcpc@25. The port is described as a sink with a dual data role. It isn't linked to the USB controller's role switch yet, so the USB controller stays a peripheral, as today. That link comes after the host-mode test (phy: the TI TUSB2E11 eUSB2 repeater (Pixel 9a) #107, arm64: dts: exynos: google: zumapro-tegu: Add the eUSB2 repeater #118).gpa8 becomes an interrupt controller with its four EINT SPIs (44-47), as gpa7 did for NFC in #105.
Checks: checkpatch --strict clean; on today's
omamobilewith the stack,zumapro-tegu.dtbbuilds andCHECK_DTBSreports nothing.On the palmtop: the same nodes and values have run since rounds tc1 (TCPC: a PD contract, replug back in 1 s) and the gauge rounds. This draft moves them into the board DT and enables USI6 and hsi2c6 there. I'll boot it as a DTB-only round on the integration kernel and post the result before asking for review.