diff options
author | Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2019-12-09 15:29:52 +0900 |
---|---|---|
committer | Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> | 2019-12-09 16:23:07 +0900 |
commit | 55e3b2f45880faaf06f3c660ca9e8a6d9aa14bce (patch) | |
tree | 6392fd201a51ff0f6dc0e474803e6f3b20919504 /wiki/Chat_log/20190509-io-chatlog | |
parent | 5d9e1b983faf7645ddc3d45d28e612d2ac4179c0 (diff) |
wiki: Porting wiki: Porting Chat Log
Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Diffstat (limited to 'wiki/Chat_log/20190509-io-chatlog')
-rw-r--r-- | wiki/Chat_log/20190509-io-chatlog | 99 |
1 files changed, 99 insertions, 0 deletions
diff --git a/wiki/Chat_log/20190509-io-chatlog b/wiki/Chat_log/20190509-io-chatlog new file mode 100644 index 0000000..f3f1d38 --- /dev/null +++ b/wiki/Chat_log/20190509-io-chatlog @@ -0,0 +1,99 @@ +09:07 < wsa> okay, let's start the meeting now +09:08 < jmondi> wsa: :) +09:08 < Marex> heh +09:08 < wsa> here are the collected IO reports +09:08 < wsa> A - what have I done since last time +09:08 < wsa> ------------------------------------ +09:08 < wsa> Geert +09:08 < wsa> : tested TPU on Salvator-XS, and investigated sh_eth and SPI EEPROM regressions +09:08 < wsa> Kaneko-san +09:08 < wsa> : addressed review of thermal calculation update for Gen3 +09:08 < wsa> Niklas +09:08 < wsa> : retested SDHI PM issues using Geerts instructions and figured them out, +09:08 < wsa> worked on clarifying the cooling-states for the Gen3 thermal driver +09:08 < wsa> Shimoda-san +09:08 < wsa> : sent a patch series to improve performance by using IOMMU, measured SDHI & USB +09:08 < wsa> SSD performance to verify the CPU load, reviewed patches about USB & DMA +09:08 < wsa> Simon +09:08 < wsa> : updated patch to avoid using TX delay mode on E3/D3, sent new version of +09:08 < wsa> rcar_thermal patch to update calculation foromula, sent new versiof of patch +09:08 < wsa> to add thermal zone to support IPA on H3, tested thermal calculation update +09:08 < wsa> for Gen3 +09:08 < wsa> Ulrich +09:08 < wsa> : sent RAVB patch to implement MTU change while device is up +09:08 < wsa> Wolfram +09:08 < wsa> : reviewed first upstream backend of i2c slave interface, sent out final version +09:08 < wsa> for watchdog_init_timeout refactoring, fixed a reported bug about not-ratelimited +09:08 < wsa> error messages with suspended I2C adapters, prepared proposal for Linux Plumbers, +09:08 < wsa> took over maintainership for the i2c-gpio driver, reviewed Shimoda-san's patches +09:08 < wsa> for SDHI and IOMMU, minor patch review for Renesas Europe +09:08 < wsa> B - what I want to do until next time +09:08 < wsa> ------------------------------------- +09:08 < wsa> Kaneko-san +09:08 < wsa> : wants to continue with thermal calculation update for Gen3 +09:08 < wsa> Niklas +09:08 < wsa> : wants to finish analyses of Geerts issues with the SDHI PM patch +09:08 < wsa> Shimoda-san +09:08 < wsa> : wants to update SDHI with IOMMU patches, and continue to discuss about +09:08 < wsa> RZ/A2 USBHS support +09:08 < wsa> Simon +09:08 < wsa> : wants to address feedback for above thermal patches, and follow up on RAVB +09:08 < wsa> on E3/D3 +09:08 < wsa> Wolfram +09:08 < wsa> : wants to investigate SDR104 regression with SDIO, handle 'arbitration lost' better +09:08 < wsa> with the IIC core +09:08 < wsa> C - problems I currently have +09:08 < wsa> ----------------------------- +09:08 < wsa> Kaneko-san +09:08 < wsa> : is looking for upporting candidates +09:08 < wsa> Simon +09:08 < wsa> : doesn't know how to handle 100MBit speed limit on D3/E3 because he cannot +09:08 < wsa> test the alternative solution (PHY settings) +09:08 < wsa> Wolfram +09:08 < wsa> : has been knocked out by an illness for nearly two weeks +09:08 < wsa> fire away any comments or questions +09:09 < wsa> horms: about your upporting question for Kaneko +09:09 < wsa> unless we get a new ticket file (bsp395?), IO is all done/assigned with upporting +09:09 < wsa> I think only MM has upporting tasks left +09:10 < wsa> dunno if that is suitable for Kaneko +09:10 < wsa> I keep looking around for other non-upporting tasks, though +09:11 < wsa> geertu: I rediscovered a clock related question to you, it's about the WDT +09:11 < wsa> https://patchwork.kernel.org/patch/10900571/ +09:11 < wsa> If you have some time... +09:11 < horms> wsa: ack, thanks +09:12 < wsa> neg: can you give a quick summary what the two issues were which you found with the MMC clock imbalance thing? +09:12 < wsa> The mails confused me a little, because I read one was MMCIF which is != SDHI? +09:12 < geertu> wsa: Thanks, will reply +09:13 < wsa> geertu: thanks! +09:13 < pinchartl> horms: there are BSP patches not addressed yet for MM, we can have a look at that during the MM part of this meeting +09:14 < wsa> neg: ? +09:14 < wsa> neg: fallen asleep on the sofa again? ;) +09:15 < horms> pinchartl: thanks. unfortunately I have to leave this meeting soon. perhaps we can chat in the not too distant future +09:15 < pinchartl> sure, works for me +09:15 < wsa> horms: do you still have a few minutes to talk about the RAVB D3/E3 testing issue? +09:15 < horms> yes, i have a few minutes +09:16 < wsa> so, we got some magic values from the BSP team for the PHY which could add this "delay mode" +09:16 < wsa> but we don't have a way to test that? +09:16 < horms> yes, that is correct +09:16 < horms> I can try the values and see if ethernet works +09:17 < horms> But I don't have a test case for the unreliable gigabit communication problem we are trying to solve +09:17 < wsa> is it possible to verify that the PHY actually uses the "delay mode"? +09:17 < horms> So I can probably say "it doesn't seem to make things worse" +09:17 < horms> But I can't say "it addresses the issue rasied by the BSP team" +09:18 < geertu> If you have a fast scope (unikely), you might notice the impact of configuring delay mode on the PHY.. +09:18 < horms> geertu: i do not +09:18 < horms> wsa: maybe, I can look into that +09:20 < wsa> At least, that would be okay with me. If the SoC has broken "delay mode" but the PHY has a working one, and we can prove that it is active, I'd think this is what we can do for now without super-fancy test hardware +09:20 < horms> Undersood. Let me a) think about if I agree and b) do some testing and see what data I can collect +09:21 < horms> In general I think we should try to move ourselves into a better position to decide +09:21 < horms> I'll see about making that so +09:21 < horms> Thanks for your advice +09:21 < wsa> Thanks, Simon! +09:22 < wsa> So, neg is still not here, which means I ran out of questions +09:22 < horms> I'll drop off now, sorry that I can't stay for the entire meeting +09:22 < wsa> have a nice day! +09:22 -!- horms [~horms@ip4dab7138.direct-adsl.nl] has quit Quit: Leaving +09:22 < wsa> are there more questions from your side? +09:24 < wsa> well then +09:24 < wsa> geertu: do you want to start now or at 09:30? +09:25 < geertu> wsa: I prefer at 09:30, for the least amount of surprise |