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/20180509-mm-chatlog | 169 ++++++++++++++++++++++++++++++++++++++ 1 file changed, 169 insertions(+) create mode 100644 wiki/Chat_log/20180509-mm-chatlog (limited to 'wiki/Chat_log/20180509-mm-chatlog') diff --git a/wiki/Chat_log/20180509-mm-chatlog b/wiki/Chat_log/20180509-mm-chatlog new file mode 100644 index 0000000..a74ce94 --- /dev/null +++ b/wiki/Chat_log/20180509-mm-chatlog @@ -0,0 +1,169 @@ +Multimedia-chat-meeting-2018-05-09 + + kbingham: Wake up! + kbingham[m]: ^ + MultiMedia is in (cryogenic?) stasis... [17:20] + Maybe he is on some odd none EU timezone ;-) In the meantime shall we do + status reports individually in name order (jmondi, kbingham, morimoto, + neg, uli___ )? + neg: fine with me [17:21] + even if I guess, the important part is collecting it, more than + re-writing here what we reported by email + I can start though + - DRM bridge format support [PATCH 0/8] drm: bridge: Add support for + static image formats HAve to really look into comments, unfortunately + seems like we opened pandora's box of bridges lifetime management. + [17:22] + - MT9T111 media: i2c: mt9t112: Add OF tree support[3~ + - Gen-3 VIN parallel support on D3 [17:23] + capture now sort-of-wroking on v4.16 -> v4.17 has severe issues with + memory corruption while capturing + Until next time) + - Complete VIN parallel support (due date 5/M) [17:24] + - Re-tackle the bridges issues + - Have MT9T111 capture working on peach, so I can integrate it on + Armadillo + - soc_camera removal + Problems I have now) + - Capturing on v4.17 is very fragile + --eot-- + soc_camera removal \o/ [17:25] + neg: slow down, it's the third time in a row that it gets post-poned + to "until next time" [17:26] + is very low priority + morimoto: do you have status update for MM? [17:28] + OK + A) What have I done since last time + geertu: not bootargs to your scripts, but mtdparts to your + bootargs, which you are clearly passing already ... btw we can + continue the discussion in #perimtd if you want ( dammsan too ) + IRQ + OK, continue [17:29] + - Enjoyed GW ! + - DMAC driver error handling fixup + # Current DMAC driver is sharing error IRQ for all channels, + # but, it will be issue if we uses Virtual Machine, Multi OS, etc. + # We can handle it on each channel's IRQ handler + - Considering new PeriPeri tool (= periupport + peripelist = + "periject") + - Posted ALSA SoC cleanup patches final step + B) What I plan to do till next time + - Consider periject design + C) Problems I have currently + - I want to know each member's opinion about periject. + but on-email is very OK + -- EOF -- + sorry, i have to go home. bye! [17:30] +*** shimoda (~shimoda@relprex3.renesas.com) has quit: Quit: WeeChat 0.4.2 + any question ? + if no, next is neg + So far I like the name periject :-) + thanks + rcar_csi2_write(priv, PHYCNT_REG, PHYCNT_RSTZ); + rcar_csi2_write(priv, PHTC_REG, PHTC_TESTCLR); [17:31] + wops + A) + - Posted and got merged second batch of VIN enhancement patches. + - VIN M3-N done. + - Rework CSI-2 based on datasheet v1.0, new patches pending. + - Investigated ADV748x behavior of AFE pixel clock. + B) + - More CSI-2 work + - Post next batch of VIN patches that piled up prior to Gen3 merger. + [17:32] + - Post fix for ADV748x + - Post prototype for v4l2-subdev video standard control + C) +* geertu joined #perimtd + - CSI-2 rework will maybe make it too late for v4.18 :-( + -- eot -- + if no questions please go a head uli___ [17:33] + A) + MM: wikified the instructions for running the IGT test suite + (https://elinux.org/R-Car/Tests:igt) + MM: rebasing IGT DU fixes, WIP + MM: adding DU support to D3, WIP + B) [17:34] + MM: finish DU on D3 + MM: send a new IGT DU fix series + C) + none + correction: C) copy-and-paste doesn't work very well in xfce terminal + that's it [17:35] + thanks, out of curiosity is there any DU work for M3-N in the pipeline? + not from me [17:36] + neg: I think Kieran was about to work on that + jmondi: ok thanks I'm just curious [17:37] + anything else we need to discuss for MM, I had counted on kbingham to + handle this so I have nothng prepared but have not read all status mails + in detail if there where any open questions + I have nothing [17:39] + neg: I only have the issues with v4.17 capture not working + none here + neg: [PATCH v2 00/11] r8a77965: M3-N DU Enablement + but actually v4.16 behaves the same, I'm finding out as we speak + geertu: thanks how could I miss that, I need a beter interface to gmane + archive I keep missing patches [17:40] + jmondi: how exactly does it not work? [17:41] + uli___: by 'randomly' hangs the CPU while capture operations is + starting [17:42] + uli___: yesterday Niklas suggested that power cyclcing the board + would help as it may be some v4.17 memory corruption issue + [17:43] + ?? + Have I just walked into a meeting that I didn't know was happening + ? + uli___: and it actually did, this morning I re-based on v4.16, first + boot was ok, but now I still need to power cycle to have capture + working + jmondi: have you nailed it down to know if s_stream() have been called + or if it's the set_fmt() that is the last v4l2 callback? [17:44] + kbingham: meeting is almost ending stage now :) + morimoto: Oh my ... I'm sorry ! I thought meetings were thursdays! + neg: with strace I see g_fmt being called and that's it + kbingham: :-) + but I would not trust strace too much to debug these kind of issues + kbingham: :) [17:45] + jmondi: i think some trace printouts in rcar-vin/rcar-dma.c would be + usefull to know if it's s_stream() or something else cousing the lockup + [17:46] + neg: you see, it is freaking 'random'.. I've been capturing images + for a good 2 hours, rebooted the board, no kernel updates, now it + hangs + neg: M3-N DU should be in renesas-drivers already. [17:47] + neg: I was not correct, I changed the pixel clock polarity between 2 + reboots, I hardly think that can hang the CPU [17:48] + jmondi: ouch that is bad, I had the impression it always failed on the + second capture attempt by bad + btw, let's tak it offline, I have nothing else for the meeting + neg: no, I made several captures in a row, until I have rebooted the + board [17:49] + Yes lets keep talking about that later to not hold everyone up :-) + So Shall I post my ABC ... and then that covers the status' :D + kbingham: please do so if you have it handy :-) [17:50] + Thursday 10th May + + A) What I have done since last time + - M3-N DU Enablement + - Got JTAG working with OpenOCD and Salvator-XS + - TLB-Opimise v7,8,9 + - DU/Interlaced v3, v4 + B) What I will do next + - DMA Virtualisation + C) Any issues I have currently + - None + Ahem ... ignore the first line ... [17:51] + I'll post that to the ML as a late addition + thanks, I think the last item on the agenda is to pick who will record + the MM log into the format pinchartl usually do and make sure it's sent + out and recorded in the wiki and what else normaly happens with it + [17:52] + neg: I think that was supposed to be me - but I'm not certain I + have all the scrollback ... [17:53] +*** horms (~horms@a80-127-179-77.adsl.xs4all.nl) has quit: Ping timeout: 264 + seconds + neg: I can put it to wiki [17:54] + kbingham: can you create it by using wiki ? + morimoto: Sure :) + kbingham: I can email you the full scrollback if you need it [17:55] + neg: morimoto: - An e-mail is probably easier thanks -- cgit v1.2.3