Multimedia-chat-meeting-2018-10-18

11:02 < pinchartl> welcome to the multimedia meeting
11:02 < pinchartl> Topic 1. Status Check for the Multimedia Tasks
11:02 < pinchartl> * Jacopo
11:02 < pinchartl> Since last meeting:
11:02 < pinchartl> - Mostly review (v4l2-mux, gmsl v3, some other media related patches)
11:02 < pinchartl> - Slides and talk preparation for ELC-E
11:02 < pinchartl> - Some patches to periupport
11:02 < pinchartl> Until next meeting:
11:02 < pinchartl> - ELC-E
11:02 < pinchartl> - Get an E3 from Laurent and start looking into the CSI-2 issue
11:02 < pinchartl> - Resume adv748x work (dynamic channel configuration)
11:02 < pinchartl> Issues and Blockers: None
11:02 < pinchartl> jmondi: any comment ?
11:03 < jmondi> not really
11:03 < pinchartl> thanks
11:03 < pinchartl> * Kieran
11:03 < pinchartl> Since last meeting:
11:03 < pinchartl> - GMSL rebase for renesas-drivers (conflicts with async/fwnode/csi2 changes)
11:03 < pinchartl> - VIN circular locking dependency report
11:03 < pinchartl> - Working on partition algorithm phases and overlaps
11:03 < pinchartl> Until next meeting:
11:03 < pinchartl> - ELCE
11:03 < pinchartl> - Aim to get pa-phase work out
11:03 < pinchartl> - Look at KUnit for testing! Looks interesting (to me?)
11:03 < pinchartl> Issues and blockers: None
11:03 < pinchartl> kbingham: any comment ?
11:03 < kbingham> Nope :)
11:03 < pinchartl> thanks
11:03 < pinchartl> * Laurent
11:03 < pinchartl> Since last meeting:
11:03 < pinchartl> - More patch review
11:03 < pinchartl> - Submitted multimedia additional tasks for Q4
11:03 < pinchartl> - Miscellaneous DU fixes
11:03 < pinchartl> - BSP upport (periupport updates)
11:03 < pinchartl> - FCNL reserved memory areas discussions (see Marek's ATF work)
11:03 < pinchartl> Until next meeting:
11:03 < pinchartl> - More patch review
11:03 < pinchartl> - Finalize multimedia additional tasks for Q4
11:03 < pinchartl> - Attend ELC-E, Linux media summit and peripericon
11:03 < pinchartl> - Get GMSL patches merged
11:03 < pinchartl> Issues and blockers: None
11:03 < pinchartl> any question ?
11:04 < pinchartl> ah, and I forgot to mention that I've reviewed the DS90x9xx patches (FPD-Link III serializers and deserializers)
11:05 < kbingham> Well yes, I could have put some FPD-Link III in my "since last meeting" section too :)
11:05 < pinchartl> I'll add that
11:05 < pinchartl> * Morimoto-san
11:05 < pinchartl> Since last meeting:
11:05 < pinchartl> - Continued work on TDM sound on StarterKit + KingFisher
11:05 < pinchartl>   - Solved codec driver issue on cold-boot, it needed clock switching.
11:05 < pinchartl>   - Solved codec kctrl settings issue, few register needed clocks.
11:05 < pinchartl>   - Solved clock switching, used gpio-mux-clock.
11:05 < pinchartl>   - Solved TDM issues, SSI driver needed few bugfix patches.
11:05 < pinchartl> All patches have been posted to the ALSA mailing list.
11:05 < pinchartl> Until next meeting:
11:05 < pinchartl> - Continue work on TDM sound on StarterKit + KingFisher
11:05 < pinchartl> Expanded sound card and BUSIF detail control are needed, will work on them 
11:05 < pinchartl> next.
11:05 < pinchartl> morimoto: any comment ?
11:05 < morimoto> No comment, but I would say I'm looking forward to see you in ELCE :)
11:06 < pinchartl> :-)
11:06 < pinchartl> I think we all are
11:06 < pinchartl> * Niklas
11:06 < pinchartl> Since last meeting:
11:06 < pinchartl> - [PATCH v2 0/3] rcar-vin: add support for UDS (Up Down Scaler)
11:06 < pinchartl> - [PATCH v2 0/5] i2c: adv748x: add support for CSI-2 TXA to work in 1-, 2- and 
11:06 < pinchartl> 4-lane mode
11:06 < pinchartl> - [PATCH] v4l2-ioctl: fix CROPCAP type handling
11:06 < pinchartl> - Tested CEC patches for Koelsch and it now works
11:06 < pinchartl> Until next meeting:
11:06 < pinchartl> - Post v3 of adv748x 1-, 2- and 4-lane mode
11:06 < pinchartl> - Attend multimedia summit during ELCE
11:06 < pinchartl> Issues and blockers: None
11:06 < pinchartl> neg isn't here
11:06 < pinchartl> * Simon
11:06 < pinchartl> Since last meeting:
11:06 < pinchartl> - E3 Audio now working, patches posted
11:06 < pinchartl> Until next meeting:
11:06 < pinchartl> - Follow up on above as necessary
11:06 < pinchartl> Issues and blockers: None
11:06 < pinchartl> horms: any comment ?
11:06 < neg> I'm back just in time it seems :-) No comment
11:07 < pinchartl> neg: welcome back !
11:07 < neg> thanks, sorry for the conflict
11:08 < horms> pinchartl: none, I had issues with E3 Audio. Morimoto's guidance helped me fix them. No problems at this time
11:08 < horms> Let me know if you want any upporting done :)
11:08 < morimoto> horms: good to know :)
11:08 < pinchartl> sure :-)
11:09 < pinchartl> I'm marking patches as 'MM upstreaming candidates' in periupport, feel free to pick them if you want
11:09 < pinchartl> there's nothing particularly urgent so far
11:09 < pinchartl> the pinctrl and DT integration commits are good candidates for non-urgent upporting
11:11 < pinchartl> Ulrich isn't here, did he say he would miss this meeting ? the last I heard was "prepare for stay in the Philippines until Dec 10" two weeks ago, but I don't know if that means holidays or working under the sun
11:11 < wsa> pinchartl: same question here
11:11 < pinchartl> wsa: I thus assume you don't know the answer :-)
11:11 < pinchartl> geertu: damm: any info ?
11:12 < geertu> pinchartl: I don't know.
11:12 < pinchartl> ok
11:13 < geertu> His "tips-and-tricks to use free Wifi effectively" may not be applicable to the Philippines ;-)
11:13 < pinchartl> :-D
11:13 < pinchartl> on the topic of periupport
11:14 < pinchartl> morimoto: in the bsp370 ticket file, you have marked lots of commits with a reference to previous BSP releases
11:14 < pinchartl> if I update a commit in the v4.14 file, should I update the corresponding commit in bsp370, or leave the reference ?
11:15 < morimoto> uhm
11:15 < morimoto> Basically there are no conflict commits between v4.14 vs bsp370
11:15 < morimoto> But, you had it ?
11:16 < pinchartl> it's not a matter of conflicts
11:16 < pinchartl> for instance
11:16 < morimoto> sorry, not conflicts, duplicate
11:16 < pinchartl> commit 543637cb084774608dc67144be0ac0ae9e534350
11:16 < pinchartl> is
11:16 < pinchartl> in bsp370
11:16 < pinchartl> N,543637cb084774608dc67144be0ac0ae9e534350|requested upport with f7cac36f6d7862f93a12cfb8d4d0d9b47f132179 of BSPv3.6.0
11:17 < pinchartl> what should I do with that ?
11:17 < pinchartl> not touch it because it's marked N ?
11:17 < morimoto> Ahh, please ignore "N" commit.
11:17 < morimoto> Mainly, we need latest ticket only. so, bsp370
11:18 < morimoto> is important to Renesas
11:19 < pinchartl> hmmmm...
11:19 < wsa> Yet, 'N' is all the Ebisu upporting for example (enablement of SCIF, I2C, for example)
11:19 < wsa> we surely want that, or?
11:19 < morimoto> on bsp370 ?
11:20 < morimoto> pinchartl: sorry, what is wrong ?
11:20 < pinchartl> another example
11:20 < pinchartl> in bsp370
11:20 < pinchartl> N,068d08088b263a2c037656ea9668f8bb2be3d046|requested upport with 6ea68fc0ce880bdfa511b45b8e7ace42303c71e5 of BSPv3.6.0
11:21 < pinchartl> and in v4.14
11:21 < pinchartl> M,6ea68fc0ce880bdfa511b45b8e7ace42303c71e5
11:21 < pinchartl> have you marked it as N in bsp370 because you expect it to be upported from v4.14 ?
11:22 < morimoto> Oops, I misunderstood...
11:23 < morimoto> BSP team is thinking that they avoid duplicate request
11:23 < morimoto> It seems
11:24 < morimoto> We need to avoid N, and care about M/H on both v4.14 and bsp370
11:24 < morimoto> Renesas inside doesn't matter about "N", but counting how many patch are upported
11:24 < morimoto> (= for L/M/H)
11:25 < pinchartl> ok
11:25 < horms> Ok, so for KPI N is irrelevant
11:25 < horms> I asked this a bit earlier, but is there a plan to produce bsp380 ?
11:25 < pinchartl> wouldn't it have been better to mark the commit as N in v4.14 and as M bsp370 ?
11:25 < pinchartl> that way the latest BSP ticket file would contain most of the work to be done
11:26 < morimoto> pinchartl: it is good idea. thanks
11:26 < pinchartl> similarly to when you post a v2 of a patch, v1 is marked as superseded and everybody forgets about it
11:27 < pinchartl> so how should we handle this ? does anyone have a magic script to reconcile everything ? :-)
11:28 < morimoto> I can't use magic :(
11:28 < horms> is it against company policy?
11:29 < morimoto> horms: is it question to me ?
11:29 < horms> morimoto: sorry, it was a joke about magic.
11:29 < pinchartl> I'll try to write a script to handle this
11:30 < pinchartl> morimoto: thanks for the feedback
11:30 < morimoto> horms: yeah, it is joke my side too :)
11:30 < pinchartl> Topic 2. Discussions
11:30 < horms> morimoto:)
11:30 < pinchartl> Marex: you've requested a discussion about FCNL
11:30 < pinchartl> we've already discussed the topic, is there something you would like to add ?
11:32 < morimoto> pinchartl: Marex: I think you had question about it to BSP team, but 1) they don't know detail, because it is used by 3rd party 2) related guy already go back to home today. So please send me question mail, I can forward it to BSP/3rd party, and feedback to you.
11:34 < wsa> horms: what is KPI?
11:34 < pinchartl> while waiting for Marex, does anyone have any other topic they would like to discuss ?
11:34 < pinchartl> wsa: Key Performance Indicator
11:34 < Marex> pinchartl: let
11:34 < wsa> thanks
11:35 < morimoto> wsa: KPI = key performance indicator
11:35 < Marex> pinchartl: let's postpone FCNL until we have DT support in ATF ? :)
11:35 < Marex> pinchartl: and until the FCNL is sorted out in Linux too ?
11:35 < neg> I would only like to ask if anyone wish me to prepare or bring something specail to facilitate MM work during ELCE. As we talked about E3 testing maybe there is something else?
11:35 < Marex> morimoto: would Takuya Sakata-san be willing to discuss ATF with me ? :)
11:36 < morimoto> hmm.. I don't know him...
11:36 < morimoto> discuss by what ? mail ?
11:36 < Marex> morimoto: jupp, email
11:36 < Marex> morimoto: I'd like to send him some ATF patches
11:36 < Marex> morimoto: OK, I'll just send him the patches :)
11:37 < wsa> pinchartl: I think I can brush up my 'transfer upporting info from ticket x to ticket y' script to transfer the old prio if the new one is 'N'
11:37 < morimoto> Marex: OK, please do
11:37 < pinchartl> Marex: but please keep FCNL support in your ATF patch series
11:38 < Marex> pinchartl: but the bindings are not fleshed out yet and I don't want them to become ABI
11:39 < pinchartl> wsa: that would be nice, as I was thinking about writing such a script :-) my idea is roughly if (new prio == N and comment == reference to old commit) { copy old commit prio and comment to new commit; set old prio to N and comment to reference new commit }
11:39 < pinchartl> wsa: do you think you could do that ?
11:39 < pinchartl> it would be useful to commit the script to the repo too
11:40 < pinchartl> Marex: you don't have to upstream it yet, but I'd like the patches to be included in the series, in order to make sure that the proposal will work
11:40 < pinchartl> would that be OK with you ?
11:40 < Marex> I do keep the patch, it's not like I threw it away
11:40 < wsa> pinchartl: I'll try
11:41 < wsa> and let you all know :)
11:41 < pinchartl> Marex: thanks :-)
11:41 < pinchartl> wsa: thanks
11:41  * Marex wonders if we can generate FDT at compile time ... :-)
11:41 < Marex> I guess we can
11:41 < pinchartl> Marex: interesting idea
11:41 < Marex> pinchartl: we can ...
11:42 < pinchartl> so if there's no more discussion topic,
11:42 < pinchartl> Topic 3. Additional Tasks for Q4
11:42 < pinchartl> The following additional tasks have been submitted and approved, they are now going through the usual process. SoWs should be sent in the near future, with a 12/M due date.
11:42 < pinchartl> * ADV748x Dynamic Routing (Jacopo)
11:42 < pinchartl> * M3-N rotation bug fix (Kieran)
11:42 < pinchartl> * Fix RGB output routing on D3 and E3 (Laurent)
11:42 < pinchartl> * Upporting and addition of pixel format (Niklas)
11:42 < geertu> Marex: if we know the parameters at compile-time, we can
11:42 < pinchartl> any question/comment ?
11:43 < neg> Looks good to me
11:43 < Marex> geertu: but then why should it be part of ATF ? We can have the bootrom load the DT
11:43 < jmondi> fine with me, thanks
11:44 < kbingham> Sounds OK to me.
11:44 < geertu> Marex: ATF programs the DRAMC
11:44 < Marex> geertu: but the programming of that is given to ATF by the integrator
11:44 < pinchartl> next, Topic 4. Face to Face Meeting in Edinburgh
11:44 < Marex> geertu: it's literally a few C macros
11:45 < pinchartl> I don't think we should spend time discussing status updates there, as there will not be much
11:45 < pinchartl> are there any particular topic that team members would like to discuss face to face ?
11:45 < kbingham> There's going to be a v4l2 codec meeting at ELCE
11:45 < pinchartl> correct
11:46 < kbingham> But from previous attempts at suggesting codec work - I assume renesas has little interest?
11:46 < neg> Potential plan and for unified DU and VIN test suite :-)
11:46 < kbingham> ^ Plus automated testing, + unit testing :)
11:47 < morimoto> interesting topic for test team
11:47 < pinchartl> kbingham: I wouldn't expect Renesas to have any new interest all of a sudden, but if you can think about a strategy to make them change their mind, I'd love to discuss that
11:50 < kbingham> pinchartl, well that depends on what their concerns are regarding the codecs. Whether it's keeping firmware out - or just completley hiding the implementation altogether. But once there is a standard API for codecs - It would be silly not to use it - and it seems unfortunate not to be part of those early designs
11:50 < pinchartl> I would like to also briefly discuss the GMSL and FPD-Link plans
11:50 < kbingham> Yes :)
11:51 < pinchartl> kbingham: I'll add codecs to the agenda, we can then spend some time discussing how to report the ongoing V4L2 codecs API developments to Renesas
11:51 < pinchartl> any other topic ?
11:52 < jmondi> not from here, thanks
11:52 < kbingham> Dont think so ...
11:53 < neg> not from me
11:53 < morimoto> not from me too
11:53 < morimoto> s/too/either/
11:55 < pinchartl> ok, thanks
11:55 < pinchartl> in that case
11:55 < pinchartl> Topic 5. Next Meeting
11:55 < pinchartl> two weeks from now ?
11:56 < pinchartl> three weeks from now ?
11:56 < pinchartl> four weeks from now ? :-)
11:56 < pinchartl> geertu: wsa: ^^
11:56 < morimoto> * PeriPeri: chat: Chat meeting 18Q4-B
11:56 < morimoto>  
11:56 < morimoto> 	date: 2018-11-08
11:56 < morimoto>  
11:56 < morimoto> 	I/O:    08:00 BST / 09:00 CEST / 10:00 EEST / 16:00 JST
11:56 < morimoto> 	Core:   08:30 BST / 09:30 CEST / 10:30 EEST / 16:30 JST
11:56 < morimoto> 	MM:     09:00 BST / 10:00 CEST / 11:00 EEST / 17:00 JST
11:56 < wsa> geertu already wrote 8.11. and I think this is good
11:56 < morimoto>  
11:56 < wsa> let's check what we agreed with dammsan
11:57 < geertu> pinchartl: That's the date from Morimoto-san's calendar
11:57 < wsa> we agreed that with dammsan
11:57 < pinchartl> ok, 3 weeks from now
11:57 < pinchartl> wsa: indeed
11:58 < pinchartl> that's all for today
11:58 < pinchartl> I propose adjourning the meeting
11:58 < pinchartl> does anyone second ?
11:58 < wsa> ack
11:59 < morimoto> 2nd
11:59 < pinchartl> meeting adjourned, thank you all for attending !