Merge remote-tracking branch 'gitlab/wiki' into HEAD

1 files changed, 581 insertions, 0 deletions

diff --git a/wiki/Chat_log/20160706-mm-chatlog b/wiki/Chat_log/20160706-mm-chatlog
new file mode 100644
index 0000000..5d1544a
--- /dev/null
+++ b/wiki/Chat_log/20160706-mm-chatlog
@@ -0,0 +1,581 @@
+Chat Report 2016-07-06
+
+We had a multimedia group meeting on 2016-07-06. Here's a summary of the 
+discussions. Please correct any mistake you would notice.
+
+Attendees:
+
+- Kieran
+- Laurent
+- Morimoto-san
+- Niklas
+- Ulrich
+
+Magnus was excused.
+
+
+Topic 1. Status check for the multimedia tasks
+----------------------------------------------
+
+- FDP,v4.8,prototype,kieran,Develop and upstream driver
+
+Patches have been posted for public review, DT bindings have been acked. 
+Development itself is complete, the task will be split in two with only the 
+upstreaming part remaining. The upstreaming target is v4.9.
+
+- AUDIO-DMAC,?,plan,magnus,IPMMU integration on Gen2
+- AUDIO-DMAC,?,plan,magnus,IPMMU integration on Gen3
+- AUDIO-DMAC,?,plan,magnus,IPMMU support on Gen2
+- AUDIO-DMAC,?,plan,magnus,IPMMU support on Gen3
+- VIN,?,prototype,magnus,IPMMU integration on Gen2
+- VIN,?,prototype,magnus,IPMMU integration on Gen3
+- VIN,?,prototype,magnus,IPMMU support on Gen2
+- VIN,?,prototype,magnus,IPMMU support on Gen3
+
+No progress.
+
+- RSND,v4.10,public,morimoto,DT bindings for graph sound
+- RSND,v4.10,public,morimoto,dw-hdmi-i2s-audio prototype on Gen3
+- RSND,v4.10,prototype,morimoto,HDMI SSI prototype on Gen3
+- RSND,v4.10,plan,morimoto,HDMI sound Upstream support without hotplug on Gen2
+- RSND,2016-09-30,plan,morimoto,Hotplug support upstream on Gen3
+
+The ALSA + HDMI patches are organized as follows.
+
+1. Cleanup
+2. OF graph
+3. OF graph-based new sound card
+4. HDMI sound driver
+
+Patches for 1. and 2. have been posted. Cleanup is progressing slowly. OF 
+graph DT bindings (2) have passed maintainer's review, but the implementation 
+(3) is required before the patches can be merged.
+
+DT bindings will also be discussed during PeriPeriCon.
+
+- ADV7482,v4.7,public,niklas,Prototype on Gen3
+- VIN,v4.7,public,niklas,CSI2 prototype (Gen3)
+
+The tasks are complete.
+
+- ADV7482,v4.9,plan,niklas,Gen3 support upstream
+- ADV7482,v4.9,plan,niklas,Interlace support upstream
+- VIN,v4.9,plan,niklas,CSI2 interlace support upstream (Gen3)
+- VIN,v4.9,plan,niklas,CSI2 support upstream (Gen3)
+- VIN,v4.9,plan,niklas,Gen3 support upstream (without CSI-2)
+
+No progress.
+
+- VIN,v4.8,public,niklas,Gen3 support
+
+No progress. Upstreaming requires deciding how to handle the ADV7482, moving 
+the task to v4.9 as a result.
+
+- VIN,v4.8,plan,niklas,Scaler support (on Gen3)
+
+No progress. A prototype will hopefully be implemented before PeriPeriCon. 
+Moving to v4.9 for upstreaming.
+
+- DU,v4.7,plan,ulrich,Atomic API test program
+- DU,v4.7,prototype,ulrich,Test setup with HDMI output to HDMI input loopback 
+(without EDID)
+
+The test application and setup are public, marking as complete.
+
+- DU,v4.7,public,ulrich,HDMI output on Gen3 prototype
+
+The prototype is public, marking as complete.
+
+- DU,v4.7,public,ulrich,EDID generation support for the HDMI loopback test 
+setup
+
+Patches will be posted today.
+
+- DU,v4.9,plan,ulrich,HDMI output on Gen3 upstream
+
+No progress.
+
+- VIN,v4.8,public,ulrich,Add DV timings support to rcar-vin
+
+The patches have been merged to the linux-media tree, they should end up in 
+v4.8. Marking as complete.
+
+- DU,?,plan,laurent,IPMMU integration on Gen3
+- DU,?,plan,laurent,IPMMU support on Gen3 (through VSPD+FCP)
+- DU,v4.9,plan,laurent,Fix 3 planes formats
+- VSP,?,plan,laurent,Fixed alpha support (VI6_DPR_*_ROUTE.FXA)
+
+No progress.
+
+- VSP,?,plan,laurent,UDS regression fix
+
+UDS on Gen3 can scale images wider than 128 or 256 pixels. It requires slicing 
+(partitioning) input images in software and running the VSP pipeline for each 
+slice. Renaming the task to "Image partitioning support". This will require a 
+significant amount of work. There's no completion estimate as the task hasn't 
+been scheduled yet.
+
+- VSP,v4.8,plan,laurent,Fix suspend/resume crash
+
+No progress. The task isn't scheduled, removing the target version.
+
+- VSP,v4.8,public,laurent,HGO operation mode selection
+- VSP,v4.8,public,laurent,HGO support upstream on Gen3
+- VSP,v4.8,public,laurent,HGO test application
+
+No progress. A pull request will hopefully be sent this week, but this will be 
+too late for v4.8. Moving to v4.9 as a result.
+
+- VSP,v4.8,prototype,laurent,Rotation support
+
+Rotation itself is implemented, but requires image partitioning support for 
+images wider than 256 pixels. Removing the target version due to the 
+dependency.
+
+- VSP,v4.8,public,laurent,V4L2 request API usable prototype
+
+Patches should go out today.
+
+- VSP,?,prototype,laurent,V4L2 request API upstream
+
+No progress.
+
+
+Topic 2. Additional '50%' tasks (June)
+--------------------------------------
+
+The additional tasks are
+
+- VIN CSI-2 Support Prototype
+- ADV7482 Driver Prototype
+- VSP CLU Improvements
+- VSP Rotation Support
+- HDMI Input/Output Loopback for R-Car Gen2
+- FDP Support on Gen3
+
+All tasks are complete, with a caveat for rotation support that requires image 
+partitioning for images wider than 256 pixels. Rotation will automatically 
+work for wider images once image partitioning is implemented.
+
+
+Topic 3. Additional '50%' tasks (Q3)
+------------------------------------
+
+Due to unforeseen and sad circumstances that required Magnus to travel to 
+Sweden negotiation of the tasks got delayed.
+
+The two tasks currently planned for Ulrich are
+
+- VIN HDMI input EDID
+- VIN integration on Gen2
+
+For Niklas we have initially discussed the UDS regression fix, but as it turns 
+out it will require more work than expected it wasn't a good match. The 
+current plan is to implement support for one of the currently unimplemented 
+VSP modules. The SHP (sharpener) was mentioned but the hardware isn't fully 
+documented and the available source code just programs registers with 
+parameters passed by upper software layers that are not available to us.
+We will thus likely switch to a different module.
+
+
+Topic 4. PeriPeriCon & RenesasCon preparation
+---------------------------------------------
+
+Topics proposed for PeriPeriCon are
+
+- OF graph for ALSA (Morimoto-san)
+- V4L2 support for subdevices with more than one output pipeline (Niklas)
+- Second batch of additional tasks for Q3 (Laurent)
+- What are we doing right or wrong, and how can we improve (Laurent)
+- Long-term roadmap (Laurent)
+
+The topic owners should prepare a very short presentation when appropriate to 
+quickstart the discussion and get everybody on the same page.
+
+The https://osdr.renesas.com/projects/linux-kernel-development/wiki#PeriPeriCon wiki page contains more information about the 
+PeriPeriCon schedule.
+
+
+Topic 5. Next meeting
+---------------------
+
+The next meeting will be held at PeriPeriCon on Monday the 11th of July. The 
+next IRC meeting will be held on 2016-07-27 at 09:00 BST / 10:00 CEST / 11:00 
+EEST / 17:00 JST.
+
+
+h1. Multimedia-chat-meeting-2016-07-06
+
+
+<neg> hi all  [16:54]
+<morimoto> hi  [16:55]
+<pinchartl> hello  [16:56]
+<uli___> hi
+<pinchartl> I assume Magnus will not joing us
+<kbingham> Morning all!
+<pinchartl> let's get started  [16:58]
+<pinchartl> agenda for today
+<pinchartl> Topic 1. Status check for the multimedia tasks
+<pinchartl> Topic 2. Additional '50%' tasks (June)
+<pinchartl> Topic 3. Additional '50%' tasks (Q3)  [16:59]
+<pinchartl> Topic 4. PeriPeriCon & RenesasCon preparation
+<pinchartl> Topic 5. Next meeting
+<pinchartl> anything else ?
+<morimoto> nothing from me ;P  [17:00]
+<pinchartl> ok
+<pinchartl> let me take the tasks list
+<pinchartl> in alphabetical order  [17:02]
+<pinchartl> FDP,v4.8,prototype,kieran,Develop and upstream driver
+<pinchartl> I believe the driver was posted for public review
+<kbingham> Patches all out for review.
+<kbingham> Yes, the dt-bindings look like they've been acked, and simon has
+	   acknowledged and will pick those I believe.  [17:03]
+<pinchartl> I've reviewed a previous version of the patches and they look
+	    pretty good to me
+<kbingham> For the FDP1 driver, I would say we're just waiting for some review
+	   to happen on the linux-media lists.
+<pinchartl> I'll review the public version too
+<pinchartl> the corresponding task didn't include upstreaming, so it's
+	    complete  [17:04]
+<pinchartl> I propose splitting this item in two
+<pinchartl> development and upstreaming
+<pinchartl> and marking development as complete  [17:05]
+<kbingham> Ok. Sounds good to me.
+<pinchartl> v4.8 will be a bit tight for upstreaming  [17:06]
+<pinchartl> I'll schedule it for v4.9
+<kbingham> yes, that sounds more feasible.
+<pinchartl> next, Magnus  [17:08]
+<pinchartl> who's not available
+<pinchartl> AUDIO-DMAC,?,plan,magnus,IPMMU integration on Gen2
+<pinchartl> AUDIO-DMAC,?,plan,magnus,IPMMU integration on Gen3
+<pinchartl> AUDIO-DMAC,?,plan,magnus,IPMMU support on Gen2
+<pinchartl> AUDIO-DMAC,?,plan,magnus,IPMMU support on Gen3
+<pinchartl> VIN,?,prototype,magnus,IPMMU integration on Gen2
+<pinchartl> VIN,?,prototype,magnus,IPMMU integration on Gen3
+<pinchartl> VIN,?,prototype,magnus,IPMMU support on Gen2
+<pinchartl> VIN,?,prototype,magnus,IPMMU support on Gen3
+<pinchartl> is anyone aware of any progress there ?
+<pinchartl> I'll take that as a no :-)  [17:09]
+<neg> I know he started to look at VIN+IPMMU not sure how far he got  [17:10]
+<pinchartl> we don't have a "started looking at but not sure" status, I'll
+	    leave it as-is :-)
+<pinchartl> next, Morimoto-san  [17:11]
+<pinchartl> RSND,v4.10,public,morimoto,DT bindings for graph sound
+<pinchartl> RSND,v4.10,public,morimoto,dw-hdmi-i2s-audio prototype on Gen3
+<pinchartl> RSND,v4.10,prototype,morimoto,HDMI SSI prototype on Gen3
+<pinchartl> RSND,v4.10,plan,morimoto,HDMI sound Upstream support without
+	    hotplug on Gen2
+<pinchartl> RSND,2016-09-30,plan,morimoto,Hotplug support upstream on Gen3
+<morimoto> My ALSA + HDMI patch-set are 
+<morimoto> 1) cleanup patches  [17:12]
+<morimoto> 2) OF graph patches
+<morimoto> 3) OF graph base new sound card patches
+<morimoto> 4) HDMI sound driver patches
+<morimoto> I posted 1) and 2)
+<morimoto> 1) is slow progress
+<morimoto> Maintainer said 2) is OK for him, but he want to see 3)  [17:13]
+<morimoto> So, 2) and 3) will be merged and posted in next time
+<pinchartl> nice
+<morimoto> But, I don't know how to handle it on each Maintainer  [17:14]
+<morimoto> I'm asking it now
+<pinchartl> ok
+<morimoto> I asked about 2) to you pinchartl :)
+<morimoto> about port vs endpoint on video/sound
+<morimoto> not a big deal, but DT change after formal is difficult ?  [17:15]
+<pinchartl> I know
+<pinchartl> I haven't had time to review the patches yet
+<pinchartl> I'll try to do it this week but I can't promise
+<morimoto> OK
+<morimoto> that's it from me  [17:16]
+<morimoto> Maybe we can talk about it on MiniPeriCon ?
+<pinchartl> that's a good idea  [17:17]
+<morimoto> Thanks
+<pinchartl> next, Niklas
+<pinchartl> ADV7482,v4.7,public,niklas,Prototype on Gen3  [17:18]
+<pinchartl> ADV7482,v4.9,plan,niklas,Gen3 support upstream
+<pinchartl> ADV7482,v4.9,plan,niklas,Interlace support upstream
+<pinchartl> VIN,v4.7,public,niklas,CSI2 prototype (Gen3)
+<pinchartl> VIN,v4.8,public,niklas,Gen3 support
+<pinchartl> VIN,v4.8,plan,niklas,Scaler support (on Gen3
+<pinchartl> VIN,v4.9,plan,niklas,CSI2 interlace support upstream (Gen3)
+<pinchartl> VIN,v4.9,plan,niklas,CSI2 support upstream (Gen3)
+<pinchartl> VIN,v4.9,plan,niklas,Gen3 support upstream (without CSI-2)
+<neg> easy this time, no progress so far. Hope to have a new VIN patchset with
+      UDS support done before I leave for Tokyo  [17:19]
+<pinchartl> ok  [17:21]
+<pinchartl> for VIN,v4.8,public,niklas,Gen3 support
+<pinchartl> should that be moved to v4.9 ?
+<neg> yes since I think we need to figure out what/if to extend v4l2 to
+      support the ADV7482 first  [17:22]
+<pinchartl> and regarding No progress, will hopefully be implemented before
+	    PeriPeriCon.  [17:23]
+<pinchartl> oops
+<pinchartl> ADV7482,v4.7,public,niklas,Prototype on Gen3
+<pinchartl> VIN,v4.7,public,niklas,CSI2 prototype (Gen3)
+<neg> or do you think there is value to try and get driver up as soon as
+      possible that only works with a 1 output version of the adv7482?
+<pinchartl> as those are prototype tasks
+<pinchartl> they''re complete, right ?
+<neg> yes  [17:24]
+<pinchartl> thanks  [17:25]
+<pinchartl> for Gen3 support I don't think we need to rush the merge
+<pinchartl> it's likely too late for v4.8 already anyway  [17:26]
+<pinchartl> I'll move the scaler to v4.9 too  [17:27]
+<pinchartl> next, Ulrich
+<neg> thanks
+<pinchartl> DU,v4.7,plan,ulrich,Atomic API test program
+<pinchartl> DU,v4.7,public,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.9,plan,ulrich,HDMI output on Gen3 upstream
+<uli___> the test setup is up on elinux/github  [17:28]
+<uli___> edid generation will go out today
+<uli___> that's it
+<pinchartl> do you mean the HDMI loopback test setup ?  [17:30]
+<uli___> yes
+<pinchartl> how about DU,v4.7,plan,ulrich,Atomic API test program ?
+<uli___> i moved the wiki pages
+<uli___> that's what was missing, iirc
+<pinchartl> thanks  [17:31]
+<pinchartl> and DU,v4.7,public,ulrich,HDMI output on Gen3 prototype  [17:32]
+<pinchartl> is that considered as complete ?
+<uli___> let's consider it as such.  [17:33]
+<pinchartl> there was also  [17:34]
+<pinchartl> VIN,v4.8,public,ulrich,Add DV timings support to rcar-vin
+<uli___> that has been picked up recently
+<pinchartl> nice  [17:35]
+<pinchartl> by Hans ?
+<uli___> i just saw the auto-generated e-mail for the media tree
+<pinchartl> then they have been applied by Mauro, perfect
+<pinchartl> next, me, messing up the alphabetical order again  [17:37]
+<pinchartl> DU,?,plan,laurent,IPMMU integration on Gen3
+<pinchartl> DU,?,plan,laurent,IPMMU support on Gen3 (through VSPD+FCP)
+<pinchartl> DU,v4.9,plan,laurent,Fix 3 planes formats
+<pinchartl> no progress
+<pinchartl> VSP,?,plan,laurent,Fixed alpha support (VI6_DPR_*_ROUTE.FXA)
+<pinchartl> no progress
+<pinchartl> VSP,?,plan,laurent,UDS regression fix  [17:38]
+<pinchartl> it turns out that this requires implementing image partitioning
+	    support in the VSP driver
+<pinchartl> as, unlike the VSP1 in Gen2, the VSP2 in Gen3 can't scale images
+	    wider than 128 or 256 pixels (I have to check for the exact
+	    number)
+<pinchartl> so the images must be sliced by software, and the VSP run for each
+	    slice  [17:39]
+<pinchartl> I'll thus rename the task to "Image partitioning support"  [17:40]
+<pinchartl> UDS will work out of the box then
+<morimoto> pinchartl: about UDS regression, it was VSP driver side issue do
+	   you mean ?  [17:41]
+<pinchartl> it wasn't a regression  [17:42]
+<pinchartl> or rather
+<pinchartl> it's a hardware regression
+<morimoto> Ahh, OK
+<pinchartl> that requires significant additional work in the VSP driver
+<pinchartl> VSP,v4.8,plan,laurent,Fix suspend/resume crash  [17:43]
+<pinchartl> this isn't scheduled, I'll remove the target version
+<pinchartl> VSP,v4.8,public,laurent,HGO operation mode selection  [17:44]
+<pinchartl> VSP,v4.8,public,laurent,HGO support upstream on Gen3
+<pinchartl> VSP,v4.8,public,laurent,HGO test application
+<pinchartl> no progress
+<pinchartl> I hope to send a pull request this week
+<pinchartl> but it might be too late for v4.8
+<pinchartl> I'll move it to v4.9  [17:45]
+<pinchartl> VSP,v4.8,prototype,laurent,Rotation support
+<pinchartl> rotation itself is implemented
+<pinchartl> but it also requires image partitioning support for images wider
+	    than 256 pixels  [17:46]
+<pinchartl> this is a dependency that I wasn't aware of
+<pinchartl> I'll thus remove the target version due to the dependency on image
+	    partitioning that hasn't been scheduled yet  [17:47]
+<pinchartl> VSP,v4.8,public,laurent,V4L2 request API usable prototype  [17:48]
+<pinchartl> I was hoping to send the latest version Monday last week but got
+	    delayed, partly by the preparation of additional tasks for the
+	    multimedia team for Q3  [17:49]
+<pinchartl> and then by being unavailable from Friday to Tuesday
+<pinchartl> I'll resume now, the patches should go out today
+<morimoto> BSP team want to use latest verion on renesas-driver.  [17:50]
+<pinchartl> as soon as the patches are out I'll of course send a pull request
+	    to Geert  [17:51]
+<morimoto> sound gr8
+<pinchartl> that's it for the tasks  [17:53]
+<pinchartl> Topic 2. Additional '50%' tasks (June)
+<morimoto> pinchartl: what is current status of CLU/LUT ?
+<pinchartl> merged
+<morimoto> nice !
+<pinchartl> - VIN CSI-2 Support Prototype  [17:54]
+<pinchartl> - ADV7482 Driver Prototype
+<pinchartl> - VSP CLU Improvements
+<pinchartl> - VSP Rotation Support
+<pinchartl> - HDMI Input/Output Loopback for R-Car Gen2
+<pinchartl> - FDP Support on Gen3
+<pinchartl> I believe everything is complete
+<pinchartl> except for VSP rotation support
+<pinchartl> that is complete for images not wider than 256 pixels
+<pinchartl> Topic 3. Additional '50%' tasks (Q3)  [17:55]
+<morimoto> uli___: what is latest status of HDMI out for ES1.1 issue ?
+<pinchartl> (go ahead, we'll move to topic 3 after)  [17:56]
+<morimoto> pinchartl: sorry
+<uli___> still todo...
+<morimoto> OK.
+<pinchartl> creation of the 50% tasks for Q3 has been delayed  [17:57]
+<pinchartl> I've submitted the tasks for Ulrich, all others are still under
+	    discussion with Magnus
+<pinchartl> due to unforeseen and sad circumstances it didn't go as expected
+<pinchartl> uli___: have you received an SoW from Jinzai ?
+<uli___> not yet  [17:58]
+<uli___> for the 50% tasks, that is
+<pinchartl> ok
+<pinchartl> the two tasks currently planned for Ulrich are  [17:59]
+<pinchartl> VIN HDMI input EDID
+<pinchartl> VIN integration on Gen2
+<pinchartl> for Niklas we have initially discussed the UDS regression fix
+								        [18:00]
+<pinchartl> but as it turns out it will require more work than expected it
+	    wasn't a good match
+<pinchartl> the current plan is to implement support for one of the currently
+	    unimplemented VSP modules
+<pinchartl> the SHP (sharpener) was mentioned  [18:01]
+<pinchartl> but the hardware isn't fully documented
+<pinchartl> and the available source code just programs registers with
+	    parameters passed by upper software layers that are not available
+	    to us
+<pinchartl> so we'll likely switch to a different module
+<pinchartl> for Kieran and me the situation isn't clear either, I expected
+	    feedback from Magnus today  [18:02]
+<pinchartl> we'll try to fix this asap  [18:03]
+<kbingham> Understandable if magnus is away.
+<pinchartl> Topic 4. PeriPeriCon & RenesasCon preparation  [18:04]
+<pinchartl> unless there are questions about the additional tasks for Q3 ?
+<neg> I'm good for now :-)  [18:05]
+<pinchartl> for, for peripericon  [18:06]
+<pinchartl> s/for/so/
+<pinchartl> we'll discuss multimedia topics on Monday afternoon
+<pinchartl> there's no fixed agenda yet
+<pinchartl> now is the time to propose topics :-)
+<morimoto> I would like to talk about OF graph  [18:07]
+<neg> extensions to v4l2 to support subdevices with more then one output
+      pipeline
+<pinchartl> anything else ? uli___ and kbingham I know you won't be there, but
+	    are there topics you would like us to discuss ?  [18:09]
+<uli___> can't think of anything  [18:10]
+<pinchartl> I'd like to discuss the following topics
+<pinchartl> - Second batch of additional tasks for Q3
+<pinchartl> - What are we doing right or wrong, and how can we improve
+<pinchartl> - Long-term roadmap
+<neg> hum I don't know if this is on the roadmap but if there is plans to
+      support audio in or CEC from VIN HDMI how that would work. But maybe
+      that is covered in morimoto topic about OF graph?  [18:11]
+<kbingham> the current m2m design is limited and seems to prevent pipelined
+	   usage of hw ... but I think that's possibly a topic for linux-media
+	   . But that's the only thing I can think of on my future discussion
+	   lists.
+<pinchartl> neg: I might be mistaken but I don't think we have hardware
+	    support for CEC  [18:12]
+<pinchartl> the target market for Renesas devices isn't exactly consumer
+	    electronics :-)  [18:13]
+<pinchartl> kbingham: yes, I think that's a topic for linux-media
+<pinchartl> I'll write it down as a potential task for the future
+<neg> pinchartl: hum ofc CEC is terminated in the adv7482 so it might not be
+      high on the agenda  [18:14]
+<pinchartl> ah, ADV7482 has CEC support ?
+<pinchartl> good to know
+<pinchartl> I'm sure Hans would be interested
+<pinchartl> but I don't think Renesas would. we should of course ask
+<pinchartl> same for audio input. Morimoto-san, do you know if there's an
+	    interest in HDMI audio input ?  [18:15]
+<morimoto> Yeah, of course
+<morimoto> Oops,
+<morimoto> Do you mean BSP request ?
+<morimoto> BSP team doesn't have such request at this point.  [18:16]
+<pinchartl> either an existing BSP request, or something that would be of
+	    interest to them in the future
+<pinchartl> same for HDMI CEC support, is there an interest ?
+<morimoto> but it seems they are starting about HDMI support for customer
+<morimoto> I can say BSP team is stating about "HDMI" only, they don't know
+	   detail of it :)  [18:17]
+<pinchartl> ok
+<morimoto> So yes, in the future, they will request such detail feature
+<pinchartl> we can discuss that during RenesasCon  [18:18]
+<pinchartl> I'll send out the list of topics for PeriPeriCon in the meeting
+	    report, if anyone wants to add topics to the agenda it will still
+	    be possible until the end of the week
+<pinchartl> Morimoto-san and Niklas, could you each prepare a very brief
+	    presentation for the topic you proposed for the meeting ?
+								        [18:19]
+<pinchartl> it should be 5 minutes long at most
+<pinchartl> just to get everybody on the same page to start discussions
+<morimoto> on email ? or here ?
+<pinchartl> no, for PeriPeriCon  [18:20]
+<neg> will do
+<morimoto> OK, will do
+<pinchartl> thank you
+<pinchartl> regarding RenesasCon
+<pinchartl> I propose finalizing the preparation for it during PeriPeriCon
+<pinchartl> Renesas is driving the agenda there  [18:21]
+<pinchartl> but it will be a good occasion to ask questions
+<pinchartl> for instance regarding HDMI audio input and CEC
+<pinchartl> I will also prepare a presentation of the multimedia group
+	    activities  [18:22]
+<pinchartl> neg: I've seen the slides you've sent, thank you
+<pinchartl> morimoto: do you think we need a detailed presentation from each
+	    developer, or a single summary presentation of our activities ?
+								        [18:23]
+<neg> I hope they are on the right level for the event. Thanks morimoto for
+      your comments!
+<morimoto> pinchartl: it up to you :) I can say it is free style  [18:24]
+<morimoto> neg: no problem :P
+<morimoto> basically, 1 person has 10min. style is free  [18:25]
+<morimoto> BTW, I created Wiki page for MiniPeriCon and RenesasCon  [18:26]
+<morimoto>
+	   https://osdr.renesas.com/projects/linux-kernel-development/wiki#PeriPeriCon
+<morimoto> We can use it
+<morimoto> 
+<pinchartl> thank you
+<pinchartl> I think that's it then  [18:27]
+<pinchartl> the next multimedia meeting will be during PeriPeriCon
+<morimoto> sounds nice :)
+<pinchartl> and the one after that will be on Wednesday two weeks later, I'll
+	    send an invite
+* kbingham wishes he was going to Japan :)   [18:28]
+<pinchartl> kbingham: it's not too late to book a plane ticket ;-)
+<neg> I have a practical question for peripericon and renesascon, do anyone
+      plan to bring a HDMI->VGA adapter incase we find an old beamer :-)
+<morimoto> kbingham: can we meet on Oct ELCE ?
+<kbingham> morimoto: Of course :) I'll be at ELCE
+<kbingham> pinchartl: It's not the ticket preventing me from going to japan
+	   next week :)  [18:29]
+<morimoto> Oops, we need projector on MiniPeriCon ? I need to prepare
+<pinchartl> morimoto: yes, that would be useful
+<pinchartl> neg: I don't have one  [18:30]
+<neg> me neither, so I will buy one then so we have if needed  [18:31]
+<pinchartl> I propose adjourning the meeting. does anyone second ?  [18:32]
+<neg> seconded  [18:33]
+<pinchartl> thank you
+<pinchartl> the meeting is adjourned, talk to you in Tōkyō for the ones who
+	    will be there  [18:34]
+<neg> thanks all
+<morimoto> thanks
+<kbingham> Cheers and Enjoy!  [18:35]
+<morimoto> pinchartl: when you arrive to Jinbotyo station A4 exit, you can
+	   email me by "kuninori.morimoto.gx@renesas.com" or
+	   "dr.mk.gemini@gmail.com"  [18:36]
+<pinchartl> morimoto: I don't think I'll have an internet connection
+<morimoto> Maybe it can be good lunch time :)
+<morimoto> Oops, from Hotel ?
+<pinchartl> I can probably send you an e-mail when I leave the hotel  [18:37]
+<pinchartl> and call you when I get to the station
+<pinchartl> I can also send a text message to Niklas
+<pinchartl> or Geert or Wolfram
+<morimoto> OK, sound nice !!
+<morimoto> Have a nice trip you guys !!  [18:38]
+<pinchartl> thank you
+<morimoto> note that, unfortunately, Japan in rainy season now.
+<neg> another Q, can I fit my US power plug into a JP socket physicly? (yes I
+      know the voltages are different) the internet gives me different awnsers
+								        [18:39]
+<morimoto> I always using Japan plug on US without exchanger  [18:40]
+<morimoto> I'm always using Japanese plug in US without exchanger
+<neg> nice thx
+<morimoto> OK, thanks you guys, I will quit  [18:42]