From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ricardo Ribalda <ribalda@chromium.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Esker Wong <esker@chromium.org>
Subject: Re: [PATCH] media: uvcvideo: Implement V4L2_EVENT_FRAME_SYNC
Date: Mon, 6 Nov 2023 12:59:41 +0200 [thread overview]
Message-ID: <20231106105941.GB16995@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CANiDSCsnrb5a3XTnHRrUjttcV6aAw7yC6RtUApvsK5CBhFGJyQ@mail.gmail.com>
On Mon, Nov 06, 2023 at 11:51:06AM +0100, Ricardo Ribalda wrote:
> On Mon, 6 Nov 2023 at 11:42, Laurent Pinchart wrote:
> > On Mon, Nov 06, 2023 at 12:39:26PM +0200, Laurent Pinchart wrote:
> > > On Fri, Oct 20, 2023 at 06:41:45AM +0000, Ricardo Ribalda wrote:
> > > > Add support for the frame_sync event, so user-space can become aware
> > > > earlier of new frames.
> > > >
> > > > Suggested-by: Esker Wong <esker@chromium.org>
> > > > Tested-by: Esker Wong <esker@chromium.org>
> > > > Signed-off-by: Ricardo Ribalda <ribalda@chromium.org>
> > > > ---
> > > > We have measured a latency of around 30msecs between frame sync
> > > > and dqbuf.
> > >
> > > Not surprising, especially for large resolutions. I'm curious though,
> > > what do you use this event for ?
>
> I think Esker is using it to get more accurate power measurements of
> the camera stack.
Esker, would you be able to provide more information ?
> > > It's easy to miss the ++ there when reading the code, would the
> > > following be more readable ?
>
> Actually that was my original code, but I thought you would like this better :)
>
> Thanks for the review, a v2 is on its way.
Thank you.
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2023-11-06 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-20 6:41 Ricardo Ribalda
2023-11-05 18:34 ` Ricardo Ribalda
2023-11-06 10:39 ` Laurent Pinchart
2023-11-06 10:42 ` Laurent Pinchart
2023-11-06 10:51 ` Ricardo Ribalda
2023-11-06 10:59 ` Laurent Pinchart [this message]
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=20231106105941.GB16995@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=esker@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
/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
all inboxes | Powered by JetHome®