Multimedia-chat-meeting-2018-01-25

09:42 < pinchartl> so welcome to the multimedia meeting
09:42 < pinchartl> I think we have a full house today
09:42 < pinchartl> jmondi, kbingham[m], dammsan, morimoto, neg, uli___, yes
09:42 < pinchartl> first topic, status updates
09:43 < pinchartl> from last to first, let's start with Morimoto-san
09:43 < pinchartl> I'll post the update and ask for comments, like last time
09:44 < pinchartl> Since last meeting:
09:44 < pinchartl> - Posted ALSA SoC framework main cleanup patches
09:44 < pinchartl> Patches are too big, asked each driver author to test them. Few issues are already noticed and fixup patches posted.
09:44 < pinchartl> - Export paper work for datasheet, schematic, board, etc
09:45 < pinchartl> Until next meeting:
09:45 < pinchartl> - Continue the ALSA SoC framework things
09:45 < pinchartl> Issues and Blockers: None (other than paperwork killing your soul)
09:45 < pinchartl> any comment ?
09:47 < morimoto> no comment
09:47 < pinchartl> while waiting for comments, let's continue with Niklas
09:47 < pinchartl> ok :-)
09:47 < pinchartl> thank you
09:47 < pinchartl> neg:
09:47 < pinchartl> Since last meeting:
09:47 < pinchartl> - [PATCH 0/5] GMSL: enable multiple simultaneous streams from the same MAX9286
09:47 < pinchartl> - [PATCH] v4l2-dev.h: fix symbol collision in media_entity_to_video_device()
09:47 < pinchartl> - Prepared VIN, CSI-2 and multiplexed patches for the GMSL code camp
09:47 < pinchartl> Until next meeting:
09:47 < pinchartl> - Media code camp working on GMSL related stuff..
09:47 < pinchartl> - Post next versions of VIN, CSI-2 and multiplexed pads series
09:47 < pinchartl> - Look if rcar-vin can more aggressively switch to continues capture  mode if it due to buffer starvation enters single capture mode.
09:47 < pinchartl> - Start on DU integration for V3M.
09:47 < pinchartl> Issues and Blockers:
09:47 < pinchartl> - Laurents excellent review comments on VIN have resulted in a rewrite of some parts of the driver. End result is much cleaner but have taken more time than expected.
09:47 < pinchartl> any comment ?
09:48 < neg> Thanks for your comments, other than that no :-)
09:48 < pinchartl> next, Jacopo
09:48 < pinchartl> Since last meeting:
09:48 < pinchartl> - v4/5/6 of the CEU driver
09:48 < pinchartl> Rebased on Hans' parm branch, fixed v4l2-compliance issues.
09:48 < pinchartl> - Add DTS support to ov7670 driver
09:48 < pinchartl> This was needed to test CEU polarities, now waiting for DT bindings ack.
09:48 < pinchartl> - Build and test the Cogent GMSL Yocto layer
09:48 < pinchartl> - Got FSYNC working
09:48 < pinchartl> Compared Cogent's settings again then niklas->magic() and got fsync working 
09:48 < pinchartl> keeping reverse communication channel open as GPO transitions are sent through 
09:48 < pinchartl> it.
09:48 < pinchartl> Until next meeting:
09:48 < pinchartl> - GMSL Code Camp: consolidate setup and test fsync reliability
09:48 < pinchartl> - Brussels FOSDEM
09:48 < pinchartl> - Handle frame rate setting in the ov7720 driver
09:48 < pinchartl> This implies working on Migo-R clocks and reverse engineer a poorly documented 
09:48 < pinchartl> sensor. Hans won't take the driver otherwise, or we can park it in staging.
09:48 < pinchartl> Issues and Blockers: None
09:48 < pinchartl> any comment ?
09:49 < jmondi> nope
09:49 < jmondi> that's all
09:49 < pinchartl> thanks
09:49 < pinchartl> next, Ulrich
09:49 < pinchartl> Since last meeting:
09:49 < pinchartl> - Attempted to get mainline-patched GSX driver to work with Yocto
09:49 < pinchartl> Until next meeting:
09:49 < pinchartl> - Multimedia meeting in Belgium
09:49 < pinchartl> - Brussels FOSDEM
09:49 < pinchartl> - Multimedia-related PFC upstreaming for Gen3 SoCs
09:49 < pinchartl> Issues and Blockers:
09:49 < pinchartl> - The GSX driver still doesn't work (except for OpenCL)
09:49 < pinchartl> Even the officially sanctioned Yocto userspace fails, so it seems increasingly
09:49 < pinchartl> unlikely that it is userspace-related. Help from someone (i.e. Laurent) to 
09:49 < pinchartl> check if the up-port of the DRM bits in Rogue driver makes sense when we meet 
09:49 < pinchartl> in Brussels would be useful.
09:49 < pinchartl> any comment ?
09:50 < uli___> please help me. :)
09:50 < pinchartl> :-)
09:50 < morimoto> :)
09:50 < pinchartl> I think we can have a look at it in Brussels
09:50 < uli___> ok, thanks
09:50 < pinchartl> can you make sure to prepare everything to avoid spending time with build or other similar issues ?
09:51 < uli___> i'll prepare everything
09:51 < pinchartl> you will arrive on Thursday, right ?
09:51 < uli___> yes, early afternoon
09:51 < pinchartl> let's try to address that on Thursday later afternoon then
09:52 < uli___> ok
09:52 < uli___> there's going to be an h3 board there, right?
09:52 < pinchartl> I'll have a kingfisher with an H3SK
09:52 < pinchartl> and Kieran will bring a Salvator-XS
09:53 < pinchartl> next, Kieran
09:53 < pinchartl> * Kieran
09:53 < pinchartl> Since last meeting:
09:53 < pinchartl> - GMSL investigations and Yocto builds with Jacopo
09:53 < pinchartl> Extracted the Cogent Kernel so we can build independently.
09:53 < pinchartl> - ADV748x TXB lane power investigation and support
09:53 < pinchartl> - vsp1/tlb-optimise/v5 (rebase for updated DRM/UIF)
09:53 < pinchartl> - Eagle-V3M Display testing
09:53 < pinchartl> - ADV748x invalid page mapping fix
09:53 < pinchartl> - ADV7511 device tree I2C address mapping
09:53 < pinchartl> - ADV7604 device tree I2C address mapping
09:53 < pinchartl> Until next meeting:
09:53 < pinchartl> - GMSL Code Camp
09:53 < pinchartl> - Brussels FOSDEM
09:53 < pinchartl> - H3 ES2.0 LVDS + VGA Performance Investigation
09:53 < pinchartl> Issues and Blockers:
09:53 < pinchartl> - Draak D3 I2C support not yet integrated into renesas-drivers
09:53 < pinchartl> Draak ADV7511/ADV7612 development is based on out-of-tree patches.
09:53 < pinchartl> any comment ?
09:54 < kbingham> That's it - except for taking advantage of Uli being here so I can ask if he plans to work on the D3 i2c patches anytime (it doesn't matter if you don't plan too - I think geertu might pick the patches up for next renesas-drivers anyway, or I can base on the ones I have)
09:55 < kbingham> or rather uli___:  ^ :D
09:55 < uli___> no immediate plan, but that's mostly because i forgot about those
09:55 < pinchartl> that was my question too, what are the plans to get that upstream ?
09:55 < uli___> i'll have a look
09:56 < kbingham> Ok, that's me done for today then :D
09:56 < pinchartl> thank you
09:57 < pinchartl> oh, last time you mentioned you were planning to resubmit kmstest verification based on review comments
09:57 < pinchartl> any update on that ?
09:59 < kbingham> Nope - it got stalled, blocked by other tasks - so I'll try to get that done this cycle.
10:01 < pinchartl> there's no hurry, but please keep it on your todo list
10:01 < pinchartl> I got the order wrong and nearly forgot Jacopo again
10:01 < pinchartl> Since last meeting:
10:01 < pinchartl> - v4/5/6 of the CEU driver
10:01 < pinchartl> Rebased on Hans' parm branch, fixed v4l2-compliance issues.
10:01 < pinchartl> - Add DTS support to ov7670 driver
10:01 < pinchartl> This was needed to test CEU polarities, now waiting for DT bindings ack.
10:01 < pinchartl> - Build and test the Cogent GMSL Yocto layer
10:01 < pinchartl> - Got FSYNC working
10:01 < pinchartl> Compared Cogent's settings again then niklas->magic() and got fsync working 
10:01 < pinchartl> keeping reverse communication channel open as GPO transitions are sent through it.
10:01 < pinchartl> Until next meeting:
10:01 < pinchartl> - GMSL Code Camp: consolidate setup and test fsync reliability
10:01 < pinchartl> - Brussels FOSDEM
10:01 < pinchartl> - Handle frame rate setting in the ov7720 driver
10:01 < pinchartl> This implies working on Migo-R clocks and reverse engineer a poorly documented 
10:01 < pinchartl> sensor. Hans won't take the driver otherwise, or we can park it in staging.
10:01 < pinchartl> Issues and Blockers: None
10:01 < pinchartl> any comment ?
10:02 < jmondi> you have pasted my report already :)
10:02 < jmondi> this time I don't feel left out :)
10:03 < jmondi> and no comments neither this time!
10:03  * pinchartl needs to wake up -_-'
10:03 < pinchartl> a few questions though
10:04 < pinchartl> do you still need support from Omnivision and Maxim ?
10:04 < jmondi> for GMSL?
10:04 < jmondi> I guess we'll find out once we can test fsync stability a bit more in Brussels
10:05 < morimoto> jmondi: I forwarded their response for you. does it works ?
10:05 < pinchartl> of course, but is there any open question for which we're still waiting for an answer ?
10:05 < morimoto> About register setting list
10:05 < jmondi> everything was revolving around fsync, now that niklas has made it working everything else is secondary
10:06 < pinchartl> ok, thanks
10:06 < jmondi> I guess we'll may need support when implementing support for more image resolutions
10:06 < jmondi> morimoto: yes thanks, that would be required when changing the image sizes
10:06 < pinchartl> finally, myself
10:06 < pinchartl> Since last meeting:
10:06 < pinchartl> - Prepared the FOSDEM code camp
10:06 < pinchartl> - DU LVDS rework
10:06 < pinchartl> - Patch review
10:06 < pinchartl> - Started virtualization investigation
10:06 < pinchartl> Until next meeting:
10:06 < pinchartl> - GMSL Code Camp
10:06 < pinchartl> - Brussels FOSDEM
10:06 < pinchartl> - Virtualization investigation
10:06 < pinchartl> Issues and blockers: None
10:08 < morimoto> jmondi: nice to know
10:08 < pinchartl> so that's it for the status update
10:08 < pinchartl> any question or comment ?
10:09 < morimoto> yes
10:09 < morimoto> pinchartl: I still can't find my DU 2 PLL fixup patches on linux-next.
10:10 < pinchartl> morimoto: that's because I still haven't sent the pull request. as the merge window is about to open the DRM tree is currently frozen
10:10 < pinchartl> I will send it as soon as the merge window closes
10:10 < morimoto> OK, your branch is not connected to linux-next directly (I don't know detail of it)
10:11 < pinchartl> no, it gets in linux-next through the DRM tree
10:11 < morimoto> Thanks ! nice to know
10:12 < pinchartl> dammsan: anything to report by any chance ? :-)
10:12 < dammsan> nope, sorry =)
10:12 < dammsan> just that i'm currently discussing your task proposals
10:13 < pinchartl> that at least is nice to hear
10:13 < dammsan> hope to get back to your about that tomorrow
10:13 < pinchartl> which leads to
10:13 < pinchartl> Topic 2. Additional Tasks for 2018 Q1
10:13 < pinchartl> Additional tasks for 2018 Q1/1 have been approved, and candidates for 2018 
10:13 < pinchartl> Q1/2 submitted. The goal is to agree on the second batch for the end of 
10:13 < pinchartl> January.
10:13 < pinchartl> I assume you've all seen the proposals for Q1/2
10:15 < kbingham> yes, (now refreshed for a second time)
10:16 < pinchartl> neg: what would you think about the single/continuous capture mode support in VIN for Q1/2 ? it seems the BSP team would like to have it sooner than later
10:16 < neg> pinchartl: was just about suggest that so it would work good for me :-)
10:18 < pinchartl> dammsan: would that be OK with you ?
10:20 < dammsan> sure of course
10:20 < pinchartl> can you add it to the list of tasks to discuss with Renesas then ?
10:20 < dammsan> most important is to keep upstream focus though, so as long as we don'tloose that
10:20 < dammsan> i can
10:20 < dammsan> and will
10:21 < pinchartl> thank you
10:21 < pinchartl> jmondi, kbingham, uli___: any comment on the proposed tasks ?
10:21 < neg> dammsan: that task do not depend on VIN Gen3 support being merged first :-)
10:22 < uli___> i would like to look into the size and quality of that igt test suite before deciding whether that is 5 days
10:22 < uli___> other than that, i'm happy
10:22 < dammsan> neg: ok, not sure if it is good or bad =)
10:23 < pinchartl> uli___: ok. you won't need to get all tests running, an initial subset would be enough
10:23 < uli___> ok
10:23 < jmondi> For me D3 VIN supports seems fine, I'm not sure everythihg we need is upstream (ie D3 i2c). I have to made sure any of the camera modules I have may be connected to D3 expansions
10:23 < jmondi> and, what's DISCOM? :)
10:24 < pinchartl> it's a VSP module that computes CRCs
10:25 < jmondi> target platforms? I have an M3-W and a D# here
10:25 < jmondi> nice D#.. D3 I meant
10:27 < pinchartl> M3-W will work
10:27 < neg> jmondi: V3M also have a parallel input on its expansion board and there i2c works and I have verified the HDMI/CSI-2 input on the expansion board if all else fails
10:28 < jmondi> neg: nice, but I don't have V3M... ofc there's the remote option, but I need to wire a camera to the expansion headers
10:30 < pinchartl> next topic, GMSL code camp
10:30 < pinchartl> by now I assume you all have sorted out your travel plans
10:30 < pinchartl> and know what to bring
10:30 < pinchartl> please make sure you enter your travel plans in the wiki
10:32 < jmondi> FYI: https://osdr.renesas.com/projects/linux-kernel-development/wiki/Periperi-2018-02
10:32 < pinchartl> I will post an agenda proposal for the Thursday afternoon multimedia meeting
10:32 < pinchartl> regarding the code camp itself I think the agenda is quite simple
10:32 < pinchartl> any question ?
10:33 < kbingham[m]> Neg, can you provide our latest gmsl branch to test?
10:34 < kbingham[m]> That is assuming that your latest patches are the most recent work
10:34 < neg> kbingham[m]: I'm working on bulding it, got gready and wanted the latest VIN patches as it's base. As soon as it's done I will provided a tag
10:35 < kbingham[m]> Great
10:35 < pinchartl> thank you
10:36 < pinchartl> regarding logistics, I will likely arrive in Brussels first
10:38 < neg> I will arrive Sunday BRU 1900 if anyone want to share a cab
10:38 < pinchartl> any other question ?
10:39 < jmondi> and I'll land at 19.35 if I'm not wrong
10:39 < jmondi> no question though
10:39 < kbingham> Best ways of contacting people upon arrival ?
10:39 < kbingham> jmondi - whatsapp, pinchartl sms, neg ?
10:39 < pinchartl> sms or phone for me, yes
10:39 < kbingham> (kb, IRC, whatsapp, or sms)
10:40 < neg> kbingham[m]: phone or sms is best for me
10:41 < jmondi> IRC, telegram or if no alternatives whatsapp
10:42 < pinchartl> any other topic to discuss ?
10:42 < neg> not from me
10:43 < pinchartl> I then propose adjourning this meeting. any objection ?
10:43  * kbingham seconds
10:43 < geertu> jmondi: Please don't use telegrams to contact me. The service was stopped in Belgium on 2017-12-29.
10:43 < pinchartl> meeting adjourned
10:43 < pinchartl> thank you all for attending