Multimedia-chat-meeting-2019-04-04

10:13 < pinchartl> welcome to the multimedia meeting
10:13 < pinchartl> Topic 1. Status Check for the Multimedia Tasks
10:13 < pinchartl> * Jacopo
10:13 < pinchartl> Since last meeting:
10:13 < pinchartl> - [RFC 0/5] media: Implement negotiation of CSI-2 data lanes
10:13 < pinchartl> - [PATCH v4 00/31] v4l: add support for multiplexed streams
10:13 < pinchartl> - Patch review
10:13 < pinchartl>   - [PATCH v4 0/7] TVP5150 new features
10:13 < pinchartl>   - [PATCH v3 2/2] media: Introduce helpers to fill pixel format struct
10:13 < pinchartl> Until next meeting:
10:13 < pinchartl> - v5 of multiplexed stream support + data lane negotiation
10:13 < pinchartl> Issues and blockers: None
10:14 < pinchartl> I believe Jacopo is busy getting is mouth tortured by a dentist
10:14 < pinchartl> * Kieran
10:14 < pinchartl> Since last meeting:
10:14 < pinchartl> - DU group handling refactoring
10:14 < pinchartl> - UDS phase handling in VSP partition algorithm
10:14 < pinchartl> - Linaro Connect in Bangkok
10:14 < pinchartl> Until next meeting:
10:14 < pinchartl> - Finish Linaro Connect
10:14 < pinchartl> - Complete UDS phase handling in VSP partition algorithm
10:14 < pinchartl> - Work on the DU group rework issues reported by Test Team
10:14 < pinchartl> Issues and blockers: None
10:14 < pinchartl> kbingham: any comment ?
10:15 < kbingham> That' sums it up :)
10:15 < pinchartl> thank you
10:15 < pinchartl> * Laurent
10:15 < pinchartl> Since last meeting:
10:15 < pinchartl> - Finished the LVDS dual-link prototype
10:15 < pinchartl> - Submitted DU pull requests (writeback support, misc fixes)
10:15 < pinchartl> - Added support for missing RGB formats in the VSP and DU drivers
10:15 < pinchartl> - Prepared multimedia plan for face-to-face meeting
10:15 < pinchartl> - Face-to-face meeting with Renesas in Japan
10:15 < pinchartl> Until next meeting:
10:15 < pinchartl> - Move forward with the LVDS dual-link prototype
10:15 < pinchartl> - Prepare 2019 Q2 additional tasks in sync with the multimedia
10:15 < pinchartl>   development plan
10:15 < pinchartl> Issues and blockers: None
10:15 < pinchartl> (let's handle the face-to-face meeting as part of the discussions after the status update)
10:15 < pinchartl> any question ?
10:16 < neg> Not from me
10:16 < morimoto> Thank you for F2F meeting at Renesas
10:16 < pinchartl> thank you for hosting it :-)
10:16 < pinchartl> * Morimoto-san
10:16 < pinchartl> Since last meeting:
10:16 < pinchartl> - Fixed sound clock issue for v5.1-rcX
10:16 < pinchartl> - Reviewed E3 sound support patch
10:16 < pinchartl> - Sound-related Q/A with customer
10:16 < pinchartl> - Fixed a sound DT regression in v5.1
10:16 < pinchartl> Until next meeting:
10:16 < pinchartl> - Continue with ALSA SoC work
10:16 < pinchartl> Issues and Blockers: None
10:16 < pinchartl> morimoto: you also reported by e-mail about creating a "pseudo", but I'm not sure to understand what you meant
10:17 < pinchartl> could you please elaborate ?
10:17 < morimoto> Ahh
10:17 < morimoto> The perfect is like this
10:17 < morimoto> "Linux" + "Intel guys work" + "my work"
10:18 < morimoto> but "Intel guys work" is based on Intel guys
10:18 < morimoto> So, I created pseudo code, like this
10:18 < morimoto> "Linux" + "pseudo Intel code" + "my work"
10:18 < morimoto> Is it clear for you ?
10:19 < pinchartl> yes, thank you
10:19 < pinchartl> do you plan to upstream the pseudo Intel code ? :-)
10:19 < morimoto> Good question :)
10:19 < morimoto> but no such plan ;)
10:20 < morimoto> Sorry for my unclear mail
10:20 < pinchartl> seriously speaking, if Intel stalls forever, and that blocks your work, after pinging them several times you could take over that work if needed
10:21 < morimoto> Yeah, I tried it few weeks ago
10:21 < morimoto> And agreed. thank you for your advice
10:21 < pinchartl> you're welcome. let me know if I can help
10:21 < pinchartl> * Niklas
10:21 < pinchartl> Since last meeting:
10:21 < pinchartl> - [PATCH v2 0/2] rcar-csi2: Use standby mode instead of resetting
10:21 < pinchartl> - [PATCH v2] rcar-csi2: Propagate the FLD signal for NTSC and PAL
10:21 < pinchartl> - [PATCH v2 0/3] rcar-csi2: Update start procedures to latest revision of datasheet
10:21 < pinchartl> - [PATCH] arm64: dts: renesas: r8a774c0: Remove invalid compatible value for CSI40
10:21 < pinchartl> - [PATCH v3 0/2] rcar-csi2: Use standby mode instead of resetting
10:21 < pinchartl> - [PATCH v3] rcar-csi2: Propagate the FLD signal for NTSC and PAL
10:21 < pinchartl> - [PATCH v3 0/3] rcar-csi2: Update start procedures to latest revision of datasheet
10:21 < pinchartl> Until next meeting:
10:21 < pinchartl> - Try to clean up the VIN crop and compose code
10:21 < pinchartl> This is needed to merge UDS and PM support.
10:21 < pinchartl> Issues and blockers: None
10:21 < pinchartl> neg: any comment ?
10:22 < neg> No additional comment
10:22 < pinchartl> thank you
10:22 < pinchartl> * Ulrich
10:22 < pinchartl> Since last meeting: None
10:22 < pinchartl> Until next meeting: None
10:22 < pinchartl> Issues and Blockers: None
10:22 < pinchartl> uli___: no MM work planned so far, is that correct ?
10:23 < uli___> yes
10:23 < pinchartl> thank you
10:24 < pinchartl> Topic 2. Discussions
10:24 < pinchartl> I'll start with
10:24 < pinchartl> - Face-to-face meeting in Japan
10:24 < pinchartl> as you probably all know, I met with the BSP team in Tokyo on March the 26th
10:25 < pinchartl> I explained the multimedia development plan and strategy, and expanded that to also touch areas outside of the MM group
10:26 < pinchartl> the feedback I have received during the meeting was limited, and mostly consisted of BSP requests for MM development unrelated to the plan that was presented
10:26 < pinchartl> *however*
10:26 < pinchartl> there were several interesting points worth noting
10:27 < pinchartl> one, even though I tried to include more text than usual on my slides to make it easier to follow, there was still probably a language barrier that made communication a bit hard
10:27 < pinchartl> I know I speak too fast :-S
10:27 < pinchartl> so the BSP team has received the slides, and Morimoto-san said they would provide feedback on the plan
10:27 < pinchartl> two, the budget situation is very unclear, with all options being on the table
10:28 < pinchartl> in some discussions the future looked gloomy, but in others the BSP team talked about Gen4
10:28 < pinchartl> we don't know what will happen next year (or even after Q3) but hoping is still permitted
10:29 < pinchartl> three, on the multimedia side, there was a good match between key areas we have identified and one request from the BSP team related to VSP performance improvement
10:29 < pinchartl> that match is the request API, which I plan to propose as one of the core work items for MM in the next two quarters
10:30 < pinchartl> to finalize the plan proposal I will need the feedback from the BSP team I mentioned above
10:30 < pinchartl> four, I explained during the meeting that the thin slicing of budget in small additional tasks made it difficult to tackle bigger development tasks
10:30 < pinchartl> and asked if we could solve that somehow
10:30 < pinchartl> the request seemed to be well received, and Morimoto-san said he would try to help with that
10:31 < pinchartl> we thus need to make a proposal
10:31 < pinchartl> this depends on the finalization of the development plan
10:31 < pinchartl> that's a coarse summary of the discussions
10:31 < pinchartl> any question or comment ?
10:31 < pinchartl> morimoto: anything you would like to add, anything I missed ?
10:32 < morimoto> please wait few min
10:32 < neg> morimoto: pinchartl: Thanks to you both for having this meeting and sharing the results of it
10:33 < pinchartl> morimoto: sure
10:33 < pinchartl> neg: you're welcome
10:33 < pinchartl> in the meantime, any other question or comment ?
10:33 < pinchartl> or any other discussion point for today (I want to discuss additional tasks for Q2)
10:33 < neg> pinchartl: I know the burden of traveling to Japan for it must have been gruesome ;-)
10:34 < wsa> I want to point out (again) that M/M is (rightfully) different from IO, and probably core
10:34 < morimoto> About one, sorry for our English skill
10:34 < pinchartl> neg: you know I will always donate my person for the good cause (I hope this comes out correctly in English)
10:34 < wsa> the thin slicing wasn't too bad for IO
10:34 < pinchartl> morimoto: no need to be sorry. the issue wasn't caused by your bad English skills, it was caused by my lack of Japanese skills :-)
10:34 < wsa> but I understand that it was difficult for M/M
10:35 < pinchartl> wsa: I agree, the problem differs in the three groups, and also depends on the tasks at hand
10:35 < wsa> I'm just saying a "one process for all" will always face this diversity
10:36 < morimoto> About three, thank you for your help
10:36 < neg> For the limitations we identified in MM I think it's encouraging that talk of how to handle that in a new format of additional contracts have started
10:36 < morimoto> About four, it depends with two
10:37 < morimoto> But I want to solve the issue
10:37 < morimoto> It needs Jinso-Renesas-Magnus-SoW connection
10:38 < morimoto> It is my (our) home-work
10:39 < pinchartl> my opinion is that the SoWs and additional tasks are related to the development plan. I would thus like to finalize the plan based on the feedback from the BSP team, and then discuss together how we can create SoWs that keep the concept of additional tasks, but make that fit with larger development
10:39 < pinchartl> do you know when we could receive feedback on the proposals ?
10:40 < morimoto> from BSP team ?
10:40 < pinchartl> yes
10:40 < morimoto> I'm waiting it. I will send ping to them
10:41 < pinchartl> thank you
10:42 < pinchartl> any other question or comment ?
10:43 < neg> Is it too early to start to plan Renesas days around OSSJ ?
10:43 < pinchartl> I'd say the earlier the better
10:44 < pinchartl> the first question is then, will we have a periperi meeting in Japan ?
10:44 < pinchartl> (around OSSJ-
10:44 < pinchartl> )
10:45 < pinchartl> morimoto: any plan on Renesas side ?
10:45 < morimoto> No plan so far
10:46 < pinchartl> morimoto: do you think we should make a plan ? :-)
10:46 < wsa> I am not going to OSSJ this year, too many schedule conflicts :(
10:46 < pinchartl> wsa: :-(
10:46 < morimoto> I'm plannng so far for OSSJ is Chanko which is requested from wsa
10:46 < pinchartl> how about everybody else, who plans to go, who will not go, and who is still undecided ?
10:46 < morimoto> wsa: Grrr you don't this year
10:47 < pinchartl> I know Kieran will likely not be able to join, due to having a wedding on both sides of the conference
10:47 < wsa> morimoto: didn't i tell you?
10:47 < uli___> i intend to go
10:47 < pinchartl> (getting married once is already crazy, having two weddings is even worse if you ask me :-))
10:47 < pinchartl> uli___: that's the right decision :-)
10:47 < kbingham> Correct. OSSJ is highly unlikekly for me I'm afraid.
10:47 < morimoto> wsa: did you ? I don't remember...
10:47 < wsa> i thought we discussed OSSJ attendance somewhen already on IRC
10:48 < pinchartl> geertu: how about you ?
10:48 < neg> kbingham: will the divorce papers clear in time for the second wedding?
10:48 < pinchartl> horms: same question ?
10:48 < wsa> morimoto: I'm sad myself :'-(
10:49 < kbingham> neg, They'll be fine.
10:49 < horms> If the question is about OSSJ then the answer is that I currently have no plans to attend
10:49 < morimoto> wsa: I will miss you, so much...
10:49 < pinchartl> horms: yes, that was the question. would you make plans to attend if needed, or is that unlikely ?
10:50 < wsa> maybe we should do this by email, but what about you guys attending Plumbers (Lisboa) and/or Embedded/Kernel-Recipes (Paris) in September
10:50 < wsa> ?
10:50 < wsa> morimoto: will we meet in Lyon at ELCE?
10:50 < pinchartl> wsa: LPC or ELCE would be a good idea too
10:50 < morimoto> Maybe I can't joint to ELCE this year
10:51 < morimoto> s/joint/join/
10:51 < pinchartl> morimoto: I suppose it depends on the budget situation, and we will only know about it later ?
10:52 < pinchartl> geertu: ping ?
10:52 < horms> pinchartl: if its important I can make a plan. but other plans would work better for me, f.e. I do plan to attend LPC and ELCE would take me about as long to drive to as it would to fly to OSSJ
10:53 < pinchartl> horms: ok
10:53 < pinchartl> so a whole periperi meeting seems more likely at LPC or ELCE time than OSSJ time at the moment
10:53 < pinchartl> I have submitted a talk proposal for OSSJ so I will likely go
10:54 < pinchartl> maybe we'll have a MM meeting instead of a global meeting then
10:54 < geertu> pinchartl: I can go to OSSJ
10:55 < pinchartl> geertu: nice :-)
10:55 < geertu> I will be at Embedded-Recipes (invited speaker)
10:55 < wsa> same here for Embedded Recipes
10:55 < geertu> It's been 3 years since I've been to JP :-(
10:55 < wsa> not sure about Plumbers yet
10:55 < geertu> wsa: Marex did a good job ;-)
10:55 < pinchartl> what will you speak about at RC ?
10:55 < wsa> yes :D
10:55 < pinchartl> s/RC/ER/
10:56 < geertu> pinchartl: No topic set so far
10:56 < wsa> similar here, a rough idea was to speak about my subsystem (new things, workflow...)
10:56  * geertu considers a talk about the Japanese cherry tree in his garden
10:58 < pinchartl> :-)
10:58 < geertu> Probably I should install a camra to take daily Sakura pictures
10:58 < wsa> morimoto: you are not coming to Lyon? Well, looks like I need to find another excuse than OSSJ to come to Japan then :)
10:58 < geertu> And I plan to attend ELCE, as usual
10:59 < geertu> (until LF has exploded by then)
10:59 < geertu> s/until/unless/
11:00 < pinchartl> any plan to make LF explode ?
11:00 < wsa> Yeah, I plan for ELCE, too
11:01 < morimoto> wsa: yeah, I can't this year. so sorry
11:01 < geertu> http://techrights.org/2019/03/30/what-happened-lf/
11:02 < pinchartl> geertu: interesting, I had missed that
11:02 < pinchartl> anyway, the conclusion for now is
11:02 < pinchartl> likely no official global meeting around OSSJ
11:02 < pinchartl> perhaps a multimedia meeting
11:03 < pinchartl> and perhaps a global meeting around LPC or ELCE (but that is likely conditioned by budget)
11:03 < pinchartl> next discussion topic for the MM meeting
11:03 < pinchartl> additional tasks for Q2
11:03 < pinchartl> as discussed before, the plan is to makes those tasks fit in the global MM development plan
11:04 < pinchartl> I would like to already move forward with tasks related to the request API
11:04 < pinchartl> for other tasks, I would like to first receive feedback from the BSP team on the plan
11:04 < pinchartl> neg: if I understand correctly, you have all your additional task time allocated already for Q2, right ?
11:06 < marex-cloud> morimoto: I'll likely be at OSSJ :)
11:06 < geertu> marex-cloud: Critical mass reached!
11:07 < marex-cloud> geertu: heh
11:07 < neg> pinchartl: yes Q2 already allocated
11:07 < marex-cloud> geertu: I'll also be at ER most likely, I seem to be roped into a special role
11:07 < pinchartl> neg: thanks
11:08 < marex-cloud> geertu: godfather was the name I think
11:08 < pinchartl> so I'll work on a proposal for the request API already, and wait for feedback for the rest
11:08 < pinchartl> any other dicussion topic for today ?
11:09 < neg> not from me, thanks
11:09 < morimoto> marex-cloud: nice to know :)
11:09 < marex-cloud> geertu: what about doing a trip to Toyama around OSSJ, eat great food etc?
11:09 < pinchartl> I then propose adjourning this meeting. does anyone second ?
11:10 < neg> second
11:10 < morimoto> 3rd
11:10 < marex-cloud> morimoto: maybe I should consider relocation ^_^'
11:10 < morimoto> marex-cloud: sorry for what ?
11:10 < pinchartl> meeting adjourned. thank you all for attending