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

Multimedia-chat-meeting-2017-03-28

<morimoto> Hi
<morimoto> sorry for my late
<pinchartl> hi Morimoto-san  [16:02]
<pinchartl> no worries
<morimoto> (I will post my list soon by email)
<pinchartl> it's my fault, I should have thought about DST when we scheduled
	    this meeting  [16:03]
<pinchartl> so let's get started and hope that Jacopo will show up
<pinchartl> topics for today are  [16:04]
<pinchartl> Topic 1. Status check for the multimedia tasks
<pinchartl> Topic 2. Multimedia plan (related to VIN development)
<pinchartl> Topic 3. Meeting around LinuxCon Japan  [16:05]
<pinchartl> Topic 4. Next meeting
<pinchartl> anything else ?
<jmondi> pinchartl: yes I am... got confused with time zone switch  [16:06]
<pinchartl> no worries
<pinchartl> Topic 1. Status check for the multimedia tasks  [16:07]
<pinchartl> let's go in reverse alphabetical order to give Jacopo a few
	    minutes to wake up  [16:08]
<pinchartl> uli___: you're first
* kbingham back
<uli___> so i have a max9286/9271/ov10635 driver combo that has a chance of
	 actually doing something
<uli___> not yet checked if it actually does
<uli___> and the mt8137 chromebook embedded controller is connected to the soc
	 via spi  [16:09]
<uli___> not trivial to set up without a kernel
<uli___> that's a); nothing to report for b) c) d)  [16:10]
<pinchartl> you don't plan to do any work for the next two weeks ? :-)
<uli___> well, tbd
<uli___> no concrete plans yet
<uli___> i might test the driver works, i guess :)  [16:11]
<dammsan> we sort of depend on the outcome of the max/ov combo prototype...
<pinchartl> a bit more than *sort of* actually
<dammsan> =)
<pinchartl> it's very high priority
<pinchartl> so could you please elaborate on what has been done and what is
	    left to be done ?  [16:12]
<pinchartl> and why the code couldn't be tested yet ?
<uli___> like i wrote in the e-mail, it probes, media-ctl says everything is
	 fine
<uli___> it's not tested yet because i finished it yesterday
<dammsan> uli___: i think the power controller bits should be sorted since
	  some time ago  [16:13]
<dammsan> can you access devices over I2C?
<pinchartl> the power controller bits ?
<dammsan> apparently a second power adapter was needed for the board  [16:14]
<dammsan> it was not provided with the board from the beginning
<uli___> the devices are there
* morimoto Renesas inside talk
<dammsan> present devices is an improvement i think
<pinchartl> dammsan: do you mean the MAX9286 board ?
<dammsan> i don't even know the name of the board
<dammsan> the hardware i received from morimoto-san  [16:15]
<dammsan> the daughter board for salvator-x
<dammsan> with tons of camera connections
<pinchartl> yes
<pinchartl> so now you have hooked up a power supply to that board ?
<dammsan> since some time ago
<dammsan> maybe about 2 weeks ago
<dammsan> the hardware should be fine now at least  [16:16]
<dammsan> (what i can tell)
<dammsan> so if the I2C devices are present
<dammsan> then there is no need for the r8a7792 blanche backup plan?  [16:17]
<pinchartl> I see power connectors in the schematics indeed
<uli___> dammsan: not for my point of view. but what exactly is the r8a7792
	 backup plan?
<dammsan> i hooked up an unknown camera to the r8a7792 blanche board some time
	  ago  [16:18]
* morimoto back
<dammsan> i kind of wanted to see if some devices showed up on I2C there too
<pinchartl> uli___: you mentioned in your e-mail that you ported two drivers,
	    one from Cogent, one from the BSP  [16:19]
<uli___> yes
<pinchartl> and that our hardware is quite different from what the first
	    driver support
<pinchartl> how so ?
<uli___> our hardware is connected like so:
<uli___> soc <=i2c= max9286 <=i2c= max9271 <=i2c= ov10635  [16:20]
<uli___> they support various boards, but they all have more than one chip
	 connected directly to the soc
<uli___> some have an i2c multiplexer  [16:21]
<uli___> but none are in a straight line like ours
<pinchartl> they don't support that hardware setup ? what kind of hardware
	    setup do they support ?
<uli___> i think somewhere in their pile of patches there is the code from the
	 renesas bsp as well  [16:22]
<uli___> they support boards called "kingfisher" and "view", and an unnamed
	 board i think
<pinchartl> so they have no direct support for our hardware platform, and
	    while it might not be too difficult to fix that, you decided to
	    use the BSP code instead ?  [16:23]
<uli___> i was a bit pressed for time, and the bsp code is written for this
	 platform...  [16:24]
<neg> where do they have the i2c multiplexer in ther setup, between the SoC
      and MAX9286 chip(s)?
<pinchartl> I'm not complaining :) I'm just trying to make sure I understand
	    the situation correctly
<uli___> neg: i don't remember, i would have to look up the DT  [16:25]
<neg> Me too, I think it's awesome you got that code working with the VIN
      dirver. When I looked at that code I felt sick :-)
<neg> uli___: OK np I was just curious how it differd
<uli___> it's a pca9somethingsomething, and it's connected to the soc
<uli___> i guess they packed everything in one driver because a proper
	 implementation would need two additional i2c host drivers...
								        [16:26]
<pinchartl> yes
<pinchartl> uli___: so, when do you think you'll be able to test the code ?
<pinchartl> and, more importantly, get it to work :-)  [16:27]
<uli___> test, today or tomorrow i guess. get it to work, hmmm... :)
<pinchartl> I would really appreciate if you could provide the first test
	    results today  [16:28]
<pinchartl> I'll sleep better (or worse...) tonight
<uli___> i'll see what it does later  [16:29]
<pinchartl> thank you
<pinchartl> you can send a quick e-mail to update us
<uli___> ok
<pinchartl> if everything works I'll be very happy
<pinchartl> if that's not the case, please try to describe what the problem(s)
	    are with as much information as possible  [16:30]
<pinchartl> I'm sure Niklas can assist you with any VIN issue
<neg> sure can
<pinchartl> neg: you're next :-)  [16:32]
<neg> a) Posted two VIN series '[PATCH 00/16] rcar-vin: fix issues with format
      and capturing' and '[PATCH v3 00/27] rcar-vin: Add Gen3 with media
      controller support'
<neg> b) Act on reviews on the posted series and try to take a stab at
      extending the of graph framework to be able to iterate over all DT nodes
      in a graph connected by endpoints.
<neg> c) None
<neg> d) None
<neg> if someone got review time please look at the first series as it should
      be simpler to review and fixes real issues and the second one depends on
      it. Also it would feel good to finaly get some VIN work merged :-)
								        [16:33]
<neg> ooh also in b) I will fixupo a few things for the CSI-2 driver and
      repost it  [16:34]
<neg> --EOT--
<pinchartl> thank you
<pinchartl> do you feel you're on track schedule-wise ?
<neg> Yes I hope so, there are still some work to be done in the are to be
      able to find, and then use the async framework to create all media
      controller links for arbitrary long device chains which needs to be
      sorted  [16:36]
<pinchartl> ok  [16:37]
<neg> problem is as we talked shortly about your holiday is how to best relay
      information about pads from DT to MC
<neg> but I imagine some work is needed there in the task to fix  ADV7482
      multiple subdevices  [16:38]
<pinchartl> yes
<pinchartl> that's one of the nasty missing pieces
<pinchartl> have you discussed that with anyone while I was away ?
<neg> so I currently focus on exteding of graph to provied helpers to find all
      DT nodes since this will be needed however the port->pad thing is solved
      and it would also be used later by the device allocator API  [16:39]
<neg> no I have not presude it further as the discussion with Russel King
      about MC in general I feelt safer to let it cool of a bit before trying
      to attack that issue
<pinchartl> I'll add the port->pad mapping to your list of issues  [16:40]
<neg> thanks
<pinchartl> morimoto: you're next  [16:42]
<neg> I know you must have a huge mail backlog but maybe sometime next week
      you and I (and anyone else interessed ofc) can have a short chat about
      it, I feel a bit lost on how to best think about the problem
<morimoto> OK
<pinchartl> neg: sure. early next week would be best for me
<kbingham> There is rumour I will be looking at some ADV7482 work based on the
	   chat log from the last meeting - so let me know when you have the
	   chat :)
<neg> thanks, I can ping you and kbingham monday then and see when would be
      convinient, thanks  [16:43]
* morimoto let me know if I can start ;P
<pinchartl> morimoto: please go ahead :-)
<morimoto> Hehe :O
<morimoto> s/:O/:)/
<morimoto> A)
<morimoto> o I posted OF-graph patchset again, no response  [16:44]
<morimoto> o Hacking for Sound driver bug fix
<morimoto> o Hacking for bind/unbind issue for ALSA SoC
<morimoto> o I could contact to OV guys, and discuss about OV camera
	   datasheet.
<morimoto> I sent you that you can receive datasheet from OmniVision, but you
	   can call me liar.
<morimoto> Final conclusion is that I need to export it to you. and it will
	   takes not short term.
<morimoto> o I asked you guys about camera board power cable, on
<morimoto> Subject: Re: CSI2 multiple subdevices development
<morimoto> Date: Wed, 22 Mar 2017 09:18:44 +0900
<morimoto> B)  [16:45]
<morimoto> o DT maintainer response is too slow
<morimoto> o I'm very x10 sad (;_;), because no response from MultiMedia group
	   leader (= holiday guy) for camera board cable ;P
<morimoto> C)
<morimoto> o Continue hacking for sound driver/framework
<pinchartl> :-)
<morimoto> o OV camera export paper work
<morimoto> --EOF--
<pinchartl> thank you  [16:46]
<pinchartl> so what's the situation with the OV datasheet ? do you have it ?
<morimoto> Now I have it
<morimoto> But I need to export paper work
<morimoto> (In secret, Maybe I can put it on Redmine)  [16:47]
<morimoto>
	   https://osdr.renesas.com/projects/linux-kernel-development/wiki/Salvator-X_MAXIM_camera_board
<morimoto> (not yet)
<pinchartl> regardless of how we transfer the datasheet, it will be covered by
	    our NDA, so that part is fine
<morimoto> Yes  [16:48]
<pinchartl> regarding the camera board cable  [16:49]
<pinchartl> what's the issue ? :-)
<morimoto> issue is that whether you can use existing power cable or not
								        [16:51]
<morimoto> if not, I need to export power cable, but it needs more paper work
<pinchartl> let me quickly check
<morimoto> You can use Lager/Koelsh/Salvator power cable
<pinchartl> is that a regular 12V power supply with a barrel connector ?
								        [16:52]
<morimoto> Do you mean Lager/Koelsh/Salvator power cable ? then yes
<geertu> (2.1/5.5mm center positive)  [16:53]
<pinchartl> that's easy to source
<pinchartl> no need to send them from Japan
<morimoto> Nice !!
<pinchartl> we can order power supply pretty much anywhere if needed, that
	    will be much faster  [16:54]
<morimoto> You saved me !!
<neg> In the email you also state two power cables could be used right? One to
      Salvator-X and one to the Camera board and as long as you already have
      two Gen2/Gen3 power cables you are ok
<morimoto> neg: Yes
<morimoto> 1 note is that camera board doesn't have reset button  [16:55]
<morimoto> You need to plug out/in for reset camera board :P
<morimoto> I think above url has such explanation
<pinchartl> do you know if the salvator-x and camera boards can be powered up
	    in any order, or is a specific order required to avoid damaging
	    the hardware ?  [16:56]
<morimoto> Yes, it has special order. you can check it on above URL
<morimoto> see. Power ON order  [16:57]
<pinchartl> thanks
<morimoto> And special know-how for jumper pin, too
<pinchartl> thank you  [16:58]
<pinchartl> dammsan: you're next
<dammsan> nothing to report here really
<dammsan> just sent out an email regarding V2H and serial multiplexing  [16:59]
<dammsan> not sure if it made it to periperi or not with the large size photo
	  of schematic
<dammsan> this is related to "plan b" in case ulrich can't get it going
<dammsan> apart from that nothing to report  [17:00]
<pinchartl> thank you  [17:01]
<pinchartl> I'm next  [17:02]
<pinchartl> I've been on holidays for two weeks, so not much to report
<pinchartl> my short term plan is catching up with my e-mail backlogs and with
	    patch reviews
<pinchartl> kbingham: you're next  [17:03]
<kbingham> Ack!
<kbingham> Nothing to report since last time, I've been working on other
	   projects as my Renesas budget was empty.
<kbingham> In the upcoming weeks, I expect that to replenish, and will be
	   getting my existing series' rebased and following up on review
	   comments.
<kbingham> I have a small support task for jinzai which should be solving
	   today, and then I will be following whatever the latest plan is on
	   our multimedia task force.
<kbingham> The notes from the last meeting suggest that I will be looking at
	   the ADV7482 sometime, but I don't know any further details about
	   this planned work yet.
<kbingham> -- EOT --  [17:04]
<pinchartl> thank you  [17:05]
<kbingham> Any comments? Is the ADV7482 still my task in the plan?
<pinchartl> yes
<pinchartl> I propose discussing it with Niklas early next week  [17:06]
<kbingham> I was about to say the same :D
<pinchartl> Monday morning or Tuesday would work best for me
<kbingham> Tuesday is better for me ...
<kbingham> But I can do monday.
<pinchartl> neg: how about you?
<neg> both work for me
<kbingham> oh wait
<kbingham> Actually I think Tuesday might be bad for me :)
* kbingham checks
<kbingham> I have to go out at 10am on Tuesday, so Monday is better :)  [17:07]
<neg> so standard meeting time monday morning?
<kbingham> Can we make it 9am UK time :)  [17:08]
<pinchartl> works for me
<neg> sure
<kbingham> great.
<pinchartl> I've sent you an invitation  [17:09]
<kbingham> Received.  [17:10]
<pinchartl> jmondi: you're next (and last)
<jmondi> thanks!  [17:11]
<jmondi> few things to report since last time
<jmondi> I only spent 1 week of my time on multimedia, and I have ported the
	 DRM/KMS test application to gen 3
<jmondi> not tested with VIN patches yet
<jmondi> but I have closed pinchartl review comments on last version  [17:12]
<jmondi> I should send out an email with details probably...
<pinchartl> that would be nice
<jmondi> apart from that not much, still waiting to have a more defined plan
	 for next months, where I should be all about multimedia
<pinchartl> thank you  [17:13]
<jmondi> I guess the OV datasheet export issue has impact on me, as I was
	 supposed to work on ov10(don't remember name) sensor, right?
<pinchartl> correct  [17:14]
<pinchartl> morimoto: maybe the datasheet should appear magically on a server
	    somewhere
<pinchartl> nobody will know where it came from  [17:15]
<pinchartl> and nobody will ask any question
<jmondi> for just a few minutes maybe?
<pinchartl> life will be good, everybody will be happy
<morimoto> pinchartl: actually, it will takes long term for export  [17:16]
<morimoto> but, I can put it on Redmine if I can be guilty guy  [17:17]
<pinchartl> nobody will tell :-)
<morimoto> Hehe :)
<morimoto> jmondi: when do you need it ? immediately ?  [17:18]
<jmondi> morimoto: the sooner the better
<morimoto> OK...
<jmondi> since we're both online, you can upload and delete in 5 minutes
<morimoto> Please pray that no stone-head guys come here :)
<pinchartl> there's usually an application note that goes with the OV sensors
	    datasheets
<pinchartl> if you have to too, it would be nice to get it
<morimoto> It will be formal, but not yet now
* kbingham grabbed a copy to see too :)  [17:22]
<pinchartl> no problem
<morimoto> I only have datasheets, not application note
<pinchartl> that closes the first topic
<pinchartl> Topic 2. Multimedia plan
<morimoto> If you need it, I can ask to OmniVision guy
<pinchartl> dammsan: what's the status of base contracts and additional tasks
	    for Q2 ?
<pinchartl> morimoto: it would be nice to get it, the datasheet usually lacks
	    important information that is present in the application note
<morimoto> pinchartl: OK, will do  [17:23]
<morimoto> neg: I will delete datasheet, are you OK ?
<neg> yes  [17:24]
<neg> thanks, and what datasheet :-)
<dammsan> pinchartl: the base tasks have been submitted, waiting for
	  processing  [17:25]
<dammsan> additional tasks
<pinchartl> do you expect any issue or delay for the base tasks ?
<dammsan> not really
<dammsan> i think the only unknown is that camera prototype at this point
* morimoto bye-bye datasheet  [17:26]
<dammsan> i expect base tasks to be ready this week
<pinchartl> ok
<pinchartl> how about the additional tasks ?  [17:27]
<dammsan> i think your idea with the shared more generic task description is
	  good
<dammsan> so i would like to proceed with that  [17:28]
<dammsan> however, i would like to know that we at least have _something_ that
	  works first
<pinchartl> uli___: I think there's a bit of pressure on you :-)  [17:29]
<dammsan> from my side, we can be blocked on several other random issues
	  before we get there
<pinchartl> but in any case we have to go in that direction
<dammsan> (who knows, another power supply needed or perhaps some jumper is
	  missing)
<pinchartl> which is why I want more generic tasks  [17:30]
<pinchartl> to handle the issues as we progress
<dammsan> sure
<dammsan> i mainly want results myself =)
<pinchartl> have you submitted the generic task proposal internally to Renesas
	    to get their feedback ?  [17:31]
<dammsan> nope
<dammsan> we've been busy with base tasks
<pinchartl> Q2 starts next week, and I think everybody is getting nervous
								        [17:32]
<dammsan> this is why we have the base tasks
<dammsan> i would have preferred to have overlapping ones myself
<dammsan> but hey
<pinchartl> how would you like to proceed ?
<dammsan> i want to get the updated result from the camera prototype  [17:33]
<dammsan> i propose that we revisit next week, hopefully some update is
	  available then?
<dammsan> that should have sorted out the base tasks too
<pinchartl> ok  [17:34]
<pinchartl> by the way
<pinchartl> morimoto: what's the status about the hardware setup that should
	    be sent to Europe ?  [17:35]
<dammsan> in the mean time, lets do ping-pong-email you and me in case some
	  detail need to be adjusted in the additional task descripiton
<morimoto> pinchartl: camera board ?  [17:36]
<pinchartl> morimoto: yes  [17:37]
<morimoto> camera *board* I already have
<morimoto> camera itself will be arrive at 5
<morimoto> 5 = May
<pinchartl> at 5 ? 5pm today ? :-)
<pinchartl> ok
<uli___> 5pm in may
<pinchartl> when in May ?
<morimoto> Hehe
<morimoto> Don't know, just "May"  [17:38]
<pinchartl> so potentially we won't have access to local hardware before end
	    of May ?
<morimoto> Unfortunately
<jmondi> we can pick them at LCJ directly :/  [17:39]
<pinchartl> ok
<morimoto> jmondi: Unfortunately, it is not allowed
<pinchartl> that's not very nice, but we have no choice
<pinchartl> how comes the camera will arrive so late ? is it because of the
	    lead time from the manufacturer ?
<morimoto> I'm not sure, I know is that it will came from Philippine  [17:40]
<pinchartl> who's the manufacturer ? do you have a model number ?  [17:41]
<morimoto> Module name is "RDACM20-01"  [17:42]
<pinchartl> thank you
<morimoto> manufacturer seems... IMI Japan  [17:43]
<pinchartl> I don't think it makes sense to really update the multimedia plan
	    at this point before we have results from Ulrich's work
								        [17:45]
<pinchartl> uli___: is there any way we can help to speed it up ?
<uli___> during this meeting i have received an e-mail from my tax guy, who
	 has failed to do my taxes for 2015, which are at the absolute latest
	 due tomorrow, until now  [17:46]
<uli___> i need to look up some documents
<geertu> http://www.global-imi.com/about-imi/global-facilities/ does not list
	 Japan.  But it does list Czech Republic and Bulgaria
<uli___> i'm afraid that has 110% priority
<uli___> i'll still try to do the test today, though
<pinchartl> uli___: let's discuss the results tomorrow morning then  [17:47]
<uli___> ok
<pinchartl> Topic 3. Meeting around LinuxCon Japan  [17:48]
<pinchartl> we have agreed on dates for the trip  [17:49]
<pinchartl> with a VIN code camp with local hardware access on the 29th and
	    30th of May
<pinchartl> so far no meeting with the BSP team is scheduled, as no need to
	    have such a meeting has been expressed  [17:50]
<pinchartl> morimoto: dammsan: does that still hold ? or do you think we
	    should organize a meeting ?
<morimoto> pinchartl: no plan with BSP team meeting at this point.  [17:51]
<dammsan> pincharl: we should go out for drinks together at least =)  [17:52]
<pinchartl> dammsan: of course :-)
<pinchartl> I'd like to spend as much time coding as possible  [17:53]
<pinchartl> so if meetings are needed, I'd like to know ASAP
<dammsan> makes sense
<neg> I would also like to book my trip soonish :-)
* jmondi too ^  [17:54]
<kbingham> Yes, flights have increased in price by 30% already here I think.
<kbingham> (google keeps telling me when the price changes)
<kbingham> Of course that could just be because the £ has decreased in value
	   :)  [17:55]
<neg> I think I managed to clear my previous date troubles so I should be
      avaliable from/to both weekends before and after and be happy to stay
      both if other ppl are around for code or drinking sessions ;-)
<pinchartl> neg: \o/
<jmondi> neg: you're talking about the May 27th/28th weekend and June 3rd/4th,
	 right?  [17:56]
<pinchartl> morimoto: persmission to book flights then ?
<kbingham> I can do before much easier than after :)  [17:57]
<neg> jmondi: yes
<morimoto> pinchartl: sorry, what do you mean?
<pinchartl> morimoto: can we go ahead and book flights for the week in Japan ?
	    and can we invoice them to Jinso ?  [17:58]
<morimoto> Ahh, OK. I will ask to our boss, please wait
<pinchartl> thank you  [18:00]
<pinchartl> last topic, next meeting
<pinchartl> I propose two weeks from now  [18:01]
<pinchartl> Tuesday the 11th of April
<jmondi> works for me I guess
<pinchartl> at 8:00 GMT / 09:00 CEST / 10:00 EEST / 16:00 JST
<pinchartl> (usual time)
<dammsan> sounds good
<kbingham> Ack here.  [18:02]
<pinchartl> good, I'll send the invite now
<morimoto> pinchartl: how many people caming to Japan ?
<pinchartl> morimoto: Ulrich can't make it, so that would be Jacopo, Kieran,
	    Niklas and me
<morimoto> And Core/IO group member ?  [18:03]
<neg> date works for me
<geertu> pinchartl: You really want to conflict with all future Core Meetings?
<pinchartl> morimoto: I don't know about Gert or Wolfram's plans for LCJ
<pinchartl> geertu: good point
<pinchartl> should we make it Wednesday the 12th ?
<geertu> pinchartl: What happened with the MM meetings on Wednesdays?
<pinchartl> geertu: lack of sleep I think :-)  [18:04]
<pinchartl> we've switched this week, but let's go back to the original
	    schedule
<pinchartl> so Wednesday the 12th
<pinchartl> at 8:00 GMT / 09:00 CEST / 10:00 EEST / 16:00 JST
<dammsan> gotcha  [18:05]
<pinchartl> I propose closing this meeting
<pinchartl> does anyone second?
<geertu> pinchartl: Thank you!
<morimoto> pinchartl: about trip budget, maybe OK 
<pinchartl> geertu: you're welcome
<morimoto> pinchartl: about 4/12 2nd  [18:06]
<pinchartl> 4/12 2nd ?
<morimoto> s/2nd/second/
<morimoto> I mean OK for 4/12 meeting  [18:07]
<pinchartl> :-)
<kbingham> 4th December is a bit late :D
<pinchartl> perfect
<pinchartl> thank you all for attending
<pinchartl> and have a nice day
<kbingham> Cheers all
<neg> thanks all
<morimoto> kbingham: oops, 4/12 = 4th December in Europe, it is April, 12th in
	   Japan ;P  [18:08]
<jmondi> cheers! see you
<morimoto> thanks