Hi Laurent, On Fri, Feb 17, 2023 at 01:11:05AM +0200, Laurent Pinchart wrote: > Hi Sakari, > > On Thu, Feb 16, 2023 at 10:12:22AM +0200, Sakari Ailus wrote: > > On Wed, Feb 15, 2023 at 09:23:05PM +0200, Laurent Pinchart wrote: > > > On Wed, Feb 15, 2023 at 02:00:46PM +0200, Sakari Ailus wrote: > > > > On Fri, Feb 10, 2023 at 12:34:01AM +0200, Laurent Pinchart wrote: > > > > > Thank you for the patch. > > > > > > > > Thanks for the review! > > > > > > > > This was indeed hastily written, to help debugging a particular issue. But > > > > I hope it'll be useful for other purposes, too. V4L2 async is about to get > > > > more complicated soon. > > > > > > Could it get simpler instead ? :-) Maybe one day v4l2-async may cross > > > the threshold of how much pain I can bear, and I'll rewrite it... > > > > I wish it could, but often supporting complex needs is complicated. > > "Simplicated" is not even a proper word after all. Let's see. > > Don't try to lure me into rewriting it sooner than later ;-) This could be all avoided if drivers got all what they need during probe. It would require vast changes accross a large number of drivers and might never happen. Also this is related to not exposing access any hardware before all of it is available. -- Regards, Sakari Ailus
