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/20160803-mm-chatlog | 277 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 277 insertions(+) create mode 100644 wiki/Chat_log/20160803-mm-chatlog (limited to 'wiki/Chat_log/20160803-mm-chatlog') diff --git a/wiki/Chat_log/20160803-mm-chatlog b/wiki/Chat_log/20160803-mm-chatlog new file mode 100644 index 0000000..d26a6ab --- /dev/null +++ b/wiki/Chat_log/20160803-mm-chatlog @@ -0,0 +1,277 @@ +Multimedia-chat-meeting-2016-08-03 + + hi all [16:22] + hello + hello + I don't think Kieran or Magnus will join us today [16:24] + so everybody is here + let's thus get started [16:25] + hi + I've asked you all to send task status by e-mail before the + meeting, and you have all done so + thank you :-) + let's see if we can speed this up, we'll cap the meeting to one + hour max [16:26] + we also don't have to go through task status in details + we can try the scrum-style meeting and just report work done, work + planned, and blockers/issues [16:27] + really sorry I need to let the postman in at the door, brb please go + head without me + an announcement first + I've submitted additional tasks for Q3 to Morimoto-san [16:28] + we have exchanged a few e-mails about them, hopefully everything + is on track now + morimoto: do you still need more information from me ? is there + anything I can do to help ? + Now, shimoda-san and our boss is checking it. + or is everything fine ? + is that a good sign ? :-) [16:29] + pinchartl: please wait. please start meeting first [16:30] + well, I'll assume it's not a bad sign :-) + that's all I wanted to announce on this topic + I've also noticed that Salvator-X M3 boards have started shipping + [16:31] + so let's get ready for integration work and testing on M3 + pinchartl: starting "paper work", not shipping ;P [16:32] + pinchartl: I send question mail to you. please check it + well, paperwork is the first step for shipping :-) + I will right after the meeting + back, sorry about that + neg: no worries + I'll give you a minute to read the log. any question ? [16:33] + thx, I'm good + ok, let's go round the (virtual) table then [16:34] + in alphabetical order as usual + using the real alphabetical order this time, I'll start + since last meeting in Japan three weeks ago + - there was RenesasCon and LinuxCon Japan [16:35] + followed by a week of holidays + leaving a week and a half of work + - I've continued working on the request API. Hans Verkuil is back + from holidays, I've discussed contention points with him and + Sakari Ailus [16:36] + in the end there was no more disagreement with my proposal, so + I've continued working on the implementation [16:37] + - I've also started IPMMU + DU integration, targetting Gen3 + the result can't be tested properly on H3 as the IPMMU is known to + be faulty + partial tests will be performed on Gen2 by hooking the VSP1 to the + DU the same way as we do on Gen3 [16:38] + - last but not least, I acted as Magnus' deputy for additional + tasks negotiation + during the next two weeks, I will [16:39] + - continue working on IPMMU + DU and the request API + - continue Kieran's work on the VSP image partitioning + implementation + (Kieran has left for his honeymoon and will be back at the end of + the month) [16:40] + issues and blockers: + - the IPMMU is faulty on H3, blocking full testing of the IPMMU + + DU integration, but that's a known problem and not a blocker as + explained above [16:41] + no other issue for me + ah, I will also during the next two weeks try to get the VSP HGO + support upstreamed [16:42] + a new iteration of the patch series might be needed with minor + changes, I don't expect any problem + that's it for me + Morimoto-san, you're next in the alphabetical order [16:43] + OK, + I have posted cleanup patches which is needed for OF graph. [16:44] + but still no responce from maintainer. I wonder is Europe under + summer vacation now ?? + 1 - 1.5 month, no responce + some people must be [16:45] + OK + who is the maintainer ? + Mark Brown ? + Yes + Do you know his situation ?? + he has been quite active on the kernel summit mailing list lately, + so he's definitely alive + OK alive. but no responce... [16:46] + Anyway, because of this, I started to solve other headache + he doesn't seem to be on vacation + you can ping him + Sometimes, he post his mail, but he doesn't accept patches, not + only me. [16:47] + So now, I started to solve other headache which is "unload" issue + on ALSA SoC [16:48] + ah + a big one + I've seen your e-mails on that + the topic was also mentioned by Lars in the kernel summit mailing + list + Yes. ALSA SoC has same issue [16:49] + that's related to hotplug support, right ? + Yes. + especially, hot-unplug [16:50] + ok + I'm not sure how to solve this issue, but I started to investigate + ALSA SoC framework, and I noticed that it has many duplicate + implementation. + It makes hotplug support difficult I think [16:51] + So, I would like to cleanup ALSA SoC + I think you can discuss it with Lars if needed, he seems quite + interested in this topic as well + Now, I'm asking about it ot ML. + Nice idea. [16:52] + I think I can have a chance to talk him on next ELCE ? + I would expect so, yes + Mark Brown should hopefully be there too + I hope so + maybe you should schedule a meeting with them at ELCE + I would be interested in joining + sounds nice for me [16:53] + with beer ? + Anyway, this is current my status. + :-) + I think this "hotplug" is requested for HDMI ? [16:54] + yes + well, I don't know how HDMI audio is implemented in ALSA + and whether unplugging the cable will remove the device or not + In my understand, "unplugging cable" and "unload driver" are + different problem. [16:55] + But, some of them can be related ? + no sure + they can be, but that depends on how ALSA handles it. I don't know + is that something you can investigate ? + I think so. [16:56] + thanks + what is your plan for the next two weeks ? + For this purpose, my 1st step is cleanup framework. It is now tasty + spaghetti + 1) continue OF graph related patch work [16:57] + 2) investigate and cleanup ALSA SoC + It is related Mark's situation + any issue or blocker, apart from Mark being unresponsive ? [16:58] + no blocker. + thank you [16:59] + Oops, export paper work sometimes block me :) + :-) + neg: you're next + since last time: Working on addaptions to rcar-vin to keep up with + patches posted for adv7180 and help out Sergie with his problem. Added + ALTERNATE field support to rcar-vin + plan: Keep pushig for those patches and once they are picked up start to + break out patches from my Gen3 VIN series and post them in smaller + chunks to try and get some tracktion on them + issues: No reviews on the VIN Gen3 and CSI-2 patches and unclear how to + handle ADV7482 tasks. + I suppose the "no review" is a hint for me ? :-) [17:00] + :-) + I'll get to that [17:01] + regarding ADV7482, would you like to discuss it at some point ? + np, if you are super swamped maybe you can hold off abit untill I start + sending out break out parts of the Gen3 series and review them + early next week would work best for me if that's fine with you + [17:02] + Monday or Tuesday + yes I would like to discuss ADV7482, just let me know when you have some + time + (I'll be unavailable next Wednesday) + ok [17:03] + sure, Monday morning and between 15-17 I will have builders starting + construction but other than that just ping me when you have time + Monday 13:00 your time ? + works + ok [17:04] + uli___: you're next + for work done, see the status update + planned is to start on the additional tasks, plus deal with this: + issue: + the hdmi gen3 output needs to read the product register to handle + es1.1 [17:05] + ouch + right now, that is a hardcoded register access + which people dislike + in response, dirk behme wrote a driver + which people consider overkill, i guess :) + the last alternative is to code that in the DT, which i consider a + technical fail, considering it can be autodetected + any opinions on how to tackle this? [17:06] + why does the hdmi code need the product register value ? + what is handled differently ? + i must admit i have not looked into what it exactly does :) maybe + morimoto knows? + about ES1.1 ? [17:07] + yes + Unfortunately, ES1.0 and ES1.1 have different behavior [17:08] + on HDMI + is the code that handles the ES1.0/ES1.1 differences public ? + it's from the bsp [17:09] + where I can get it from ? + morimoto-san sent an email about that to periperi [17:10] + as a response to a group meeting summary + Then, apply this new version of DPLL support patch from BSP. + But, you will get conflict, but it is not difficult to fix. + 01b4818ac558f17f7c74505003c5cca2fc149de1 + (drm: rcar-du: Add DPLL support) + Above DPLL support needs new header from BSP. + 9c4c8fb9e6c11fb9594e3edaccc1c73976e0cfe6 + (soc: renesas: Add product register helpers) + what's the mail's subject ? + "Renesas Multimedia Group Meeting" :) [17:11] + Re: [periperi] Renesas Multimedia Group Meeting + it's from june 2 + Date: Thu, 2 Jun 2016 01:17:13 +0000 + + got it + I will have a look + It came from BSP + uli___: when do you plan to address that ? [17:12] + (to know what my deadline is to look at the issue) + in the not too distant future, if possible + i actually wanted to send it out yesterday, then i remembered that + this isn't addressed yet [17:13] + could you be slightly more precise ? :-) + in a week? + or two? [17:14] + ok, I'll try to check that on Monday too [17:15] + is that fine ? + yes, perfectly fine. thanks. + you're welcome + I and Magnus had discussed about that, we can use Geert's DT + compatible magic ? I believe it will add es version on compatible. + "r8a7795-salvator" -> "r8a7795-salvator-es1.1" "r8a7795-salvator" + that's the option i'd like to avoid if at all possible + OK [17:16] + but i can deal with it, if necessary + I also wonder how much work we should put into that, given that es + 1.0 is meant to disappear + whatever solution we come up with, it must not make es 1.1 support + too complex or dirty + anyway, I'll have a look [17:18] + ok, thank you + any last comment from anyone ? + I'll take that as a no [17:19] + thanks for steping up as Magnus deputy :-) + you're welcome + I propose scheduling the next meeting in two weeks, Wednesday the + 17th, at the usual time (half an hour later than today) + would that be fine for everybody ? + OK for me [17:20] + fine for me + Not OK for me + :-/ + it is under summer vacation + when are your summer vacation ? + 13 - 21 + 13th Aug to 21th Aug I mean [17:21] + I give you permission to skip the meeting then :-) + :) + if you could send a status report either before leaving for + vacation, or after coming back, it would be appreciated + I will be in Berlin from tomorrow to sunday, so I might be slow in + responding during that time [17:22] + pinchartl: OK, I will try + morimoto: thank you + neg: ok, thanks for the information + on the same topic, I will be on vacation from Saturday the 20th to + Sunday the 28th [17:23] + we've reached the one hour limit + and we're done with the meeting, so it's a good timing + thank you everybody, and have a nice day in Europe or evening in + Japan [17:24] + thanks all + Thanks ! -- cgit v1.2.3