diff options
Diffstat (limited to 'wiki/Chat_log/20160511-mm-chatlog')
| -rw-r--r-- | wiki/Chat_log/20160511-mm-chatlog | 395 |
1 files changed, 395 insertions, 0 deletions
diff --git a/wiki/Chat_log/20160511-mm-chatlog b/wiki/Chat_log/20160511-mm-chatlog new file mode 100644 index 0000000..2730dfe --- /dev/null +++ b/wiki/Chat_log/20160511-mm-chatlog @@ -0,0 +1,395 @@ +Multimedia-chat-meeting-2016-05-11 + +<neg> morning/evening all [16:54] +<pinchartl> it feels like night +<morimoto> it is 17:00 in Japan [16:55] +<pinchartl> night is when I haven't had enough sleep yet :-) +<neg> with your definition of afternoon I can relate :-) +<uli___> good morning +<pinchartl> :-) +<pinchartl> good morning everybody [16:56] +<pinchartl> Magnus is excused for today +<pinchartl> so we can start +<pinchartl> topics for today [16:57] +<pinchartl> - Topic 1. Status check for the multimedia tasks +<morimoto> 1 question. is it 10:00 CEST in Europe ?? +<pinchartl> yes it is [16:58] +<pinchartl> - Topic 2. Next meeting +<pinchartl> we can also discuss additional tasks for June +<morimoto> OK, pinchartl invite was "10:00 CEST / 18:00 JST" but, "17:00 JST" + seems is correct +<pinchartl> but I believe I've already discussed those tasks with you + individually (well, only with Ulrich and Niklas obviously) +<pinchartl> oops, sorry about that [16:59] +<pinchartl> I'll fix it for the next meeting +<morimoto> No problem :) +<pinchartl> anything else for the agenda ? +<morimoto> About RenesasCon [17:01] +<morimoto> very short topic +<pinchartl> we've briefly discussed that during the core meeting yesterday, if + you have additional information we can talk about it, sure +<morimoto> About multimedia topic [17:02] +<pinchartl> ok +<pinchartl> let's start with Magnus as he's not here :-) +<pinchartl> VIN,?,plan,magnus,IPMMU integration on Gen2 [17:03] +<pinchartl> VIN,?,plan,magnus,IPMMU integration on Gen3 +<pinchartl> VIN,?,plan,magnus,IPMMU support on Gen2 +<pinchartl> VIN,?,plan,magnus,IPMMU support on Gen3 +<pinchartl> I don't believe there has been any progress in that area +<pinchartl> that was easy +<pinchartl> now, in alphabetical order, Morimoto-san +<pinchartl> RSND,2016-06-30,plan,morimoto,DT bindings for HDMI sound +<pinchartl> RSND,2016-06-30,plan,morimoto,dw-hdmi-ahb-audio prototype on Gen3 +<pinchartl> RSND,2016-06-30,plan,morimoto,HDMI SSI prototype on Gen3 +<pinchartl> RSND,2016-06-30,plan,morimoto,HDMI sound Upstream support without + hotplug on Gen2 +<pinchartl> RSND,2016-09-30,plan,morimoto,Hotplug support upstream on Gen3 + [17:04] +<pinchartl> anything to report there ? +<morimoto> OK, I created prototype HDMI sound output +<morimoto> it start works ! +<pinchartl> nice ! +<morimoto> but, it is using existing DT binding +<morimoto> and super local HDMI sound coding +<morimoto> My headacke is that how to solve DT things [17:05] +<morimoto> And +<pinchartl> (DT is a pretty popular headache) +<morimoto> yes +<morimoto> this is based on Ulrich's HDMI out prototype +<morimoto> but his prototype is maybe based on BSP (?) [17:06] +<morimoto> becasuse of this +<morimoto> my sound is prototype of prototype +<pinchartl> :-) +<morimoto> HDMI DT itself is very specical +<pinchartl> that's understandable +<morimoto> this is current my status [17:07] +<pinchartl> does that cover "HDMI sound Upstream support without hotplug on + Gen2" too ? +<morimoto> not Gen2 [17:08] +<morimoto> only Gen3 +<morimoto> HDMI Gen2 was working, and some other guy posted its driver +<morimoto> driver patch +<morimoto> sorry, again +<morimoto> HDMI Gen2 was working on my dest, but I didn't posted it to ML +<morimoto> because of DT +<pinchartl> ok [17:09] +<morimoto> but some other guy posted its driver patch to ML +<morimoto> but it is not yet accepted, because of DT +<morimoto> Yes, DT is bottleneck +<pinchartl> that's ADV7511, right ? +<morimoto> I forgot detail number but yes, ADV7xxx [17:10] +<pinchartl> ok +<pinchartl> then, Niklas +<pinchartl> let's start with the v4.7 tasks [17:11] +<pinchartl> ADV7482,v4.7,plan,niklas,Prototype on Gen3 +<pinchartl> VIN,v4.7,plan,niklas,CSI2 prototype (Gen3) +<pinchartl> VIN,v4.7,public,niklas,New VIN driver without soc-camera (tested + on Gen2) +<pinchartl> and then we'll have +<pinchartl> ADV7482,v4.8,plan,niklas,Gen3 support upstream +<pinchartl> ADV7482,v4.8,plan,niklas,Interlace support upstream +<pinchartl> VIN,v4.8,plan,niklas,CSI2 interlace support upstream (Gen3) +<pinchartl> VIN,v4.8,plan,niklas,CSI2 support upstream (Gen3) +<pinchartl> VIN,v4.8,plan,niklas,Gen3 support upstream (without CSI-2) +<pinchartl> and finally +<pinchartl> VIN,?,plan,niklas,Gen3 support +<pinchartl> VIN,?,plan,niklas,Scaler support (on Gen3) +<pinchartl> anything to report ? +<neg> Gen2 driver is accepted by Hans and pull request is sent for media_tree + but I have not yet seen it picked up there [17:12] +<neg> basic prototype of VIN on Gen3 with CSI2 and ADV7482 from BSP is working +<pinchartl> good news ! [17:13] +<pinchartl> Mauro usually takes a couple of days to handle pull requests +<neg> now that we have agreed an a design plan for VIN on Gen3 I can start + focusing on that +<neg> plan is to have that done by end of may [17:14] +<pinchartl> have you posted the prototype code ? +<neg> no and there I have a question, what repository should I try to target + for the full prototype that migh contiain some local hacks for CSI2 and + ADV7482 ? [17:15] +<pinchartl> (it doesn't have to be patches, a mail to linux-renesas-soc with a + link to a git branch is fine) +<pinchartl> I'm not sure to understand the question [17:16] +<pinchartl> do you mean what you should use as a base ? +<neg> the additional contract for VIN on Gen3 stats code should be avaliable + for easy testing from a repository, since parts of the prototype will + need not yeat ready BSP code I'm not sure where I should try to get it + public [17:17] +<pinchartl> it should be publicly available, but it doesn't have to be merged + in an upstream repository +<pinchartl> do you have a personal git tree somewhere ? [17:18] +<neg> yes, is that good enough? [17:19] +<pinchartl> for prototype code, sure +<pinchartl> but make sure you keep the branch there until the code is merged + upstream +<neg> then I'm happy, will make the hack prototye availabe there and keep it + updated with my progress [17:20] +<pinchartl> please let me know when you post the code, I'll update the tasks + status [17:21] +<neg> will do, keep in mind that the prototype is a hack not contaning the + design we talked about in our mail thread [17:22] +<pinchartl> sure +<pinchartl> so next step is VIN Gen3 for end of May, right ? +<neg> yes +<pinchartl> remind me, that includes CSI-2 but not ADV7482 ? [17:23] +<neg> No CSI2 is not mandatory but yes it will requier me to work on the CSI2 + parts anyhow [17:24] +<pinchartl> ok +<neg> I think csi2 would be a separat task just like adv7482 +<pinchartl> it makes sense [17:25] +<pinchartl> so [17:26] +<pinchartl> the existing tasks are +<pinchartl> ADV7482,v4.8,plan,niklas,Gen3 support upstream +<pinchartl> ADV7482,v4.8,plan,niklas,Interlace support upstream +<pinchartl> VIN,v4.8,plan,niklas,CSI2 interlace support upstream (Gen3) +<pinchartl> VIN,v4.8,plan,niklas,CSI2 support upstream (Gen3) +<pinchartl> VIN,v4.8,plan,niklas,Gen3 support upstream (without CSI-2) +<pinchartl> VIN,?,plan,niklas,Gen3 support +<pinchartl> VIN,?,plan,niklas,Scaler support (on Gen3) +<pinchartl> we need to adjust that +<pinchartl> "VIN Gen3 support" is for end of May +<pinchartl> I'll set it to v4.7 as it doesn't have to be merged upstream + [17:27] +<neg> sounds about right yes +<pinchartl> scaler support isn't scheduled yet +<pinchartl> but that's support to be part of the base contract [17:28] +<neg> no and I don't think it will requier so much work so I'm hoping to do + that in my base contract during Q3 +<pinchartl> should I tentatively schedule it for v4.8 ? +<neg> sure [17:29] +<pinchartl> do you think the schedule will hold for the v4.8 tasks ? [17:30] +<neg> not sure about the problem set for interlace but other then that yes + [17:31] +<pinchartl> they're all about upstream [17:32] +<pinchartl> so v4.8 means merged in Mauro's tree at the end of the v4.7 + development cycle +<pinchartl> which is end of this quarter +<neg> hum then no it might be a bit steap giving the phase VIN for Gen2 moved +<pinchartl> I'll move them all to v4.9 [17:33] +<neg> yes I think that is better [17:34] +<pinchartl> next, Ulrich +<pinchartl> DU,?,plan,ulrich,Atomic API test program +<pinchartl> DU,v4.7,plan,ulrich,HDMI output on Gen3 prototype +<pinchartl> DU,v4.7,prototype,ulrich,Test setup with HDMI output to HDMI input + loopback (without EDID) +<pinchartl> DU,v4.7,public,ulrich,EDID generation support for the HDMI + loopback test setup +<pinchartl> DU,v4.8,plan,ulrich,HDMI output on Gen3 upstream +<pinchartl> VIN,v4.7,public,ulrich,Add DV timings support to rcar-vin +<pinchartl> VIN,v4.7,public,ulrich,Upstream Lager HDMI input bug fixes +<uli___> for dv timings for rcar-vin, i have a new series to post today + [17:35] +<uli___> adapted to rcar-vin v6 +<pinchartl> for Niklas' new rcar-vin driver ? +<uli___> yes +<pinchartl> nice +<uli___> and i have a 12-hour old prototype of hdmi out on gen3 +<uli___> that works +<pinchartl> :-) [17:36] +<uli___> but takes a few shortcuts :) +<pinchartl> congratulations +<uli___> it's based on the bridge-API-converted du driver +<pinchartl> I'll move dv-timings to v4.8 then, as the v4.7 merge window is + about to open. if we can make it to v4.7 it would be nice so + please try if possible +<uli___> i'll do my best [17:37] +<pinchartl> thank you +<pinchartl> have you posted the HDMI output prototype already ? +<uli___> not yet. i can send whatever i have right now to periperi, it may + help morimoto-san +<pinchartl> please do [17:38] +<uli___> i'll be on vacation in another 12 hours or so :) +<pinchartl> and let me know when it will be done, I'll update the task +<pinchartl> :-) +<pinchartl> when will you come back ? +<uli___> i'll be back in full force on the 23rd +<morimoto> uli___: does it measn it have no issue on HDMI1-OUT ? +<uli___> moment +<uli___> no, i'm using hdmi1 :) [17:39] +<morimoto> OK, nice. and base on which branch ? +<uli___> i have to look that up, i'll tell you [17:40] +<morimoto> OK, thanks ! +<morimoto> I need to update HDMI sound :) +<pinchartl> no progress yet on the test program I suppose ? +<uli___> none yet +<pinchartl> ok [17:41] +<pinchartl> regarding Gen3 HDMI support upstream, do you think v4.8 is + feasible ? +<uli___> that would be end of the quarter? +<pinchartl> yes +<pinchartl> or will you need more time to clean up the local hacks used in the + prototype ? [17:42] +<uli___> _might_ work +<pinchartl> ok +<pinchartl> and about +<pinchartl> - DU,v4.7,prototype,ulrich,Test setup with HDMI output to HDMI + input loopback (without EDID) +<pinchartl> - DU,v4.7,public,ulrich,EDID generation support for the HDMI + loopback test setup +<pinchartl> please document the setup in the elinux wiki [17:43] +<uli___> ok +<pinchartl> I want to mark those tasks as complete, they've been there for + quite some time and there isn't too much left to do +<uli___> the edid generation actually works, it's part of the patch series + [17:44] +<uli___> even though hans has a mild dislike for it +<pinchartl> the series you will repost today rebased on rcar-vin v6 ? +<uli___> yes +<pinchartl> ok, I'll then have a look at it [17:45] +<pinchartl> and finally, what about +<pinchartl> - VIN,v4.7,public,ulrich,Upstream Lager HDMI input bug fixes +<geertu> uli___: If you post the HDMI output prototype to periperi, I can + include it in next renesas-drivers (that's gonna be next week, v4.6) +<neg> me too, I got a new setup just to test hdmi in :) +<uli___> pinchartl: i have trouble remembering what this is about... +<pinchartl> (geertu: on a side note, I'll also have vsp1 code for the next + renesas-drivers) [17:46] +<pinchartl> I think that was the adv7604 driver fixes +<uli___> that has made it upstream, i think [17:47] +<uli___> "[media] adv7604: fix SPA register location for ADV7612" +<geertu> (pinchartl: If you add it to drm/du/vsp1-kms/boards, it'll be in) +<pinchartl> uli___: perfect, thanks [17:48] +<pinchartl> (geertu: I'll split it in topic branches as you requested :-) and + will let you know) +<pinchartl> now it's my turn [17:49] +<pinchartl> DU,?,plan,laurent,DU+VSPD Integration in Renesas drivers (Gen3) +<pinchartl> DU,?,plan,laurent,IPMMU integration on Gen3 +<pinchartl> DU,?,plan,laurent,IPMMU support on Gen3 (through VSPD+FCP) +<pinchartl> DU,v4.7,public,laurent,VSPD Z-order support upstream (Gen3) +<geertu> (pinchartl: Even better ;-) +<pinchartl> VSPD Z-order support is ready, I'll send a pull request today + [17:51] +<pinchartl> DU+VSPD integration should already be in renesas-drivers +<pinchartl> no progress on IPMMU integration +<pinchartl> then, on the VSP side [17:53] +<pinchartl> - VSP,v4.8,plan,laurent,HGO operation mode selection [17:54] +<pinchartl> - VSP,v4.8,plan,laurent,HGO support upstream on Gen3 +<pinchartl> - VSP,v4.8,plan,laurent,HGO test application +<pinchartl> patches will be posted today +<pinchartl> the schedule holds +<pinchartl> although discussions about the API showed some disagreements + [17:55] +<pinchartl> but nothing too big so far +<pinchartl> - VSP,v4.8,plan,laurent,Fix suspend/resume crash [17:56] +<pinchartl> - VSP,v4.8,public,laurent,CLU/LUT support submitted upstream on + Gen3 +<pinchartl> no progress so far +<pinchartl> - VSP,?,plan,laurent,Fixed alpha support (VI6_DPR_*_ROUTE.FXA) +<pinchartl> - VSP,?,plan,laurent,CLU WARN_ON fix +<pinchartl> - VSP,?,plan,laurent,CLU 2D and 3D mode support +<pinchartl> - VSP,?,plan,laurent,CLU/LUT test application +<pinchartl> - VSP,?,plan,laurent,CLU/LUT upstream API +<pinchartl> - VSP,?,plan,laurent,UDS regression fix +<pinchartl> no progress so far either +<pinchartl> - VSP,v4.8,public,laurent,V4L2 request API usable prototype + [17:57] +<pinchartl> this is becoming the hot topic for VSP development +<pinchartl> now that I've completed HGO I can focus on it again +<pinchartl> other developers started showing interest, in particular Sakari + Ailus posted a new version of my patch series last week with + additional improvements [17:58] +<pinchartl> I plan to post a new version myself over the weekend +<pinchartl> the scheduled date to finalize this is end of this month +<horms> geertu: I'm finished with the M3 board now. Sorry for not letting you + know I was using it earlier +<pinchartl> morimoto: you were interested in additional information about the + request API, does this answer your questions ? [18:00] +<morimoto> our side would like to test it, not additional information :) +<morimoto> of course it is very nice information for us [18:01] +*** khiemnguyen (d2a0fca8@gateway/web/cgi-irc/kiwiirc.com/ip.210.160.252.168) + has quit: Quit: http://www.kiwiirc.com/ - A hand crafted IRC client +<pinchartl> :-) +*** khiemnguyen (d2a0fca8@gateway/web/cgi-irc/kiwiirc.com/ip.210.160.252.168) + has joined channel #periperi +<pinchartl> that's it for the existing tasks then +<pinchartl> ah no [18:02] +<pinchartl> FDP,v4.8,plan,laurent,Develop and upstream driver +<pinchartl> Kieran is working on this +<kbingham> Ack! +<pinchartl> I've received the new salvator-x board yesterday, DHL should pick + it up today +<pinchartl> v4.8 might be a bit tight, but it can still be doable [18:03] +<pinchartl> depending on the amount of changes requested during review +<morimoto> salvator-x yesterday ? very delay... +<kbingham> indeed I am currently 'virtually' working on it :) +<pinchartl> as it's a mem-to-mem driver I don't expect lots of push back +<pinchartl> morimoto: they wanted to deliver it on the first day after I left + Finland :-/ +<pinchartl> I only came back home last Saturday [18:04] +<morimoto> Ahh, OK +<pinchartl> and for some reason they didn't try to deliver it on Monday +*** horms (~horms@reginn.isobedori.kobe.vergenet.net) has quit: Ping timeout: + 276 seconds +<morimoto> It seems Europe has GW too :) +<pinchartl> the board arrived in Helsinki on the 22nd, I left Finland on the + 27th +<pinchartl> so, that's it for the tasks [18:05] +<pinchartl> Topic 2. Additional '50%' tasks [18:06] +<pinchartl> we've discussed the tasks for June previously +<pinchartl> I'll submit them to Magnus today +<pinchartl> unchanged compared to our last discussions on the topic +<pinchartl> any question or comment about that ? +<uli___> go right ahead [18:07] +<neg> not from me +<pinchartl> easy :-) +<pinchartl> Topic 3. RenesasCon +<pinchartl> morimoto: would you like to talk about that ? +<morimoto> Renesas side would like to discuss, and share information about + MultiMedia things. +<morimoto> BSP team who need to deliver MultiMedia items to customer will have + presentation about their plan. [18:08] +<morimoto> I guess Laurent/Kieran/Niklas related to this ? +<morimoto> not sure +<morimoto> if you have any comment, question, etc. please prepare about it +<pinchartl> uli___: you won't be in Japan, right ? +<uli___> no +<pinchartl> neg: will you be there ? +<pinchartl> kbingham: how about you, any plan to attend LinuxCon Japan ? :-) + [18:09] +* kbingham checks when LinuxCon Japan is... +<morimoto> kbingham: July 13th - 15th +<pinchartl> the meeting with Renesas will be on the 12th +<neg> yes I booked the trip yesterday will arive the 10th and stay untill the + 16th +<kbingham> pinchartl: morimoto: I would love to - but it is rather close to my + wedding, and I may find my self in trouble if I'm the other side of + the world ;) [18:10] +<pinchartl> kbingham: we will celebrate your wedding drinking nihonshu then + :-) [18:11] +<morimoto> kbingham: congratulation about wedding ! +<kbingham> pinchartl: I hope so :) [18:12] +<kbingham> morimoto: Thankyou :) +<morimoto> OK, pinchartl and neg can be Japan +<pinchartl> ok, I'll prepare a presentation about our status, short term and + longer term plans for the meeting in Japan then. I'll submit it as + a discussion topic for one of the renesas multimedia group chats + before LCJ +<morimoto> pinchartl: Thanks +<pinchartl> last topic, next meeting [18:13] +<neg> I also booked all nights at the LCJ hotell, hope it is possible to get + to Renesas from there? +<pinchartl> I propose two weeks from now +<pinchartl> 25th of May +<pinchartl> same place, same time +<pinchartl> neg: it's a bit of a commute, but it's possible :-) +<morimoto> same time means 17:00 JST ? :) [18:14] +<pinchartl> morimoto: yes +<pinchartl> 10 CEST +<morimoto> OK +<morimoto> I'm OK [18:15] +<pinchartl> uli___ and neg ? +<uli___> ok for me +<pinchartl> and kbingham ? +<neg> OK +<kbingham> pinchartl: Ok by me! [18:16] +<pinchartl> kbingham: it will be a good occasion to report your progress on + the FDP driver, and congratulate the Renesas hardware engineers + for the amazing hardware design (or share your frustration and + find a shoulder to cry on) :-) +<pinchartl> ok, that's it for today then [18:17] +<pinchartl> thank you all for attending +<pinchartl> and keep the good work +<pinchartl> looking forward to more patch bombs in my inbox +<morimoto> Hehe :) thank you. bye [18:18] +<uli___> have a good day +<neg> thanks all, bye |