diff options
Diffstat (limited to 'wiki/Chat_log/20160322-mm-chatlog')
| -rw-r--r-- | wiki/Chat_log/20160322-mm-chatlog | 513 |
1 files changed, 513 insertions, 0 deletions
diff --git a/wiki/Chat_log/20160322-mm-chatlog b/wiki/Chat_log/20160322-mm-chatlog new file mode 100644 index 0000000..321be0a --- /dev/null +++ b/wiki/Chat_log/20160322-mm-chatlog @@ -0,0 +1,513 @@ +Multimedia-chat-meeting-2016-03-22 + +<pinchartl> hello [16:55] +<morimoto> Hi +<neg> morning +<pinchartl> let's give Ulrich and Magnus a few more minutes to join [16:57] +<pinchartl> or maybe they're here already ? +<pinchartl> dammsan: hello +<pinchartl> uli___: hello +<morimoto> I couldn't get any response from Magnus during today [16:58] +<morimoto> Maybe he is super busy +<pinchartl> let me try to ping him [16:59] +<dammsan> hi [17:00] +<dammsan> sorry for being late +<pinchartl> hello ! +<pinchartl> no worries +<dammsan> i have more details for the questions +<pinchartl> let's get started [17:01] +<pinchartl> topics for today +<pinchartl> - tasks status update +<pinchartl> - VSP questions from Magnus +<pinchartl> - next meeting / ELC +<pinchartl> anything else ? +<dammsan> nope, not from me +<pinchartl> ok [17:02] +<morimoto> I sent request mail +<pinchartl> morimoto: about vsp suspend/resume ? +<morimoto> Yes, and I would like to 100% for v4.5 on peripelist :) +<pinchartl> good point [17:03] +<morimoto> Ahh, and from BSP +<morimoto> - request API (delayed) +<pinchartl> 4. How will the 50% contract affect development +<morimoto> - plane-alpha, pixel-alp +<pinchartl> added to the agenda [17:05] +<pinchartl> let's get started then +<morimoto> thanks +<pinchartl> let's try to be quick on the tasks status update +<pinchartl> I'll try to handle it per developer this time [17:06] +<pinchartl> ADV7482,v4.7,plan,niklas,Prototype on Gen3 +<pinchartl> ADV7482,v4.8,plan,niklas,Gen3 support upstream +<pinchartl> ADV7482,v4.8,plan,niklas,Interlace support upstream +<pinchartl> VIN+CSI2,v4.7,noplan,niklas,Prototype on Gen3 +<pinchartl> VIN+CSI2,v4.8,noplan,niklas,Gen3 support upstream +<pinchartl> VIN+CSI2,v4.8,noplan,niklas,Interlace support upstream +<pinchartl> VIN,v4.8,noplan,niklas,Gen3 support upstream (without CSI-2) +<pinchartl> neg: what's your status ? +<morimoto> ? noplan ? [17:07] +<neg> Bit of downtime since last meeting waiting for new contract. Working on + VIN+adv7180 hope to be done with VIN for gen2 before ELC +<pinchartl> morimoto: I think we have a plan, that's a mistake [17:08] +<morimoto> OK thanks +<pinchartl> neg: what's left to be done for VIN+ADV7180 ? +<neg> minior shuffeling of code between files per review comments and extra + check for NV16 alignment, nothing big [17:09] +<pinchartl> so you think the next version will be merged ? [17:10] +<neg> yes +<pinchartl> ok +<pinchartl> I'll add a task for that in the list +<neg> thanks +<pinchartl> VIN,v4.7,public,niklas,New VIN driver without soc-camera (tested + on Gen2) [17:11] +<neg> But I was wondering if we should try to get the false gen3 support out + of soc_camera +<pinchartl> we can, it's just a simple patch [17:12] +<pinchartl> does the above schedule still holds for you ? [17:13] +<neg> depending on if I can get the same ammount of time for multimedia as + before, yes [17:14] +<dammsan> neg: you will, but the time may come in boosts +<dammsan> lets discuss more f2f at ELC [17:15] +<pinchartl> let's discuss that as part of topic 3 +<pinchartl> then we have +<pinchartl> - DU+HDMI,v4.7,plan,ulrich,HDMI output on Gen3 prototype +<pinchartl> - DU+HDMI,v4.8,plan,ulrich,HDMI output on Gen3 upstream +<pinchartl> - DU+HDMI,v4.7,prototype,ulrich,Test setup with HDMI output to + HDMI input loopback (without EDID) +<pinchartl> - DU+HDMI,v4.7,public,ulrich,EDID generation support for the HDMI + loopback test setup +<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 +<pinchartl> Ulrich isn't here to update us on the status +<dammsan> also +<pinchartl> I'll ask him to do so by e-mail in a reply to the meeting report +<dammsan> my feeling is that we may want a HDMI video out prototype for Gen3 + earlier [17:16] +<dammsan> if possible +<pinchartl> earlier than v4.7 ? +<dammsan> well, the earlier the better =) +<dammsan> since it is a prototype it does not need to be aligned to upstream + schedule +<dammsan> perhaps something for ulrich to focus on sometime soon if possible + [17:17] +<pinchartl> ok +<pinchartl> I'll write it down +<dammsan> othanks!! +<pinchartl> then [17:18] +<pinchartl> HDMI+sound+output,2016-03-31,plan,morimoto,Prototype on Gen3 +<pinchartl> HDMI+sound+output,2016-03-31,plan,morimoto,Upstream support + without hotplug on Gen2 +<pinchartl> HDMI+sound+output,2016-06-30,plan,morimoto,Hotplug support + upstream +<pinchartl> RSND,2016-06-30,plan,morimoto,Hotplug support upstream on Gen3 +<pinchartl> morimoto: that's for you +<morimoto> I have no update for these +<morimoto> I think I need +3 month for these ? [17:19] +<pinchartl> should we try to align that with upstream kernel versions then ? +<pinchartl> instead of dates +<morimoto> I don't care details :) [17:20] +<pinchartl> we should still set milestones [17:21] +<morimoto> I means version vs date +<pinchartl> just +3 months for all four tasks then ? [17:22] +<morimoto> Because these are based on HDMI+output [17:23] +<morimoto> and not yet supported ? +<pinchartl> correct +<pinchartl> ok, I've recorded that [17:24] +<pinchartl> next +<pinchartl> - VIN,v4.7,plan,magnus,Investigate if/how parallel VIN can be used + on Salvator-X +<dammsan> i did figure that out +<dammsan> it is possible +<dammsan> but we decided to go with it as backup in case CSI gets too hairy +<pinchartl> I'll remove the task then as investigation is done [17:25] +<dammsan> good thanks +<pinchartl> DU+VSPD,2016-03-31,plan,laurent,Z-order support prototype [17:26] +<pinchartl> DU+VSPD,v4.7,plan,laurent,Z-order support upstream +<pinchartl> VSP,v4.8,public,laurent,V4L2 request API upstream +<pinchartl> VSP,v4.7,public,laurent,CLU/LUT support submitted upstream on Gen3 +<pinchartl> VSP,v4.7,prototype,laurent,HGO support upstream on Gen3 +<pinchartl> the plan for z-order support still holds, I'll try to complete it + this week [17:27] +<pinchartl> regarding the request API, I'll try to post the next version + before ELC [17:28] +<pinchartl> as I'll present it in my ELC talk :-) +<morimoto> thanks! +<morimoto> do you have Display-List plan ? [17:29] +<pinchartl> display list support is upstream [17:30] +<morimoto> already do you mean ? +<pinchartl> yes +<morimoto> thanks ! +<pinchartl> it has been merged in Linus' tree +<pinchartl> there are still enhancements that will be merged in v4.7 +<pinchartl> I couldn't get everything upstreamed in one go +<pinchartl> there shouldn't be any delay, the code is ready +<dammsan> how about request API status? [17:31] +<dammsan> is it ready to go, or shall we expect more updates? +<pinchartl> as you probably know I've had a bit of a conflictual relationship + lately with the V4L2 maintainer [17:32] +<pinchartl> it resulted in delays +<dammsan> sure, that's fine +<pinchartl> Mauro said he wouldn't merge (and didn't even review) any media + controller patch before his rework could be merged +<dammsan> internal renesas guys needed to make some workaround to use the + request API in your latest code +<pinchartl> and we're still handling the fallout +<pinchartl> so there will be a new version of the request API +<pinchartl> I hope to post it before ELC [17:33] +<dammsan> can you make sure we can consume it in renesas-drivers? +<pinchartl> I will +<dammsan> thanks. +<morimoto> pinchartl: can you add "Display-List" with "complete" status ? +<morimoto> s/complete/merged/ [17:34] +<morimoto> we would like to know when it was merged +<pinchartl> yes +<morimoto> thanks +<pinchartl> done +<pinchartl> next, [17:35] +<pinchartl> - DU,?,noplan,?,HDMI output support on Alt +<pinchartl> - DU,?,noplan,?,LVDS output support on Gose +<pinchartl> - DU,?,noplan,?,LVDS output support on Alt +<pinchartl> - FDP,2016,noplan,?,Upstream driver +<pinchartl> we still have no plan +<pinchartl> although, for FDP, I have someone who could start working on it + right after ELC +<pinchartl> but we'll need to sort out the budget +<dammsan> the Gen2 DU bits can be slow going IMO, not very important ones +<morimoto> pinchartl: can you send his cost ? I send this mail before to you + [17:36] +<morimoto> s/send/sent/ +<pinchartl> morimoto: sure. I'll reply to your e-mail +<morimoto> thanks +<pinchartl> ok, that's it for the tasks status update [17:38] +<pinchartl> topic 2 - VSP development +<pinchartl> Magnus mentioned that +<pinchartl> 1) request API is not working. +<pinchartl> 2) multiple input is not working. +<pinchartl> 3) UDS (both scale up/down) is not correct result. +<pinchartl> and Morimoto-san, that suspend/resume crashes +<pinchartl> is there anything else ? [17:39] +<dammsan> no, those are the ones i know about +<pinchartl> it's enough for me :-) +<dammsan> i bet =) +<morimoto> hehe :) +<pinchartl> do you have more information about 2 and 3 ? +<dammsan> can we begin by 1) ? [17:40] +<dammsan> we covered it already perhaps +<dammsan> but there is some patch on some internal mail thread to fix + something +<pinchartl> I think we did. there will be a new version for ELC +<pinchartl> now you're being very precise :-D +<pinchartl> could you send them my way ? +<dammsan> morimoto: can you make sure pinchartl: gets the patch related to + request API? +<morimoto> OK, will try [17:41] +<pinchartl> thanks [17:42] +<dammsan> morimoto: please hook up to me via google chat if you need details +<dammsan> pinchartl: while morimoto digs through his email, can we move to 2? +<pinchartl> yes +<pinchartl> do you have more information about 2 and 3 ? [17:43] +<dammsan> yes [17:44] +<dammsan> apparently RPF -> BRU -> WPF is working [17:45] +<dammsan> however in case RPF.1 is connected to BRU.1 there is trouble +<pinchartl> RPF.0 -> BRU.0 + RPF.1 -> BRU.1 ? +<dammsan> sink->source [17:46] +<dammsan> is filled somehow +<pinchartl> it used to work, but might have got broken in recent patches. I'll + investigate that +<morimoto> pinchartl: I send 0001-media-vsp1-workaroud-request-API.patch to + you +<pinchartl> morimoto: thanks +<pinchartl> dammsan: I'd like to create automated test scripts for the vsp + driver [17:48] +<pinchartl> but haven't had time to work on that yes +<dammsan> pinchartl: thanks +<dammsan> i've asked morimoto-san to send a patch related to 2) as well +<pinchartl> ok :-) +<pinchartl> how about 3 ? [17:49] +<dammsan> right +<dammsan> result of UDS is not correct +<dammsan> we don't know much detail about it +<dammsan> but perhaps you can show us your test case? [17:50] +<dammsan> that is known to work? =) +<pinchartl> it could also be a regression +<pinchartl> I've tested it before +<pinchartl> I'll retest it +<dammsan> thanks +<dammsan> the multimedia guys say they want to add more feature requests +<morimoto> pinchartl: sending done [17:51] +<pinchartl> because we don't have enough work ? :-) +<dammsan> but prefer to get the basic features finished first +<pinchartl> morimoto: thanks +<dammsan> i guess they may not be aware of the delay invovled +<pinchartl> when do the multimedia guys want all that to be fixed ? [17:52] +<dammsan> then theralready +<dammsan> err +<dammsan> already +<dammsan> they said they requested to have it in february, but got it + semi-working in march [17:53] +<dammsan> they seem to be concerned about plane-alpha and pixel-alpha ass well +<pinchartl> the request API, or the multiple inputs + UDS ? [17:54] +<pinchartl> multiple inputs + UDS is definitely a regression +<pinchartl> I've successfully tested it when the features were merged +<pinchartl> I'll add plane-alpha + pixel-alpha to the todo list +<pinchartl> target is v4.7 +<dammsan> thanks +<dammsan> how about we confirm priority of the current list when we meet these + guys f2f tomorrow [17:55] +<pinchartl> that's a good idea [17:56] +* uli___ sneaks in +<pinchartl> hi Ulrich [17:57] +<pinchartl> last item is suspend/resume crashes +<pinchartl> I haven't tested that on Gen3 as we don't have propery + suspend/resume support +<pinchartl> however I expect the crash to happen on Gen2 as well +<dammsan> fix gen2 first? +<pinchartl> of course [17:59] +<pinchartl> I'll add it to the todo list too +<pinchartl> which gets quite full for v4.7 +<pinchartl> I'll mark it for v4.8, but I'll let you confirm priorities in your + meeting tomorrow +<dammsan> thanks [18:01] +<pinchartl> anything else for the vsp ? +<dammsan> we will bring information from that meeting to f2f meet up at ELC +<dammsan> not that i am aware of +<pinchartl> ok, thank you +<morimoto> Does datasheet for VSP was OK for you ? [18:02] +<pinchartl> topic 3 +<pinchartl> morimoto: I think so +<morimoto> good +<pinchartl> how will the 50% contract affect multimedia development ? [18:03] +<pinchartl> we have no shortage of work +<pinchartl> and everything is urgent +<pinchartl> yet, the contracts will be reduced to 50% for April +<pinchartl> how do we deal with that ? +<dammsan> i doubt it will be very visible from the outside [18:04] +<dammsan> if one month drops and two other months increases +<dammsan> but that is not your concern perhaps? =) +<pinchartl> does that mean May and June could be covered by contracts at 125% + then ? +<morimoto> I think Base 50% + Additional 25% + Additional 25% [18:05] +<dammsan> the total amount of cash remains unchanged +<pinchartl> if we have 50 in April, 100 in May and 100 in June, that's 250 + instead of 300 +<pinchartl> (I'm talking about development time, no cash) +<dammsan> but we never have that amount of time anyway +<dammsan> with other customers and paperwork due dates [18:06] +<pinchartl> let's put it another way +<dammsan> so first month is always short before invoice? +<dammsan> sure, i'll be silent =) +<pinchartl> when I have to send a report by the 17th of the first month, I + still work from the 17th to the end of the month [18:07] +<dammsan> uli___: please chat with me using google chat about tasks +<uli___> ok +<dammsan> pinchartl: sure +<pinchartl> are we expected to work less during April compared to what we've + done so far ? +<dammsan> you may include the second half of your patches in the second + report? +<pinchartl> less = 50% of a normal month +<dammsan> it is up to you really [18:08] +<pinchartl> dammsan: I might, but I still work during the second half of the + last month of the contract +<dammsan> since you only have the base contract +<dammsan> you will not be sure how much you can adjust your work later on +<pinchartl> my point is that, if we reduce the contract scope to 50% for April + and leave it to 100% in May and June, that's 250 work time points + instead of the usual 300 +<pinchartl> meaning development will be slowed down [18:09] +<dammsan> so may and june may get more busy +<dammsan> so if you want to reduce your burden then work a bit more for base + in april to make room for may and june? +<pinchartl> so, to put it another way, is Renesas asking us to work for free + half of April because we might get more work later ? +<dammsan> no? +<dammsan> renesas is asking you to do what is written in the contract. [18:10] +<dammsan> period. +<pinchartl> but at the same time they're asking us to deliver features faster + than what we've done so far +<dammsan> hm..? +<pinchartl> "please deliver faster, but work only 50% to do so" +<pinchartl> doesn't make too much sense to me :-) +<dammsan> that portion that i don't understand +<dammsan> who asks you to deliver sooner? +<pinchartl> you mentioned earlier that HDMI output for Gen3 should be done + before v4.7 if possible [18:11] +<pinchartl> and that the VSP1 issues are expected to be fixed already +<pinchartl> that means we're considered to be too slow +<dammsan> i think you are right [18:12] +<dammsan> sorry about that feeling +<dammsan> but it is related to too much work and too little resources +<dammsan> about that HDMI Gen3 drop it is just from my side that we should aim + for something sooner IMO +<dammsan> but we need to look at the big picture [18:13] +<pinchartl> so, what are we expected to do ? +<dammsan> with reduced amount of time in April it sure looks like April will + move slower +<dammsan> we do what we can do with the amount of time we have? +<dammsan> following priority? +<pinchartl> I can certainly leave the option to all developers in the team to + work 100% in April while being paid 50% +<pinchartl> but I won't request anyone to do so +<dammsan> of course spreading out work evenly over 3 months makes sense + [18:14] +<dammsan> but we need time to finalize the additional tasks +<dammsan> so there will unfortunately be a delay +<pinchartl> the additional tasks for May and June will cover 50%, right ? + [18:15] +<pinchartl> so that's 250 instead of 300 in total for Q2, correct ? +<dammsan> in my mind they may be more fixed-price than time based +<dammsan> but we need to discuss more +<dammsan> 250 has never been the goal [18:16] +<dammsan> it has always been 300 +<dammsan> so we need to find a good balance for the amount of work in the last + two months of the quarter +<pinchartl> could it be that the additional tasks will cover more than 50%, + resulting in ~300 for Q2 in total ? [18:17] +<dammsan> it depends on how much time each individual has +<dammsan> but yes, if the total should be 300 then it must become like that +<pinchartl> of course, but do you think it could be so ? +<dammsan> it could be how? [18:18] +<pinchartl> because in that case it could make sense to work more than what + the contract covers in April and deliver the result in May and + June +<pinchartl> (but again it would be a personal decision, I won't request anyone + to do so) +<dammsan> yes, working more earlier would be excellent +<dammsan> but no papers yet i'm afraid [18:19] +<pinchartl> I'm sure Renesas won't complain if we work more than we're paid + :-) +<dammsan> so it is difficult to say what to work on =) +<pinchartl> the question is whether there's a reasonable chance that that + "overtime" could be covered by additional tasks in May and June +<dammsan> define overtime =) +<pinchartl> working 100% in April instead of 50% [18:20] +<pinchartl> obviously guessing what would be requested in May and June +<pinchartl> but we can have a reasonable guess +<pinchartl> I'm pretty sure HDMI output will be requested for instance +<pinchartl> if you tell me now that, if I can prepare already in April, + there's a 90% chance Renesas will want to request more from me in + May and June, there's an incentive [18:22] +<pinchartl> if the chance is 5%, less so :-) +<pinchartl> I'm trying to understand what will happen +<dammsan> ifok i see [18:23] +<dammsan> (sorry, got kicked out from my VM) +<pinchartl> and with the multiple hops between our team and the decision + makers in Renesas, plus the language barrier and the business + culture differences, it's hard for me to be confident about my + understanding of the situation +<dammsan> if people are willing to work more w/o papers +<dammsan> then i propose that we simply list one major task for each member + that can be focused on in april and we think will be included as + additional task [18:24] +<pinchartl> ok +<pinchartl> I believe we can keep our current focus in April [18:25] +<pinchartl> on HDMI, VIN and VSP +<pinchartl> each will require more than 10 days (50%) to complete +<pinchartl> they might be covered by the base contract or additional tasks in + May and June +<pinchartl> but in both cases I believe they will be covered [18:26] +<dammsan> yes, good plan +<pinchartl> we need to make sure we only include 50% of the deliverables in + the April report though +<dammsan> no need to play too many paper games IMO +<dammsan> but it is up to you how you want to roll +<dammsan> if code is queued up and working then report contents are not + important [18:27] +<dammsan> just a formality +<pinchartl> I personally won't change my work pace for April (well, except + that I won't code much during ELC) +<dammsan> same here +<pinchartl> ok [18:28] +<pinchartl> should I record this in the meeting report or should I leave it + out ? +<neg> same here if it's ok for me to post patches based on datasheets while I + do not have a contract [18:29] +<pinchartl> I don't think your NDA expires at the end of the SoW +<dammsan> it is up to you +<pinchartl> so that shouldn't be a problem +<pinchartl> I'll leave it out of the meeting minutes, I'm not sure how I + should phrase it [18:30] +<pinchartl> last topic +<dammsan> my only additional comment about this is +<pinchartl> yes ? +<dammsan> if you are planning vacation, feel free to do so in april instead of + may/june =) [18:31] +<pinchartl> good point :-) +<pinchartl> I'll write that down +<dammsan> thanks +<neg> ok thanks, it was the NDA part that gave me the most grief :) +<pinchartl> neg: please read your NDA in details though [18:32] +<pinchartl> I'm not a lawyer +<pinchartl> topic 4 [18:33] +<pinchartl> next meeting +<pinchartl> the next meeting would be in 2 weeks +<pinchartl> which is ELC time +<pinchartl> who will attend ELC ? [18:34] +<pinchartl> Magnus, you said you will be there +<dammsan> yes +<pinchartl> Niklas as well ? +<neg> yes +<pinchartl> Ulrich, you don't plan to attend if I remember correctly ? +<pinchartl> how about Morimoto-san ? +<uli___> correct +<pinchartl> is Morimoto-san stuck in an interrupt storm again ? [18:36] +<dammsan> maybe [18:37] +<dammsan> he is coming +<dammsan> i know it =) +<pinchartl> :-) [18:38] +<morimoto> I was ked-napped by Magnus, so yes I will got to ELC +<pinchartl> :-D +<pinchartl> very nice +<pinchartl> we'll have the next meeting there +<morimoto> F2F meeting :) +<pinchartl> I think that's it for today then +<pinchartl> thank you everybody for joining [18:39] +<morimoto> thanks +<neg> pinchartl: do you have any more information about the mini multimedia + meeting? +<pinchartl> it will be held on Thursday +<dammsan> pinchartl: is this meeting including members outside this group? + [18:40] +<pinchartl> that's all I know for now +<dammsan> or is it for our group? +<pinchartl> that's the linux media mini-summit +<dammsan> ok cool +<pinchartl> we'll have another meeting for our group during the week +<dammsan> any ideas when to meet? +<morimoto> My departure time is 8th April +<dammsan> for me meeting with you guys is top prio [18:41] +<dammsan> it may make sense to decide right away if possible +<neg> ok I got a mail from Hans telling me to let Maruo know if I wanted to + attend, I drop him a mail and see if I can find out more +<pinchartl> let me see if the conference schedule has been published +<morimoto> Do I need something for this mini-summit ? [18:42] +<neg> I have nothing else planed during ELC so anytime works for periperi + meetup +<pinchartl> ok, my talk is on Tuesday morning [18:43] +<pinchartl> morimoto: if you want to join the mini-summit you just have to be + there and listen. and possibly talk too :-) +<pinchartl> I've sent a mail and CC'ed the three of you to ask if we have + seats [18:44] +<pinchartl> I think we will +<pinchartl> I'd prefer the F2F meeting to be on Tuesday afternoon or on + Wednesday +<morimoto> pinchartl: OK, no ticket, no register are needed +<morimoto> Thanks [18:45] +<dammsan> i'm fine either Tuesday or Wednesday +<pinchartl> let's go for Tuesday right after lunch ? +<pinchartl> or maybe starting at lunch time ? [18:46] +<morimoto> pinchartl: every time is OK for me during 4th - 8th (morning) + [18:47] +<dammsan> start at lunch time must be good +<pinchartl> I'll see if I can find a nice place to have a team lunch away from + the crowd [18:48] +<pinchartl> on Tuesday +<neg> works for me +<pinchartl> ok, I think we're done +<pinchartl> and I have to go +<pinchartl> good timing :-) +<pinchartl> thank you all for attending +<pinchartl> and see you in San Diego ! +<dammsan> thank you!! +<neg> thanks +<dammsan> see ya in CA +<morimoto> Thanks [18:49] |