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/20170426-mm-chatlog | 440 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 440 insertions(+) create mode 100644 wiki/Chat_log/20170426-mm-chatlog (limited to 'wiki/Chat_log/20170426-mm-chatlog') diff --git a/wiki/Chat_log/20170426-mm-chatlog b/wiki/Chat_log/20170426-mm-chatlog new file mode 100644 index 0000000..87fce2a --- /dev/null +++ b/wiki/Chat_log/20170426-mm-chatlog @@ -0,0 +1,440 @@ +Multimedia-chat-meeting-2017-04-26 + + good morning/afternoon [15:55] + morning + hi + morning + hello everyone [15:56] + everybody is in the room + but are kbingham and dammsan awake ? +* kbingham is definitely asleep + :-) [15:57] + Morimoto-san mentioned that he has a Renesas internal meeting at + 17:00, so let's get started and try to be quick + topics for the day + Topic 1. Status check for the multimedia tasks + Topic 2. Requests from the BSP team + (from Morimoto-san's e-mail) + Topic 3. OSS Japan trip + Topic 4. Next meeting + anything else ? [15:58] + I'll take that as a no + jmondi: wanna start ? [15:59] + yeah sure + status update, as reported in the email + A) + - RFC patches to move CEU driver away from soc-camera + - studied hw platform to test it with a real camera, and possibily + not from remote [16:00] + B) + - Add OF support to that driver and add support to RZ device tree for + CEU driver + - That would maybe require cooking up a device tree for GR-Peach, if + that will ever run mainline [16:01] + C = D = Null + -- eot -- + thank you + a device tree for GR-Peach would be cool + let's see what will happen + yeah, -would be- [16:02] + I've seen your ceu RFC, I'll review that + please bear with me :) + :-) + what do you mean by "possibly not from remote" ? [16:03] + will you get a Migo-R board ? + I don't think so +*** horms (~horms@217.111.208.18) has joined channel #periperi + what do you mean then ? :-) + I want to use a GR-Peach, as it's the only RZ board I have with VIO + signal routed to connectors to test the driver + otherwise, I will have to test it from remote, on Migo-R, in MAgnus' + board farm [16:04] + ok [16:05] + next, kbingham + So I have mostly been working on ADV7482 with neg. [16:06] + The driver is now split into two subdevices (as a staging process) + for HDMI and AIN/CVBS... + These are registered and linked by rcar-vin using the device and an + extra 'port' specifier to determine which one is which from the + single DT node. [16:07] + Niklas has also been looking at incremental registrations, and I + plan to follow his work to further split into more subdev's - such + that the rcar vin registers the TXA/TXB subdevs, and they in turn + then register links to both the AIN/HDMI [16:08] + I've also started work on getting my older patchsets up to date for + ML, and I hope to get those posted in the next couple of weekes. + [16:09] + FInally - I have successfully commenced a local fork() which is due + for completion around Late October, and thus I predict I will not + be able to attend ELCE this year + congratulations for that project ! you'll realize that, like + software development, it will keep you awake at night :-) + [16:10] + I work better at night :) [16:11] + congrats!! + kbingham: if I got this right, congrats! + Thanks :) + you mentioned in your e-mail report a minor bugfix to rcar-vin + [16:12] + has it been posted ? + Yes, it was posted. + It is *very* minor really :) + with a Fixes: tag ? + Indeed - with a Fixes: tag, and it should have a -renesas in the + authorship - so any automated tools should be able to pick it up if + they hvae been developed. [16:13] + thank you + Althoguh - as a trick to test the tooling ... + :-) [16:14] + it has been sent from git-send-mail which defaulted to from: + kbingham@kernel.org - however the Patch authorship is certainly + From: kieran.bingham+renesas@ + next, me [16:15] + I've worked on the MAX9286+MAX9271+OV10635 camera support + the first step is to get it working with the BSP kernel + status: done + the next step is to port it to mainline, using the BSP code for + the rcar-vin driver + status: done [16:16] + the next step is to move it from the legacy soc_camera rcar-vin + driver to the new rcar-vin driver + status: http://www.ideasonboard.org/frame-000008.jpg + nice!! [16:17] + impressive + the code is available from git://linuxtv.org/pinchartl/media.git + vin/gmsl + is that a famiclone? :) + I'll add my kernel config, my buildroot config and instructions to + capture images on the wiki + yeah, providing vin analogue for one of the boards [16:18] + I've also cleaned up the MAX9286+MAX9271+OV10635 code + it's split in two drivers, one for the max9286 and one for the + max9271+ov10635 camera (called rdacm20, after the name of the + camera) + they're both horrible + but we'll hopefully be able to fix that later + I've sent a list of hacks performed by the drivers at the I2C + level to Niklas to give him and Wolfram material for their work on + the topic [16:19] + for the next two weeks, I plan to clean up the code a bit more, + and concentrate on my base contract to address smaller VSP and DU + tasks (including requests from the BSP team for which Porimoto-san + sent a nice reminder) [16:20] + s/Porimoto-san/Morimoto-san/ + (P and M are next to each other on Belgian keyboards) + dammsan: would it be possible to install a small lamp in front of + the cameras ? it could even be something LED-based connected to + the camera power, so it would be off by default [16:21] + otherwise it's difficult to perform tests during most of the day + here :-) + i'll see what i can do + pinchartl: You just need to improve the contrast response for dark + images :) [16:22] + thank you [16:23] + I forgot to mention that the tests have only been performed with a + single camera + next, dammsan [16:25] + or maybe not [16:26] + maybe Magnus is now trying to find a lamp + in the meantime, next, morimoto + A) What have I done since last time + - OF-graph update, but nothing happen + - OV camera datasheet export paper work (Officially, you are not + yet received OV camera datasheet) + - kicked IMI guy for camera board question (you could received + information from them) [16:27] + - fixed sound noise issue which is reported from BSP team. I posted + fixup patch to ML and it was accepted + - I had meeting with BSP team. I and BSP team will have this + meeting once per month. we can talk it in Topic 2 + B) What I plan to do till next time + - continue OF-graph posting. Japan will have long holiday from 28th + April to 7th May. So I will repost before holiday + C) Problems I have currently + D) Posted/Accepted bugfix patch + No, Sir + --EOT-- + thank you + next, neg [16:28] + A) [16:29] + - Patch to support to V4L2 for incremental async subdevice binding + - Adapted VIN and CSI-2 patches to make use of incremental async, + the code is cleaner and it will support arbitrary pipeline + lengths, that is both on-board use-case (ADV7482) and 8 channel + prototype. + - Started to plan 8 channel i2c prototype meeting with Wolfram in + Stockholm. Due to take place Monday 8th of May. If anyone have any + concerns about this topic please send them to Wolfram and me. + Laurent have already provided lots of nice feedback from his work + with the existing code. + - Passthru mode of i2c traffic + The two max9286 are connected to the same I2C bus and by + default they seems to broacast I2C messages to the other side + over the GSML bus. The devices on the other side of the + max9286 have same i2c addresses so special care is needed + here. + - Shared power supplies for all cameras + There is a delay needed when powering on the cameras, in the + [16:30] + prototype code it's set to wait 8 secondes, per camera. + - I2C address translation + The max9286 support address translation which is both + problematic but could be used to solve the i2c passthru issue + if handled with care. + - Had discussions with Kieran to hand over the ADV7482 prototype. + B) + - Post patches for incremental async subdevice + - See if it's feasible to add a new V4L2 operation to help map a DT + port/endpoint to a media controller pad. If so post patches for + this and make use of it in the CSI-2 driver. + - Post new versions of Gen3 VIN and CSI-2 series to incorporate bug + fixes and reports from Kieran and Laurent and the incremental + async subdevice changes to create a better base for the 8 channel + prototype work. + C) + None + D) + None + --eot-- + thank you [16:31] + regarding B.2, I think it should be a media controller operation, + not a V4L2 operation + next, uli___ [16:32] + thanks, will start my work as a media controller operation then :-) + [16:33] + > A) What have I done since last time + Researched with Magnus on what we can hook up to the V2H board to get + a + working camera setup. (We drew a blank. While the MAX + serializer/deserializer chips are claimed to be compatible between + families + for basic operation, they do not all support the same physical + interfaces. + The existing Renesas camera hardware is coax, but the MAX9260 on the + V2H + board only supports STP...) + > B) What I plan to do till next time + Prototype for multiplexing the V2H board's four MAX9260s to one SCIF + using + the board's GPIO-based switch. + > C) Problems I have currently + None. + > D) Posted/Accepted bugfix patch + None. + (did that work? i'm having cut-and-paste problems here...) + anyway, EOT + it's definitely readable :-) [16:34] + thank you + Topic 2. Requests from BSP team [16:35] + morimoto: would you like to drive this, and explain about the + monthly meeting ? + OK [16:36] + I and BSP team talk about remaining request + some of them is new + some of them are already requested to you guys, but nothing happen + today [16:37] + * DU fence has missing feature + This is new + Can you read my email for detail ? + Maybe this is for Laurent (?) + * confirm DMA ATTR SKIP CPU patch + This is forgotten request [16:38] + Oops. + no + this is new one + I think Laurent or Kieran can handle it ? + Subject: VSP1 driver cache flush + Date: Mon, 17 Apr 2017 16:25:42 +0900 + I'll handle the DU/VSP IOMMU support as part of my base contract, + yes + Thanks + it will include the patch you mentioned + * confirm DU/VSPD initial sequence + This was requested long time ago [16:39] + Subject: Re: DU/VSPD initial sequence + Date: Wed, 11 Jan 2017 11:07:48 +0900 + I'll work on that with Kieran, depending on who finds time first + OK + BSP team want to get it until 7/M if possible + Is it possible ? + I think so, yes + Thanks + * confirm V4L2_FIELD_SEQ_TB/TB status + This is maybe for Niklas + + we might create an additional task for the second part of Q2 for + the DU/VSP initial sequence [16:40] + Subject: [periperi] Question about V4L2_FIELD_SEQ_TB/TB on VIN + Date: Tue, 7 Mar 2017 10:34:16 +0900 + yes, that's for Niklas I think + neg: what do you think ? + pinchartl: thanks + Yes, it's for me and I think it could be possible to add + V4L2_FIELD_SEQ_TB/TB + neg: nice to know + But I really hope at least the Gen2 cleanup sereis needs to be picked up + first since I made some mistakes in the oringal code regarding scaling + which would interfere with this [16:41] + neg: you can organize the branches any way you like, feel free to + develop on top of the Gen2 cleanup series + neg: no stress. I can explain it to BSP team [16:42] + pinchartl: do you have any commnets/idea for [1/5] ? + morimoto: regaring "DU fence has missing feature", you mentioned + in your e-mail + "Then, they created and tried gem_prime_res_obj.patch (I + attached)." + but you haven't attached anything :-) + Oops + I will + ofc, I just don't want to add more to the already 50+ pile out of tree + patches of VIN :-) And from the initial discussion this was a low prio + thing, if that changes I will ofc work ontop of the out of tree patches + thank you [16:44] + I think this closes this topic, unless you have something to add + I'll check the DU patch when I'll get it and reply by e-mail +* morimoto I posted mail which has mising patch/log [16:45] + thank you [16:46] + Topic 3. OSS Japan trip + first question, have you all booked your flights and hotels ? + I have booked flights - and *partial* hotel. + both booked [16:47] +* morimoto time to go to Renesas meeting + I have booked in the hilton from the 28th to the 3rd of june. + morimoto: have fun :-) + thank you for joining + but the hilton on the day I arrive (27th) and on the Saturday (4th) + are towards the end of 'prohibitively expensive' in my opinion + I have both flight and hotell booked [16:48] + I have booked the days that were available at the LF rate, or + similar. + kbingham: you have told me a few days ago that the hilton LF room + block seemed to have been fully booked. did you get any feedback + from the LF ? + The feedback was that the block had been fully booked on the + sunday, and that I could book from the monday ... + lovely [16:49] + I was then able to book the 'sunday night' at a rate *less* than + the LF rate - by booking that night separately. + :-) + The *saturday* night - is still Y 52,250 + And the Saturday night *after* is Y 45,000 + I'm afraid you'll likely have to consider a different hotel + So I have *not* booked for either of those nights. + I can recommend a much better hotel than the Hilton for that kind + of price :-) [16:50] + hehe indeed - unless anyone has a twin room and would let me crash + in their spare bed for the night :) + I'll arrive on Sunday morning so I'm afraid I can't help you :-) + kbingham: what was the total for your hilton booking? I think I got the + LF rates for all nights and my total was Y 211.300 [16:51] + neg: what are the dates ? + 28 May to 04 Jun [16:52] + For arrival I'll find something central and cheap that I can book + for the night before I arrive (at my own cost) so that I have a bed + to check into immediately on arrival if needed. + (I arrive at 7am, and I'd rather have a room I can dump my stuff in + - and get a shower) + kbingham: let me check my dates and what kind of room I have booked + neg: for the same dates I got ¥142,247 + taxes + service charge = + ¥174,998 + 29th to the 3rd, I got a total at 124,999 Y [16:53] + (whatever the service charge is...) + kbingham: I arrive the 27th as well + pinchartl: ohh that was inc taxes and serivce, without Y 172 000 + neg: I don't think you got all the nights at the LF rate then + [16:54] + pinchartl: thanks, just wanted to make sure they did not try to fool me + :-) [16:55] + neg: I'll let you see with Magnus what can be reasonably expensed + :-) + why is my rate so different from yours???? [16:56] + jmondi: What was your rate? + jmondi: what are your dates and rate ? [16:57] + May 28th - Jun 2ns ~30K + pinchartl: more expensive rooms just meens we need to bring larger + bottels of booze as gifts, right? + s/ns/nd/ + may 27th 57.500 + Jun 2ns - June 4th 31.500 + jmondi: Ouch :) + jmondi: I assume because you booked late and didn't get the LF + room block rate [16:58] + I assumed that was the LF rate + jmondi: Convert 57500 Yen to EUR :) + I don't think you can expense ¥57.500 for one night :-) + even ¥31.500 is quite high + [5~for domestic travel renesas usually limits to 10.000 jpy per + night [16:59] + some exception can be made for you guys, but 50.000 is way off + WHAAAAT? + jmondi: hahah + jmondi: I see you have converted :-) + jmondi: And now you've realised why I chose not to book that night + :) + dammsan: I assumed that the LF room rate would be acceptable, but + above that, it seems too high to me + I booked them in block assuming it was the LF rate [17:00] + I will cancel my reservation for the first night + luckily it's cancellable, yes + jmondi: Indeed - that's what I tried to do as well.. .... Where I + went wrong was checking to see what the breakdown of costs was :) + dammsan: ~30K Y is ok? + jmondi: if you try to book 29th to 3rd separately now you might + still be able to get the LF rate [17:01] + and possibly a good rate if you book the 28th separately too, as + Kieran did + anyway, I'll let you sort that out with Magnus [17:02] + pinchartl: jmondi: Sorry - small correction on the '28th being + cheaper' + from 28th to 2nd June I have 29500 + i think you should follow pinchartl + pinchartl: They tricked me - - They displayed the rate without + taxes, - it came through at 24K JPY + kbingham: ok + kbingham: I believe that's the LF rate + ¥25K / night [17:03] + that's roughly 200€ + jmondi: We should collaborate on our arrival hotel - and what ever + we get - get the same. + i think roughly 200 EUR is acceptable + dammsan: thank you for the confirmation + the other point I wanted to discuss [17:04] + is our plans for Saturday the 3rd + I propose spending the whole day together + yea Y 24 500 / night is what I also have + taxes and services + and while we can certainly visit Tokyo, several of us have done so + already [17:05] + kbingham: we should, let's sync offline + so another option is to spend the day outside town, doing + something a bit different + neg: I assume 24.500 + tax and services is roughly the 29.500 I have + for the 28th->2nd + for instance, a day trip to mount Fuji [17:06] + proposals are welcome + pinchartl: I would be very keen on a mount-fuji trip [17:07] + could you all have a look and tell me if there's anything you'd + like to see/do around Tokyo ? + pinchartl: I will reread Tokyo Vice and get back to you.. ;-) + dammsan: it's very likely less exotic for you, but recommendations + are welcome :-) + mount Fuji sounds fun, is it a valid trip during the rain seasson? + [17:09] + neg: that's where I'd like recommendations from our locals :-) + [17:10] + The biggest lesson I learnt last time was to next time bring more + t-shirts :-) + hehe [17:11] + Topic 4. Next meeting + I propose two weeks from now, on 2017-05-10, 08:00 GMT / 09:00 + CEST / 10:00 EEST / 16:00 JST [17:12] + http://zoomingjapan.com/travel/day-trips-from-tokyo/ + pinchartl: Ack on 10th May. [17:13] + 10th of May works for me + let's go for the 10th of May then [17:15] + it nobody has anything to add, I propose adjourning this + meeting. does anyone second ? + seconded + pinchart: i moved the cameras to let you look at the board leds + dammsan: thank you [17:16] + hopefully it is better + thank you all for attending -- cgit v1.2.3