<!-- 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>

   jmondi: <u>hverkuil</u>: koike: Good morning! I would have a question regarding VIMC, is anyone of you two around ?
   hverkuil: <u>jmondi</u>: I'm around :-)
   jmondi: <u>hverkuil</u>: Hi Hans
   <br> <u>hverkuil</u>: nothing huge, in libcamera we heavly use VIMC as a test platform, and we're about to introduce new requirements for sensor drivers, starting with the presence of the PIXEL_RATE and VBLANK controls
   <br> the VIMC sensor does not support them, and I was wondering if it makes sensor to add them to the driver
   <br> they will have to have fixed values I assume
   <br> I'm not totally convinced it makes full sense to add those fake values to the driver just to please a new requirement we imposed though
   hverkuil: So these controls will be added to existing sensor drivers as well?
   <br> (for those drivers that do not already support them)
   jmondi: that's the plan
   <br> it won't happen in one go and in one day of coure
   hverkuil: Ah, most have them already. So it is perfectly fine to add them to the vimc sensor driver as well.
   jmondi: what values should be used in your opinion ?
   <br> the VIMC driver does not have any actual pixel rate nor vblankings
   <br> being it... virtual :)
   hverkuil: No idea :-)  It's been some time since I last dug into that.
   jmondi: ok, I'll figure out something then
   hverkuil: I think it should be possible to calculate reasonable values based on resolution and framerate.
   jmondi: it should
   hverkuil: I'm not sure about the framerate, though. It might be hardcoded to 60 Hz in vimc (vimc_streamer_thread)
   <br> Yeah, I think it's hardcoded.
   ***: mmattice has quit IRC (Ping timeout: 240 seconds)
   <br> mattst88 has left