From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, frieder.schrempf@kontron.de,
Tim Harvey <tharvey@gateworks.com>,
linux-arm-kernel@lists.infradead.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Javier Martinez Canillas <javierm@redhat.com>
Subject: Re: [RFC 1/1] v4l: async: Add some debug prints
Date: Fri, 17 Feb 2023 13:39:32 +0200 [thread overview]
Message-ID: <Y+9ndOYuG8WNv1mL@kekkonen.localdomain> (raw)
In-Reply-To: <Y+64CdATkoeE5AdL@pendragon.ideasonboard.com>
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
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-17 11:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 14:24 Capture image from imx219 sensor on i.MX8MM Frieder Schrempf
2023-02-06 15:31 ` Laurent Pinchart
2023-02-06 15:38 ` Frieder Schrempf
2023-02-06 15:49 ` Dave Stevenson
2023-02-06 15:50 ` Laurent Pinchart
2023-02-07 15:24 ` Frieder Schrempf
2023-02-09 22:16 ` [RFC 1/1] v4l: async: Add some debug prints Sakari Ailus
2023-02-09 22:34 ` Laurent Pinchart
2023-02-15 12:00 ` Sakari Ailus
2023-02-15 19:23 ` Laurent Pinchart
2023-02-16 8:12 ` Sakari Ailus
2023-02-16 23:11 ` Laurent Pinchart
2023-02-17 11:39 ` Sakari Ailus [this message]
2023-02-14 10:25 ` Frieder Schrempf
2023-02-14 14:56 ` Sakari Ailus
2023-02-14 14:57 ` Frieder Schrempf
2023-02-09 22:19 ` Capture image from imx219 sensor on i.MX8MM Laurent Pinchart
2023-02-14 10:18 ` Frieder Schrempf
2023-02-14 10:52 ` Laurent Pinchart
2023-02-14 13:19 ` Frieder Schrempf
2023-02-14 13:57 ` Frieder Schrempf
2023-07-07 21:57 ` Tim Harvey
2023-07-10 7:57 ` Frieder Schrempf
2023-07-11 20:02 ` Tim Harvey
2023-07-12 6:27 ` Frieder Schrempf
2023-07-13 23:37 ` Tim Harvey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y+9ndOYuG8WNv1mL@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=frieder.schrempf@kontron.de \
--cc=javierm@redhat.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=tharvey@gateworks.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox