<!-- Some styling for better description lists --><style type='text/css'>dt { font-weight: bold;float: left;display:inline;margin-right: 1em} dd { display:block; margin-left: 2em}</style>

   sailus: <u>mripard</u>: Hello!
   mripard: <u>sailus</u>: hi
   sailus: <u>mripard</u>: A bit of latency both ways. :-)
   <br> On the ov5640 driver --- I'd like to postpone the PLL patches until the driver works for where it used to work in the past.
   <br> I guess a fix on the top of the set would be fine.
   mripard: <u>sailus</u>: yeah, definitely
   <br> I didn't expect it to be merged if it breaks MIPI-CSI anyway
   sailus: Good that it came up before I sent a pull request to Mauro...
   <br> I'll take the patches out of that branch for now.
   <br> If there's a simple fix on the top, I could just apply it there, or I'll replace the set if there's a new version of the entire set.
   mripard: <u>sailus</u>: it's not really clear at that point
   <br> so I guess we should just postpone it for the moment
   <br> <u>sailus</u>: however, if you do want to merge some patches, https://patchwork.linuxtv.org/patch/49258/ would be a good candidate ;)
   neg: <u>sailus</u>: I have a question about your for-4.18-6 brach, all commits but the top 3 are in the media-tree, is there a reason for this ? I miss the rcar-csi2 driver in the media-tree :-)
   sailus: <u>mripard</u>: I'll check that out... thanks for the reminder.
   <br> <u>neg</u>: There's only that driver.
   <br> I wanted to put it in a separate branch from the sensor and lens stuff.
   neg: <u>sailus</u>: ahh thanks, just got a bit worried it wound not make it for 4.18. Thanks for reassuring me ;-)
   sailus: <u>neg</u>: I sent the pull request earlier today.
   neg: <u>sailus</u>: Ahh I found it, thanks. I did check for it yesterday when I looked at the media-tree, sorry I should have checked again today before asking you. Thanks for taking the driver
   pinchartl: <u>jmondi</u>: ^^
   <br> regarding ov5640
   <br> do you think it would be feasible to test Maxime's patches on our hardware platform ?
   jmondi: <u>pinchartl</u>: good question, I would say why not, I don't see any specific reasons why not, if not the time to cut through the thick host-platform camera support framework
   <br> <u>pinchartl</u>: btw, we fall into the 24MHz input clock use case, and if I got it right, that is tested to work with CSI-2 interface too
   ***: hverkuil has quit IRC (Quit: ZNC 1.6.6+deb1 - http://znc.in)
   mripard: <u>jmondi</u>: no, this was tested and working on DVP
   <br> CSI2 seems to be broken
   noze: hi
   <br> is there a way to configure a webcam as the "preferred choice"?
   <br> eg by configuring the assignment of a specific device node?
   ***: Marex has quit IRC (Ping timeout: 265 seconds)