path: root/wiki/Chat_log/20190221-mm-chatlog

Multimedia-chat-meeting-2019-02-21

10:17 < pinchartl> welcome to the multimedia meeting
10:18 < pinchartl> Topic 1. Status Check for the Multimedia Tasks
10:18 < pinchartl> * Jacopo
10:18 < pinchartl> Since last meeting:
10:18 < pinchartl> - Take over the V4L2 multiplexed streams patch series
10:18 < pinchartl> Started addressing review comments and adding documentation. Plan to
10:18 < pinchartl> submit next week and implement data lane negotiation on top of that.
10:18 < pinchartl> - Investigated adv748x CSI-2 data lane configuration on AFE->TXA
10:18 < pinchartl> - Reviewed VIN and miscellaneous V4L2 patches
10:18 < pinchartl> - Attended FOSDEM and periBe meetings
10:18 < pinchartl> Until next meeting:
10:18 < pinchartl> - Finalize the next version of the V4L2 multiplexed streams patch series
10:18 < pinchartl> Issues and blockers: None
10:18 < pinchartl> jmondi: any comment ?
10:19 < kbingham> jmondi, If you publish an updated/rebased mux branch - please let me know so that I can rebase my gmsl/for-renesas-drivers on top of it.
10:19 < pinchartl> we seem to be missing Jacopo
10:19 < pinchartl> * Kieran
10:19 < pinchartl> Since last meeting:
10:19 < pinchartl> - PeriPeri meetings in Brussels
10:19 < pinchartl> - FOSDEM
10:19 < pinchartl> - Hans' VSP1 smatch testing
10:19 < pinchartl> - Various reviews
10:19 < pinchartl> - VSP partition algorithm phase investigations
10:19 < pinchartl> Until next meeting:
10:19 < pinchartl> - Focus on VSP partition algorithm phase until complete
10:19 < pinchartl> - On holidays until the end of the week
10:19 < pinchartl> Issues and blockers:
10:19 < pinchartl> - VSP partition algorithm phase is difficult to understand
10:19 < pinchartl> kbingham: any comment ?
10:20 < kbingham> No.
10:20 < pinchartl> thank you
10:20 < pinchartl> * Laurent
10:20 < pinchartl> Since last meeting:
10:20 < pinchartl> - FOSDEM & multimedia meeting
10:20 < pinchartl> - DU writeback support for Gen3
10:20 < pinchartl> A working patch series has been posted, but the upstream DRM community
10:20 < pinchartl> requested the DU driver to use the DRM/KMS writeback connector API
10:20 < pinchartl> instead of V4L2 for writeback capture. A new version is under
10:20 < pinchartl> development.
10:20 < pinchartl> - Upstreamed VSP test suite and related yavta patches
10:20 < pinchartl> - Upstreamed D3/R3 RGB output
10:20 < pinchartl> Until next meeting:
10:20 < pinchartl> - DU writeback support
10:20 < pinchartl> - Finalize additional tasks for 2019 Q1
10:20 < pinchartl> Issues and blockers: None
10:20 < pinchartl> any question ?
10:20 < morimoto> Thank you for Brussels souvenir
10:21 < morimoto> for all M/M member
10:21 < pinchartl> you're welcome :-)
10:21 < jmondi> I'm here sorry
10:21 < jmondi> got distracted :) no comments from here
10:21 < pinchartl> it was a bit more Finnish than Belgian, but we signed it all in Brussels :-)
10:21 < pinchartl> jmondi: thank you
10:21 < pinchartl> * Morimoto-san
10:21 < pinchartl> Since last meeting:
10:21 < pinchartl> - ALSA SoC v5.0 bugfix for issues reported by users
10:21 < pinchartl> Until next meeting:
10:21 < pinchartl> - ALSA SoC needs to be updated for modern device
10:21 < pinchartl> Issues and Blockers:
10:21 < pinchartl> - ALSA SoC work depends on a developer from Intel
10:21 < pinchartl> morimoto: any comment ?
10:21 < morimoto> No, thanks
10:22 < pinchartl> thank you
10:22 < pinchartl> who is that Intel person ? and is there something we can help to make him help you ?
10:23 < morimoto> He is Pierre-Louis Bossart
10:23 < morimoto> He is working for other Intel work.
10:23 < morimoto> And mine is depend to it
10:24 < pinchartl> is his work progressing ? that is, is it "just" a matter of waiting for him to complete his work, or is it stalled for some reason ?
10:24 < morimoto> I think he is working very hard.
10:25 < morimoto> And I need some prepare work for my task
10:25 < morimoto> so, both are under hard work
10:25 < morimoto> :)
10:25 < pinchartl> ok :-)
10:26 < pinchartl> * Niklas
10:26 < pinchartl> Since last meeting:
10:26 < pinchartl> - [PATCH] rcar-vin: Fix lockdep warning at stream on
10:26 < pinchartl> - [PATCH] rcar-csi2: Use standby mode instead of resetting
10:26 < pinchartl> - [PATCH] rcar-csi2: Allow configuring of video standard
10:26 < pinchartl> - [PATCH 0/2] arm64: dts: r8a77990-ebisu: small fixes for VIN
10:26 < pinchartl> - [PATCH 0/3] rcar-csi2: Update start procedures to latest revision of datasheet
10:26 < pinchartl> - [PATCH] rcar-csi2: restart CSI-2 link if error is detected
10:26 < pinchartl> - Attended face-to-face periperi Multimedia meeting
10:26 < pinchartl> Until next meeting:
10:26 < pinchartl> - Try to clean up the VIN crop and compose code
10:26 < pinchartl> This is needed to ease merging of UDS and PM support.
10:26 < pinchartl> Issues and blockers:
10:26 < pinchartl> - Unsure how to upstream updates for periupport bsp392
10:26 < pinchartl> Are we using periject or periupport to track upporting now?
10:26 < pinchartl> neg: any comment ?
10:27 < neg> No comment, thanks
10:27 < pinchartl> do you want to discuss how to handle upporting after the status update ?
10:28 < neg> Yes please
10:28 < pinchartl> ok
10:28 < pinchartl> thanks
10:28 < pinchartl> * Ulrich
10:28 < pinchartl> Since last meeting:
10:28 < pinchartl> - Reviewed "rcar-csi2: Update start procedures to latest revision of
10:28 < pinchartl>   datasheet" series
10:28 < pinchartl> Until next meeting: None
10:28 < pinchartl> Issues and Blockers: None
10:28 < pinchartl> uli___: any comment ?
10:28 < uli___> nope
10:29 < pinchartl> thank you
10:29 < pinchartl> Topic 2. Discussions
10:29 < pinchartl> - BSP Upporting
10:29 < pinchartl> neg: please go ahead :-)
10:30 < neg> Thanks, I'm only unsure if we track upport progress in periupport or periject
10:31 < neg> In the past I sent patches to group leaders to periupport but after preparing such a patch recently I became unsure if we are 'live' with periject for this yet or not
10:31 < pinchartl> does anyone have an answer to that question ? wsa maybe ?
10:31 < kbingham> neg, Do we have multimedia tasks in periject yet?
10:34 < pinchartl> silence...
10:34 < Marex> morimoto: I sent you an IRC PM, did you receive it ?
10:34 < pinchartl> have we lost neg ?
10:34 < pinchartl> wsa: ping ?
10:35 < morimoto> Marex: sorry what is "PM" ?
10:35 < kbingham> Aha - we have a viewer starting :) (thanks morimoto-san)
10:35 < neg> kbingham: no, but there are upport tasks for IO, d5c115890a419f77 ("projects: add upport tasks from bsp392 for IO")
10:35 < Marex> morimoto: private message
10:35 < morimoto> Marex: I think no
10:35 < Marex> morimoto: OK, I can send you an email later, it's not important
10:35 < morimoto> kbingham: I'm creating HTML version now :)
10:36 < pinchartl> neg: Wolfram seems gone already, I fear we'll have to discuss it on the list
10:36 < kbingham> From what I can see - wsa has created IO tasks only.
10:36 < morimoto> Marex: OK
10:36 < wsa> what was the question?
10:36 < pinchartl> wsa: 10:31 < neg> In the past I sent patches to group leaders to periupport but after preparing such a patch recently I became unsure if we are 'live' with periject for this yet or not
10:37 < kbingham> morimoto, "./ject --oneline" Nice :)
10:37 < wsa> yes, sure I have created IO tasks only. Conversions needs manual updates and I can't do that for other groups
10:37 < wsa> What did you expect here?
10:38 < pinchartl> wsa: I certainly didn't expect you to handle the multimedia tasks :-)
10:38 < wsa> So, for IO, periject has gone live, but for me, we are still in beta-testing phase
10:38 < pinchartl> the question is whether we are live with periject
10:38 < wsa> pinchartl: thanks :)
10:38 < pinchartl> ok
10:38  * kbingham has a Hugo returning ... so I must leave.
10:38 < wsa> to answer neg's question: during beta-test, both is fine for me
10:39 < pinchartl> so you would say it can be a per-group decision at this time ?
10:39 < pinchartl> ok
10:39 < pinchartl> neg: what's your preference ? do you want to beta-test periject for multimedia ? :-)
10:39 < wsa> I will ensure both are in sync, and we will find out what is best
10:39 < neg> I think the confusion answers my question for MM, I will send out the patch to periupport :-)
10:39 < wsa> pinchartl: I wished everyone would go live with periject. Dunno why this has not happened yet.
10:40 < kbingham> wsa, lack of understanding I expect.
10:40 < kbingham> I think we should move to it asap.
10:41 < wsa> Okay, in case you just need someone to tell you to do it...
10:41 < wsa> Do it!
10:41 < wsa> :D
10:41 < pinchartl> neg: I agree with Wolfram, I think it would be nice if we all moved to it
10:41 < kbingham> wsa, Excellent ^ you just did :)
10:41 < pinchartl> so I'd favour using periject instead of sending patches for periupport
10:41  * kbingham really has to leave now
10:43 < Marex> morimoto: I was just curious whether it's a great idea to drop by at the end of march to see the sakura blooms and whether they're beautiful in Tokyo :)
10:44 < pinchartl> neg: ?
10:44 < neg> I'm OK with periject but keeping the two projects in sync if manual steps is involved scares me
10:45 < morimoto> March: According to web, 2019 sakura in Tokyo is from 23th March
10:45 < Marex> morimoto: jupp
10:45 < pinchartl> neg: let's go for periject only then
10:45 < neg> Sorry got lost in the periject code, it seems periject does not yet have the same feature set as periject when it comes to track upport data. Looking at wsa commits 'normal tasks are created to group sets of upport commits
10:45 < morimoto> Thank you periupport, welcome periject
10:48 < neg> So to switch to periject all MM related patches from bsp392 needs to be extracted and grouped for periject, which is fine but a task someone needs to do
10:48 < morimoto> Marex: This is Japanese page, but for 2019 sakura
10:48 < morimoto> https://jp.zekkeijapan.com/article/index/493/
10:48 < Marex> morimoto: I need to practice anyway !
10:48 < pinchartl> neg: Wolfram developed a script to classify commits. we can then manually edit the tasks
10:48 < Marex> morimoto: I am slowly starting to be able to make sense from emails between you and Hosoya-san :)
10:48 < pinchartl> neg: I can help you with that
10:49 < morimoto> Marex: Thanks. But no stress
10:49 < pinchartl> neg: would you be ok working on it with me ?
10:50 < Marex> morimoto: thank you for translating them for me :)
10:50 < neg> pinchartl: absolutely
10:50 < pinchartl> thank you
10:50 < pinchartl> let's do it then
10:50 < pinchartl> any other discussion topic ?
10:51 < neg> not from me
10:51 < wsa> pinchartl: note that the unique-key topic is still open for periject
10:51 < Marex> morimoto: btw there's an updated forecast from Feb. 7th, https://www.jnto.go.jp/sakura/eng/index.php , I think there should be new one on 21st too
10:51 < jmondi> not from here
10:51 < morimoto> Not from me. Just information, I will enjoy snowboard from tomorrow ;P
10:51 < pinchartl> wsa: I know. I'll see if I can have a look at that
10:52 < wsa> cool
10:52 < pinchartl> morimoto: nice ! :-)
10:52 < jmondi> morimoto: now we're jealous
10:52 < wsa> morimoto: have fun!
10:52 < pinchartl> Topic 3. Additional Tasks for 2019 Q1
10:52 < pinchartl> The following additional tasks will be submitted to Renesas today:
10:52 < pinchartl> - DU External Pixel Clock Routing Support
10:52  * jmondi learns there is a calendar for Japanese cherry blossom season
10:52 < pinchartl> - DU LVDS Dual Link Support Prototype
10:52 < morimoto> pinchartl: jmondi: wsa: thanks !
10:52 < pinchartl> if anyone wants another AT for Q1, please chime in today
10:53 < wsa> jmondi: it is part of the weather forecast in Japanese TV :)
10:53 < pinchartl> that's it for today
10:53 < pinchartl> next meeting two weeks from now on March the 7th ?
10:53 < wsa> ack
10:53 < neg> works for me
10:54 < pinchartl> I propose adjourning this meeting. does anyone second ?
10:54 < neg> second
10:54 < morimoto> 2nd
10:54 < jmondi> yup
10:55 < pinchartl> meeting adjourned. thank you all for attending, and have a nice day