09:02 < wsa> okay, then let's start the IO meeting 09:02 < wsa> welcome everyone! 09:02 < wsa> here are the status updates: 09:02 < wsa> Status updates 09:02 < wsa> ============== 09:02 < wsa> A - what have I done since last time 09:02 < wsa> ------------------------------------ 09:02 < wsa> Geert 09:02 < wsa> : fixed st1232 touchscreen regression on armadillo800ev, investigated Lager reboot crash reported by Wolfram (RFCs sent), tested MSIOF with SYS-DMAC on R-Car V3U and reposted patches, advertised MSIOF min/max speed limits and actual transfer speed to SPI core, reviewed R-Car V3U patches 09:02 < wsa> Shimoda-san 09:02 < wsa> : submitted patches to detect data timeouts on SDHI, investigated RPC-IF driver issues with BSP team 09:02 < wsa> Wolfram 09:02 < wsa> : enabled and tested V3U IO devices: WDT, I2C, RAVB, SDHI, HSCIF, implemented V3U quirk for I2C driver and improved Gen2 quirk handling, tested and reviewed V3U PFC & GPIO patches, improved logic analyzer and got a working prototype, reworked and sent out WDT patch to fix scheduling while atomic, sent first preparation patches for better RECV_LEN support so we can enable it then on 09:02 < wsa> i2c-rcar, started discussing add. tasks for Q1 09:02 < wsa> B - what I want to do until next time 09:02 < wsa> ------------------------------------- 09:02 < wsa> Geert 09:02 < wsa> : wants to fix PHY Runtime PM in SH-ETH and EtherAVB driver 09:02 < wsa> Niklas 09:02 < wsa> : wants to figure out number of TSC nodes on V3U 09:02 < wsa> Shimoda-san 09:02 < wsa> : wants to collect more information about R-Car Gen3e, continue to develop R-Car S4 Ethernet driver, and continue to investigate SDHI driver's issues 09:02 < wsa> Ulrich 09:02 < wsa> : wants to test and send atomic xfers for i2c-rcar 09:02 < wsa> Wolfram 09:02 < wsa> : wants to send updates of the V3U enablement patches, finalize GPIO logic analyzer, continue to to work on RECV_LEN patches, pick up SDHI work again 09:02 < wsa> C - problems I currently have 09:02 < wsa> ----------------------------- 09:02 < wsa> Shimoda-san 09:02 < wsa> : couldn't get further Gen3e information 09:02 < wsa> Wolfram 09:02 < wsa> : needs wired pins on the connectors of the V3U Falcon to test PWM and TPU 09:03 -!- uli___ [~uli@55d468c5.access.ecotel.net] has joined #periperi 09:04 < wsa> geertu: good that I had a non-standard .config for Lager, that is a highly interesting outcome what you found out with the ethernet phys there 09:04 < geertu> wsa: Indeed. 09:04 < geertu> wsa: Tried the same on AVB? 09:05 < geertu> Ah no, won't crash as invalid access doesn't cause crashes on arm64. 09:05 < wsa> shimoday: so, it seems to me that I can test RPC-IF with an upstream kernel then (not importing BSP patches) 09:05 < wsa> geertu: nope, didn't try, but noticed that you found that out 09:05 < shimoday> wsa: i think so 09:06 < geertu> wsa: After fixing the issues in the upstream driver, as pointed out by Shimoda-san? 09:07 < wsa> wasn't it the BSP driver which is broken? 09:07 < shimoday> geertu: oops, as you said, fixing the issue at first is better 09:08 < shimoday> because upstream code seems to have other issues 09:08 < geertu> wsa: Continue reading below "By the way, according to the wrong BSP commit 3612986e5109, the RPC-IF driver seems to have some issues." 09:08 < wsa> ah, that 09:08 < wsa> ok 09:10 < wsa> so, about wiring on V3U 09:10 < wsa> from what I understand, we'd need extra thin jumper wires? 09:10 < wsa> but I couldn't track any 09:12 < geertu> wsa: You mean GPIO CN, with 1.27mm pitch? 09:12 < wsa> yes 09:13 < geertu> Use an adapter cable from 1.27mm to 2.54mm pitch? Cfr. JTAG 09:15 < geertu> Make one yourself, if you cannot find one? 2 IDC connectors + 1.27mm ribbon cable 09:15 < wsa> hmm, i found hw adapters but no cable 09:16 < wsa> maybe jtag will give me better search results 09:16 < wsa> it is not so much for me but for Magnus board farm :) 09:17 < geertu> damm: BTW, does your Falcon have the ether subboard? 09:17 < damm> yep 09:17 < wsa> I'll check 09:17 < wsa> (adapter cables) 09:19 < wsa> geertu: AFAIU the next version of renesas-drivers should have the V3U PFC and GPIO patches, or? 09:19 < geertu> wsa: The previous one 09:19 < geertu> had v2 09:20 < geertu> actually the one before, too 09:21 < wsa> yes 09:22 < wsa> sorry, my question was not precise 09:23 < wsa> the patches are all good to go, so they will come into the nex ren-drivers release via -next and not seperate topic branches, or? 09:23 < geertu> correct 09:24 < wsa> great news! 09:24 < wsa> so, discussion topics from your side? 09:26 < wsa> okay, then it seems we can move to the core meeting 09:26 < wsa> thank you everyone!