mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ricardo Ribalda <ribalda@chromium.org>
To: Nicolas Dufresne <nicolas@ndufresne.ca>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Esker Wong <esker@google.com>,
	Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Sakari Ailus <sakari.ailus@iki.fi>,
	Esker Wong <esker@chromium.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] media: uvcvideo: Implement V4L2_EVENT_FRAME_SYNC
Date: Fri, 24 Nov 2023 10:58:01 +0100	[thread overview]
Message-ID: <CANiDSCsctSyfgXxH3iroJPOE7R_9jB7todiEMBCU_5OG3EOCKQ@mail.gmail.com> (raw)
In-Reply-To: <ded0b788f5896621cffd8f64c679ef375231b6d1.camel@ndufresne.ca>

> >
> > For bulk devices this is a maximum of 0.05 msec (32KiB/600MBps)
>
> I lack a bit of knowledge on how to scale this to different devices, with
> different speed/framesize. My only bulk device is:
>
> https://inogeni.com/product/4k2usb3/
>
> Which is USB 3.0, and have raw (NV12) resolution from 640x480 (max 60pfs) to 4K
> (max 30fps). What would the error look like with that ?

For bulk devices the maximum delay from packing multiple packets into
a urb is 0.05 msec (32KiB/600MBps)

Laurent's message <20231109000327.GE21616@pendragon.ideasonboard.com>
explains where those numbers come from :).

Regards!

>
> > For 1MiB transfer isoc devices (which is the biggest we have seen),
> > that is 1.8 msec.
> > In both cases, this is smaller than the jitter to process the event
> > itself by userspace.
> >
> > The time from V4L2_EVENT_FRAME_SYNC to DQBUF is around 30 msec.
> >
> > I do not know how much delay is considered acceptable... but if we
> > take the delay argument to the extreme, we could say that
> > V4L2_EVENT_FRAME_SYNC can never be implemented, because the event will
> > always be delayed by something.
>
> We have v4l2_event.timestamp for all events, so the jitter to process the event
> by userpace can be removed reliably already.
>
> Nicolas
>
> p.s. missed it earlier
>
> >
> > >
> > > --
> > > Regards,
> > >
> > > Laurent Pinchart
> >
> >
> >
>


--
Ricardo Ribalda

  reply	other threads:[~2023-11-24  9:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 10:52 Ricardo Ribalda
2023-11-06 11:05 ` Sakari Ailus
2023-11-06 11:58   ` Ricardo Ribalda
2023-11-07  5:06   ` Esker Wong
2023-11-07  7:36     ` Sakari Ailus
2023-11-07 10:58       ` Ricardo Ribalda
2023-11-07 19:27     ` nicolas
2023-11-08  6:53       ` Esker Wong
2023-11-08  7:04         ` Ricardo Ribalda
2023-11-08 20:32           ` nicolas
2023-11-08 22:10             ` Laurent Pinchart
2023-11-08 22:46             ` Ricardo Ribalda
2023-11-09  0:03               ` Laurent Pinchart
2023-11-09  0:27                 ` Ricardo Ribalda
2023-11-23 18:22                   ` Nicolas Dufresne
2023-11-24  9:58                     ` Ricardo Ribalda [this message]
2023-11-09  0:59                 ` Esker Wong
2023-11-09 11:34                   ` Laurent Pinchart
2023-11-09 11:41                     ` Esker Wong

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=CANiDSCsctSyfgXxH3iroJPOE7R_9jB7todiEMBCU_5OG3EOCKQ@mail.gmail.com \
    --to=ribalda@chromium.org \
    --cc=esker@chromium.org \
    --cc=esker@google.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nicolas@ndufresne.ca \
    --cc=sakari.ailus@iki.fi \
    /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®