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

Multimedia-chat-meeting-2016-12-07

<morimoto> Hi  [16:59]
<pinchartl> hello
<neg> hi all
<morimoto> Hyvaa huomenta  [17:00]
* morimoto I can't pronunciation
*** uli___ (~uli___@static.206.203.46.78.clients.your-server.de) has joined
    channel #periperi  [17:01]
<pinchartl> morimoto: even writing it is difficult on your keyboard :-)
<pinchartl> do you have a key for ä ?
<morimoto> Unfortunately, No.
<morimoto> :P
<pinchartl> kbingham said he might not be able to attend the meeting today
								        [17:03]
<kbingham> pinchartl: Terribly sorry to say I managed to make it (just)
<pinchartl> :-)
<pinchartl> welcome !
<pinchartl> and Magnus seems to be missing
<kbingham> Morning all :D
<morimoto> Morning kbingham  [17:04]
<uli___> morning
<pinchartl> so let's get started
<pinchartl> topics for today
<pinchartl> - Status check for the multimedia tasks  [17:05]
<pinchartl> - Next meeting
<pinchartl> anything else ?
<morimoto> FOSDEM ?
<morimoto> (I don't go though)
<pinchartl> the rabbits will miss you  [17:06]
<morimoto> Hehe :) me to
<morimoto> too
<pinchartl> so  [17:07]
<pinchartl> Topic 1. Status check for the multimedia tasks
<pinchartl> kbingham: do you mind starting ?
<kbingham> pinchartl: I'd actaully like to go last so I can upload something
	   :D  [17:08]
<kbingham> (which will show why I was skiiving of work yesterday to work on a
	   personal project :D)
<pinchartl> ok, let's reverse the order then
<pinchartl> uli___: your turn
<uli___> ok
<uli___> so i collected a bunch of patches and checked if the vsp-tests run
	 with ipmmu enabled  [17:09]
<uli___> on gen3
<uli___> with a little fix, they do
<uli___> although i had a few issues on m3-w
<pinchartl> what kind of issues ?
<uli___> where the system gets sluggish when running vsp-tests, with or
	 without ipmmu enabled
<uli___> sometimes it freezes
<uli___> but the tests pass  [17:10]
<uli___> haven't found out what that could be
<pinchartl> I haven't noticed that
<pinchartl> but I mostly use H3
<uli___> no issues on h3  [17:11]
<pinchartl> ok, we'll need to investigate that
<pinchartl> I'm a bit surprised that IPMMU works given that it's supposed to
	    be broken at the hardware level  [17:12]
<uli___> :)
<pinchartl> issues and blockers ?  [17:13]
<uli___> pressed for time. other than that, none
<pinchartl> I see you'll be on vacation from next Monday to the 3rd of January
	    ?  [17:14]
<uli___> yes
<morimoto> Wow! winter vacation ?
<pinchartl> have fun, both finishing all your tasks before that, and during
	    your vacation :-)
<uli___> :)  [17:15]
<pinchartl> next, neg
<neg> A) Nothing
<neg> B) Address CSI2 review comments  [17:16]
<neg> C) None
<pinchartl> easy :-)
<pinchartl> thanks
<neg> Will also have a shorter vacation trip then uli___ from 27 Dec -- 6 Jan
      :-)
<pinchartl> I'll wish you a good vacation during the next meeting then :-)
								        [17:17]
<pinchartl> next, Morimoto-san
<morimoto> OK
<morimoto> A)  [17:18]
<morimoto> I got review from Rob about OF-graph HDMI sound. He don't like
	   current style. Now I'm discussing about it.
<morimoto> 
<morimoto> B)
<morimoto> DU side DT will have HDMI video and sound. ALSA SoC side needs to
	   know total how many HDMI sound port exist.
<morimoto> but, Rob rejected "type=" property. So, I can't know.
<morimoto> ---- from Rob ----------------
<morimoto> I still don't think this is necessary. Simply define which port
	   number
<morimoto> is which for each HDMI chip.
<morimoto> If this is necessary, then the types, video and sound, are too
	   generic.
<morimoto> ------------------------------
<morimoto> What does it mean ?? How to get this information from ALSA side ??
<morimoto> I think I need to corroborate with HDMI video ?
<morimoto> s/corroborate/collaborate  [17:19]
<morimoto> C)  [17:20]
<morimoto> I need to re-create OF-graph patches.
<morimoto> Can I use Laurent version ? I'm using Ulrich version
<morimoto> -- EOT --
<pinchartl> regarding the type property
<pinchartl> the DT bindings for each HDMI encoder define the number and type
	    of each port
<pinchartl> Rob's point is that, instead of adding a generic type property,
	    you should query the HDMI encoder driver at runtime to know the
	    number of audio ports  [17:21]
<pinchartl> I'm not sure if that's feasible though, I haven't checked how it
	    works on ALSA"s side
<morimoto> but in runtime query, how the driver know total size ?  [17:22]
<morimoto> fixed size, does it mean ?
<pinchartl> the driver knows because the driver knows the hardware
<pinchartl> it's hardcoded in the driver  [17:23]
<morimoto> OK, I see.
<pinchartl> for instance let's say we have an HDMI encoder with two sound
	    inputs, one video input and one HDMI output
<pinchartl> that's 4 ports
<pinchartl> the DT bindings would document something like
<pinchartl> port 0: video in
<pinchartl> port 1: audio 0 in
<pinchartl> port 2: audio 1 in
<pinchartl> port 3: hdmi output  [17:24]
<pinchartl> then let's imagine that the board has audio 1 in connected
<pinchartl> and audio 0 not connected
<pinchartl> DT would have port 2 connected with an endpoint
<pinchartl> and port 1 not connected, with no endpoint
<pinchartl> the driver would parse the DT node
<pinchartl> see that port 1 is not connected and port 2 is connected  [17:25]
<pinchartl> and conclude that there's one audio input in use among the two
	    possible audio inputs
<pinchartl> there's no need for a type property there
<pinchartl> the type property would only be needed if you need geenric code to
	    parse the DT node, code that has no knowledge of the device
								        [17:26]
<morimoto> So this mean we need new "query" function for it ?
<morimoto> it tell "for video port" "for sound port" or "connected", something
	   like that  [17:27]
<pinchartl> that would be the idea. again, as I'm not too familiar with ALSA's
	    internals I don't know if that would be easy, or even good
<pinchartl> but Rob's point is that code that parses the OF graph in a
	    completely generic way is usually a bad idea  [17:28]
<morimoto> OK
<pinchartl> because DT properties are defined by DT bindings in relationship
	    with the compatible strings
<pinchartl> so a generic function that walks through the OF graph, from node
	    to node, trying to collect information about each node, can't know
	    for sure what a property means  [17:29]
<morimoto> +1 question is that this mean, DU driver will have this "query"
	   function, righ ?
<pinchartl> I'm not as opposed to that as he is, but I understand his point
<pinchartl> do you mean the dw-hdmi driver ?
<morimoto> I don't know. DU has port, right ?  [17:30]
<morimoto> not dw-hdmi
*** horms (~horms@217.111.208.18) has joined channel #periperi
<pinchartl> the DU has a DT node, yes
<pinchartl> but DU doesn't handle sound
<pinchartl> the HDMI encoder DT node does  [17:31]
<morimoto> Yes, yes. DU driver only handle video side, but will have
	   video/sound port in DT.
<morimoto> This means, DU driver need to care about video/sound port, too
<pinchartl>
	    https://git.linuxtv.org/pinchartl/media.git/commit/?h=drm/du/hdmi&id=3d12f1ed444c7d38e4006d51155dfebca0bb3d22
								        [17:32]
<pinchartl> those are the DT nodes that will have audio ports
<pinchartl> they're handled by the new rcar-dw-hdmi driver
<pinchartl>
	    https://git.linuxtv.org/pinchartl/media.git/commit/?h=drm/du/hdmi&id=59115b56b8156a60b5e1d3e0077611ed403b6154
<pinchartl> which is the platform glue layer for the dw-hdmi core code  [17:33]
<morimoto> Oops, I need to rebase to it  [17:34]
<morimoto> Does renesas-driver has it ?
<pinchartl> it should, yes
<morimoto> OK.
<pinchartl> Geert told me yesterday he would merge it
<morimoto> And it is almost upstream version ?
<pinchartl> yes
<morimoto> OK  [17:35]
<pinchartl> I've posted v1 already
<pinchartl> and will post v2 soon
<pinchartl> (more about that when it will be my turn)
<morimoto> OK, I will rebase to it, and consider about query function.
<morimoto> But, 
<morimoto> HDMI will have "sound" port anyway. So video side need to care it,
	   right ?  [17:36]
<morimoto> (avoid sound port, etc..)
<pinchartl> yes it will
<morimoto> Or HDMI video/sound can share same port ?  [17:37]
<pinchartl> it should be two different ports
<morimoto> OK, nice to know
<morimoto> I will investigate it next week. thanks
<pinchartl> so we would need an API to walk the DT graph with assistance from
	    drivers
<pinchartl> you're welcome
<morimoto> I will ask about query to Rob  [17:38]
<pinchartl> I think I've answered your question about which version of the
	    HDMI patches you should use
<pinchartl> so now it's my turn :-)
<pinchartl> since last meeting  [17:39]
<pinchartl> as I said, I've posted the HDMI output on Gen3 patches
<pinchartl> Kieran and I have been working together on that
<pinchartl> we got rid of all hacks  [17:40]
<pinchartl> one of the good news is that ES1.x / ES2.0 don't need special
	    handling anymore
<morimoto> Nice
<pinchartl> the series cleans up and enhances the dw-hdmi driver
<pinchartl> I've received a few comments about that
<pinchartl> and reworked the patches accordingly  [17:41]
<pinchartl> based on information I managed to gather about the Synopsys DWC
	    HDMI TX IP core
<pinchartl> it's not easy, as there's no public datasheet from Synopsys
<pinchartl> speaking of which, I talked to one of their engineers in private
<pinchartl> he said he wasn't allowed to give me information
<pinchartl> but that, if I needed support, I should be able to get it through
	    Renesas  [17:42]
<pinchartl> he said that if Renesas contacted Synopsys' support, the question
	    would be routed to him, and he could then talk to me in direct :-)
<pinchartl> so far I managed to solve most of the problems withotu needing
	    that
<pinchartl> I've also done review, there was quite a bit of discussion about
	    the DRIF DT bindings  [17:44]
<pinchartl> no time to post a proposal for the rotation and histogram APIs yet
	    I'm afraid  [17:45]
<pinchartl> I'll try to address that in the next two weeks
<pinchartl> aV4L2 cache
<pinchartl> oops
<pinchartl> as well as starting the V4L2 cache discussion
<pinchartl> no real issue or blocker, I've been slowed down by the lack of
	    public dwc hdmi documentation, but I found a leaked datasheet and
	    gathered more information from several developers  [17:46]
<pinchartl> so at the moment it's not an issue
<pinchartl> that's it for me  [17:47]
<pinchartl> kbingham: your turn now
<kbingham> Ok :D
<kbingham> So - as per the mail I sent - I've fixed suspend resume on m2m
	   pipelines, and incorporated the fix for the BRU race I discovered
	   into this as well.  [17:48]
<kbingham> I've also written a couple of automated tests for suspend resume
	   which should make their way into vsp-tests. - It's quite neat, as
	   it uses a PM debug tool in the kernel to suspend, and then
	   automatically resume after 5 seconds.  [17:49]
<pinchartl> (bit of context for the reader, M2M pipeline refers to the VSP)
								        [17:50]
<kbingham> Ah yes - sorry - I was lacking context there :D - There are still
	   issues in the display pipeline but that is more complicated as we
	   are then dealing with making sure multiple cells suspend resume
	   cleanly I believe.  [17:51]
<pinchartl> yes, DU suspend/resume still needs work
<kbingham> Aside from that - I've done some work on HDMI with Laurent, and
	   I've been supporting Duc@Jinso to help him get a set up for testing
	   the writeback prototype I posted last month.
<kbingham> My B) section is a little 'fuzzy' at the moment, so I'll leave that
	   section blank for now :D  [17:52]
<kbingham> C) - There was a lot of time spent looking after Jinso :(  [17:53]
<kbingham> D) Show(off) and tell -
<kbingham>  - I've made an LED Christmas Tree Hat (for Xmas parties)
<kbingham>  - https://goo.gl/photos/PRyXXbpJdJbokBQ56
<pinchartl> :-D
<neg> nice
<kbingham> Speak of the devil - Duc@Jinso has just mailed me again :D  [17:54]
<pinchartl> Morimoto-san: I've sent you an e-mail regarding the support we
	    have to provide to Jinso
<morimoto> Nice hat !  [17:55]
<pinchartl> Magnus told me he would discuss it with you, tomorrow if I
	    remember correctly
<morimoto> OK, I will talk to him. 
<morimoto> Renesas side needs discuss about that ;P
<pinchartl> kbingham: what's your vacation schedule for the end of the year ?
								        [17:57]
<kbingham> ...
<kbingham> That's just what I was writing next :D
<kbingham> Or rather was going to ask about :D
<kbingham> Keri is on holiday from school from the 19th to the 3rd.  [17:58]
<kbingham> I don't necessarily need all that time as holiday - but I don't
	   think I have much work planned at the moment ...
<pinchartl> ok  [17:59]
<pinchartl> speaking of which
<kbingham> Certainly - I won't be working 23rd to 3rd probably  [18:00]
<pinchartl> Morimoto-san, you mentioned a VSP/DU performance problem reported
	    by a customer
<pinchartl> has there been any feedback on that ?
<pinchartl> it sounded quite urgent, is it something that we need to start
	    working on before January ?
<morimoto> There is no response from BSP team, at this point  [18:01]
<morimoto> let me check
<pinchartl> ok, we'll wait and see then
<kbingham> Ok - well I have plenty of work to continue getting my garage
	   office conversion :D  [18:02]
<pinchartl> :-)
<pinchartl> and speaking of winter holidays, will Renesas be operating between
	    christmas and new year ?
<kbingham> so that will keep me busy in the meanwhile.
<kbingham> pinchartl: Are you going to take a break anytime ?  [18:03]
<pinchartl> I'll be in Belgium from the 21st to the 29th  [18:04]
<pinchartl> I'll still be available 21st-23rd (minus time stuck in transport
	    on the 21st)
<pinchartl> and will take 24th-29th off  [18:05]
<morimoto> Renesas side will have winter vacation from 29th Dec - 9th Jan
<morimoto> BSP team want to know VSP/DU plan, at this point.  [18:06]
<pinchartl> the plan to fix the issue they've reported ?
<morimoto> They will explain current situation to customer, but customer want
	   to know its plan
<morimoto> Yes
<pinchartl> we can either start working on it in 2017/Q1  [18:07]
<pinchartl> or, if it's urgent, Kieran could start investigating it in
	    December already
<horms> morimoto: are those dates inclusive or exclusive?
<pinchartl> but we'll need an additional task for him
<morimoto> horms: sorry, what do you mean ?  [18:08]
<horms> do you start holiday on Friday or Saturday?
<horms> Do you finish holiday on Sunday or Monday?
<pinchartl> horms: the 29th is actually a Thursday
<horms> ok, sorry  [18:09]
<horms> its not so important in any case
<pinchartl> no worries, calendars are confusing :-)
<morimoto> BSP team is thinkingl  [18:10]
<morimoto> oops
<morimoto> BSP team is thinking that they can get some kind of result from
	   upstream January - March  [18:11]
<morimoto> Is it possible, do you think ?
<pinchartl> that works for me
<morimoto> OK, so Kieran can spend relax Christmas :)  [18:12]
<pinchartl> :-)
<kbingham> morimoto: I'm not sure the words 'relax' and 'christmas' go
	   together anymore :S
<kbingham> but yes :D
<morimoto> sorry for my English  [18:13]
<neg> kbingham: that's why I go to the caribbeans and drink rum, I will be
      relaxed :-)
<kbingham> morimoto: No your english was fine :D
<kbingham> neg: Got any room in your luggage to pack me ?
<morimoto> horms: Renesas last working day is 28th, and holiday started from
	   29th
<horms> thanks  [18:14]
<morimoto> horms: last holiday is 9th, start works from 10th. Is this clear ?
<pinchartl> morimoto: very clear, thanks
<pinchartl> next topic, FOSDEM
<horms> very clear, thanks
<pinchartl> Morimoto-san will unfortunately not be able to join us  [18:15]
<morimoto> horms: np
<pinchartl> has there been a confirmation that a core meeting will be held on
	    Friday the 3rd of February ?
<horms> I think that is more or less confirmed
<pinchartl> ok
<horms> geertu: ?
<geertu> horms: yes?  [18:16]
<horms> geertu: is f2f core meeting on 3rd Feb confirmed?
<geertu> horms: If Laurent and Magnus join, we are 6 persons.  [18:17]
<geertu> which is critical mass, I believe? So yes
<pinchartl> I'll be there
<morimoto> Magnus said he arrive at Feb 3th  [18:18]
<morimoto> Feb 3rd afternoon
<pinchartl> ok
<morimoto> afternoon = 16:05  [18:19]
<geertu> Hmmm...
<geertu> He also said he might change his plane
<kbingham> geertu: I'll likely be there by then regardless - so I might join
	   you for somewhere to keep warm :D
<kbingham> If I'm not wanted - I'll explore brussels :)  [18:20]
<geertu> Will there be an MM meeting on Thursday?
<pinchartl> at this point there's no formal plan for a multimedia meeting, but
	    I've booked the afternoon of February the 2nd nonetheless
<kbingham> Brussels?
<geertu> Or will it just ve I/O and Core on Friday?
<pinchartl> if you're in Brussels, I'm sure we won't run out of multimedia
	    topics to discuss
<pinchartl> next topic, next meeting  [18:22]
<pinchartl> I propose two weeks from now
<pinchartl> on the 21st
<pinchartl> Ulrich is already excused as he will be on holidays
<neg> 21st works for me
<pinchartl> uli___: but please report your progress by e-mail before leaving
								        [18:23]
<morimoto> 21st doesn't works for me :(
<uli___> ok
<pinchartl> morimoto: we can move it to Tuesday or Thursday
<morimoto> 20th, 22th are OK
<geertu> Core meeting on Dec 20th?  [18:24]
<geertu> (still have to complete the report and mail it out)
<pinchartl> there's the core meeting on Tuesday already. we can have the
	    multimedia meeting after core, but it will be late for you
<pinchartl> so maybe 22nd then ?
<morimoto> 22nd is OK for me  [18:25]
<pinchartl> 22nd then. same time, 08:00 GMT / 09:00 CET / 10:00 EET / 17:00
	    JST
<morimoto> Thanks. I booked  [18:26]
<pinchartl> and that's all we have on the agenda for today. I propose
	    adjourning the meeting, does anyone second ?
<kbingham> I'll skip to thirded :D
<uli___> fourthed
<pinchartl> thank you all for attending  [18:27]
<pinchartl> and have a nice day or evening
<kbingham> Cheers all !
<neg> thanks all
<morimoto> Thanks!