08:13 <Kwiboo> sre: I should probably learn to read more details, seems only automatic GoodCRC response is handled by fusb302 not the actual PD messages ;-)

08:16 <Kwiboo> ZERO 3W only need very basic features: use fusb302 (ET7301B) to signal src power/data-role and detect orientation, then signal CH482d using a gpio pin to mux the SS lanes depending on orientation

08:20 <Kwiboo> main issue I noticed is that when fusb302 node is included in DT, then U-Boot work in SS speed for one orientation and Linux only worked in SS speed using the opposite orientation

08:20 <Kwiboo> and when the entire fusb302 node is exkluded from DT, then SS speed works for same orientation in both U-Boot and Linux

08:23 <Kwiboo> diederik: great that you got it to work, my PT2 is currently disassembled to large degree so it would have taken some time for me to do a reliable test :-)

08:48 <diederik> For a moment I thought it wouldn't boot up at all as SDcard also appeared to not work. My guess is that you need to do sth with the debug/uart adapter in some sequence to switch (back) to eMMC

08:49 <diederik> ofc I still don't know what that sequence is (if it's needed), but it's working ;-P

12:16 <sre> Kwiboo: the auto GoodCRC feature is already used by the kernel driver.

12:18 <sre> I'm currently working on stripping down the Linux kernel driver port done by Rockchip. I tried to go to the latest TCPM state first, but the kernel solution is too complex nowadays. I think a much more minimal solution should be fine for U-Boot.

12:23 <qschulz> sre: Collabora already went through this IIRC, c.f. https://gitlab.collabora.com/hardware-enablement/rockchip-3588/linux/-/issues/8

12:24 <qschulz> ah, well, sre might very well be the same initials as the person who wrote this :D

12:24 <sre> ;)

12:25 <sre> o/