From 55e3b2f45880faaf06f3c660ca9e8a6d9aa14bce Mon Sep 17 00:00:00 2001 From: Kuninori Morimoto Date: Mon, 9 Dec 2019 15:29:52 +0900 Subject: wiki: Porting wiki: Porting Chat Log Signed-off-by: Kuninori Morimoto --- wiki/Chat_log/20191128-io-chatlog | 114 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 114 insertions(+) create mode 100644 wiki/Chat_log/20191128-io-chatlog (limited to 'wiki/Chat_log/20191128-io-chatlog') diff --git a/wiki/Chat_log/20191128-io-chatlog b/wiki/Chat_log/20191128-io-chatlog new file mode 100644 index 0000000..9592ea6 --- /dev/null +++ b/wiki/Chat_log/20191128-io-chatlog @@ -0,0 +1,114 @@ +09:53 < wsa> ok, now for the IO meeting, welcome! +09:53 < wsa> Here are the status updates +09:54 < wsa> Status updates +09:54 < wsa> ============== +09:54 < wsa> A - what have I done since last time +09:54 < wsa> ------------------------------------ +09:54 < wsa> Geert +09:54 < wsa> : investigated MAX9611 regression caused by too low conversion time and asked +09:54 < wsa> Maxim about a proper value, researched eMMC regression on R-Car M3-N +09:54 < wsa> Shimoda-san +09:54 < wsa> : submitted a patch series to change DMA buswidth for SDHI +09:54 < wsa> Ulrich +09:54 < wsa> : developed a new version of the RAVB MTU runtime change patch and got it +09:54 < wsa> merged, reviewed SDHI and GPIO patches +09:54 < wsa> Wolfram +09:54 < wsa> : updated I2C API conversions and created minor cleanup patches on the way, +09:54 < wsa> worked with Geert on MAX9611 issue and eMMC regression and sent out a revert, +09:54 < wsa> discussed with MMC maintainer about CAP_ERASE with SDHI, reviewed/tested +09:54 < wsa> patches for I2C core, SDHI, MMC core, I2C, IIC, updated periject to BSP 3.9.7 +09:54 < wsa> B - what I want to do until next time +09:54 < wsa> ------------------------------------- +09:54 < wsa> Geert +09:54 < wsa> : wants to send v2 of MAX9611 fix +09:54 < wsa> Shimoda-san +09:54 < wsa> : wants to collect information about "R-Car Gen4" hardware IPs +09:54 < wsa> Ulrich +09:54 < wsa> : wants to take over the watchdog handover task from Wolfram +09:54 < wsa> Wolfram +09:54 < wsa> : wants to send more I2C API conversion patches after rc1, finish SCC clock +09:54 < wsa> handling for SDHI, update SDHI manual calibration, implement and send out +09:54 < wsa> prototypes for dynamic i2c adresses +09:54 < wsa> C - problems I currently have +09:54 < wsa> ----------------------------- +09:54 < wsa> None +09:54 < wsa> uli__: I took the liberty to add the watchdog task to your B) section because you agreed to that in Lyon :) I'll send you the details later this week, okay? +09:54 -!- Irssi: #periperi: Total of 17 nicks [0 ops, 0 halfops, 0 voices, 17 normal] +09:55 < wsa> Marex: are the PCI ranges discussions going well? +09:55 < uli__> okidok +09:55 < wsa> Marex: or are they stalled? +09:55 < wsa> any other questions/additions to the status updates? +09:57 < wsa> geertu: while updating periject, I found MSIOF patches in the BSP. However, one for H3 ES3.0 can't be checked because of no HW, and one working around issues for H3 ES1.0/1.1 is dropped because why? We can't reproduce? +09:57 < geertu> wsa: Because I never got it to work on H3 ES1 +09:58 < geertu> The logic analyzer showed that the clock starts and stops before the data starts and stops, so completely broken +09:59 < geertu> IIRC, I posted analyzer screenshots to periperi ML a few years ago +09:59 < wsa> so, basically: -EINVALID? +10:00 < geertu> yep +10:01 < wsa> ok, thanks for the heads up +10:03 < morimoto> \me "okidoki" sounds like "okidokei" for me. "okidokei" is "table clock" in Japan +10:03 < wsa> kbingham: about the I2C API conversion: I hope to get all i2c_new_device patches into 5.6 +10:03 < wsa> if that works out, I'll remove the outdated functions after 5.6-rc1 +10:03 < kbingham> wsa, Great. +10:03 < kbingham> Let me know if there's anything I can help with on those, though I suspect you've got it covered. +10:03 < geertu> morimoto: ticks like a table clock +10:04 < wsa> I want to send the i2c_get_dynamic_address prototype before that (= mid December, latest) +10:04 < wsa> then, we will see, if this is 5.6 material, too +10:04 < kbingham> that's when things get interesting of course :) +10:05 < wsa> do you need more information? +10:06 < wsa> I will share my sketch even before the prototype if there turns out to be something different than what we discussed so far +10:06 < kbingham> wsa, Not currently I don't think - feel free to cc me on patches directly if you want (then I'll be more likely to see them) +10:07 < wsa> will do +10:08 < wsa> ah, another topic: FOSDEM - just a high level view, who is going there? do we want a Renesas meeting there? +10:08 < geertu> wsa: I'll be there (20th time) +10:09 < wsa> geertu: nice anniversary! +10:09 < geertu> wsa: Yeah, FOSDEM will be celebrating too. +10:09 < kbingham> I plan to attend FOSDEM. +10:09 < uli__> i'll be back in EU in time for FOSDEM +10:09 < neg> I will attend FOSDEM +10:09 < geertu> uli__: to release some spiders in packed rooms? +10:09 < jmondi> I'll be in Brussels +10:10 < morimoto> No JaPari go there... +10:11 < wsa> morimoto: :( +10:11 < damm> I was considering going there +10:11 < wsa> damm: \o/ +10:11 < damm> but not sure +10:11 < wsa> ok, then I will plan to go there as well +10:11 < morimoto> I miss you guys (; ;) +10:12 * geertu too +10:12 < wsa> and the meeting again on the friday before? +10:13 < geertu> sounds good to me +10:14 < wsa> good, I'll plan accordingly +10:14 < wsa> next meeting, 2019-12-19? +10:15 * morimoto ok for me +10:15 < geertu> sounds good to me +10:15 < neg> I will be traveling on the 19th so not sure how much I can join from the road +10:15 < geertu> neg: Wifi on IcE? +10:15 < morimoto> neg: winter vacation +10:15 < morimoto> ? +10:16 < wsa> back to sweden +10:16 < neg> morimoto: Going home to family for Christmas +10:16 < morimoto> Nice ! +10:16 < neg> geertu: No IcE to Sweden :-( wifi from SAS +10:17 < geertu> neg: How will you attend FOSDEM in Sweden? +10:17 * geertu mixed dec 19 with jan 31, doh +10:18 < wsa> okay, I hope 2019-12-19 is okay then because I am not available on 2019-12-12 +10:19 < wsa> kbingham: 2019-12-12? +10:19 < geertu> wsa: BTW, have you looked into i2c clock rates? +10:20 < kbingham> wsa, I'm good with 12-12, (htough I presume pinchartl will re-gain control of the mm-meetings by then), 12-19 I might be out with baby activities. +10:20 < geertu> 2019-12-12 is fine for me, too +10:20 < wsa> you mean that your measurements showed some unexpected clocks? +10:21 < geertu> wsa: Yeah, 427 kHz instead of 397 kHz +10:21 < wsa> okay, then let's continue this by email so pinchartl can give his favourite choice +10:21 < wsa> geertu: not yet, slipped through the cracks :/ +10:21 < Marex> hello +10:21 < geertu> ok +10:21 < Marex> wsa: stalled, I will revisit them this weekend +10:22 < wsa> Marex: ok, thanks! +10:23 < Marex> sorry for being late +10:23 < wsa> no worries +10:23 < wsa> other questions? +10:23 < wsa> otherwise I think we are done +10:25 < morimoto> Thanks +10:25 < geertu> thx, and have a nice continued day +10:25 < neg> thanks all +10:25 < wsa> good, EOM, have a nice day everyone! -- cgit v1.2.3