Repository navigation
Conversation
The TUSB2E11 converts between an SoC's eUSB2 signalling and USB 2.0 on one port, as on the Pixel 9a between the zumapro eUSB2 PHY and the Type-C connector. It takes its role from the eUSB2 link, so the binding only describes its supply and the board's signal tuning, one property per tuning register; the register names follow Google's GPL eusb_repeater driver. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
Power the repeater, wait the 3 ms it needs before it answers I2C, enable its port and write the board's tuning from the device tree; at exit, disable the port and the supply. The role needs no driver: the repeater follows the eUSB2 link. Registers and timing follow Google's GPL eusb_repeater driver for the Pixel 9a, which writes the same tuning. Signed-off-by: W4HO <87742609+W4HO-ham@users.noreply.github.com>
|
A note for when this leaves draft, since the 9a's USB is your only link to the phone while you test it: the safety points I posted on #118 (the board side of this repeater) apply here too. Please test it behind a dead-man switch that undoes the change if a fresh SSH login fails ( |
|
Understood, and I'll keep it in draft until all three are done. Answering the part that is a code question now, and leaving the rest as the test plan for when it leaves draft. The power-down path exists. So the test plan for leaving draft, all three of your points:
No action wanted from you on this; I'll post the results under those three headings. |
|
One measurement to add, from the daily boot just now (no repeater driver loaded): That sharpens your third point rather than answering it. Powering the repeater down on |
|
Thanks for the plan. Two corrections, the first mine: |
|
Both corrections taken, thank you: I had the wrong rail. The repeater's supply is LDO19M ( |
|
Thanks, @W4HO-ham. The plan reads right to me: LDO19M ( Two things to fold into that test while you're planning it. Neither needs a push now.
Nothing more from me until it leaves draft. |
Draft: built and checked, not yet run on the palmtop. It waits for the USB host test (a flash drive on the 9a's port), which will show whether the board's repeater tuning is what host mode needs.
The 9a's USB 2.0 path goes from the zumapro eUSB2 PHY through a TI TUSB2E11 repeater (
hsi2c_9at 0x3e, supply LDO19M) to the Type-C connector. Today the bootloader's repeater setup carries peripheral mode; host mode reaches the repeater's host role, but the root hub port's reset never completes.Two patches:
ti,tusb2e11, with its 3.3 V supply and one optional property per signal tuning register (mode control 0x50, the USB 2.0 side 0x70-0x73, the eUSB2 side 0x77-0x79).phys.Registers, the ready time and tegu's values (0x50=0a, 0x70=4f, 0x71=3c, 0x72=92, 0x73=86, 0x77=00, 0x78=0b, 0x79=60) come from Google's GPL
eusb_repeaterdriver andzuma-tegu-usb.dtsi.Checks: checkpatch --strict (only the new-file MAINTAINERS note on the binding patch, which the driver patch's MAINTAINERS entry covers), W=1 build, dt_binding_check. The board DT patch follows once the host test passes.