From: Hans Verkuil <hverkuil@xs4all.nl>
To: Max Staudt <mstaudt@chromium.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Ricardo Ribalda <ribalda@chromium.org>,
Yunke Cao <yunkec@chromium.org>, Tomasz Figa <tfiga@chromium.org>
Subject: Re: [PATCH v1] media: vivid: Add webcam parameter for (un)limited bandwidth
Date: Tue, 11 Apr 2023 09:45:07 +0200 [thread overview]
Message-ID: <5649adcd-3afe-e413-2eac-a92c78427dc9@xs4all.nl> (raw)
In-Reply-To: <c6d5be4c-42c9-b8fa-fbd7-108c5da694bc@chromium.org>
On 11/04/2023 09:31, Max Staudt wrote:
> On 4/11/23 16:26, Hans Verkuil wrote:
>> I think we either use this bandwidth option and calculate the max fps based on
>> that (basically the bandwidth divided by (image_size + some blanking factor)),
>> or we keep it simple and instead of going down two steps in fps we allow up to
>> 60 fps up to 720p, then 30 fps for 1080p and 15 fps for 4k.
>>
>> The fps values currently used are a bit outdated w.r.t. modern webcams, so
>> upgrading it wouldn't hurt. And this is a lot simpler than doing bandwidth
>> calculations.
>
> Do I understand you correctly, are you suggesting to simply update the FPS limits to a new fixed schema, and not have an option at all?
Correct.
The ideal solution is indeed proper bandwidth calculations, since this would
be a proper emulation of actual webcam hardware. If you have time and are
interested in doing the work, then that would be great, of course.
But if you just want to increase the fps limits to be more in line with
modern webcams, then that's much quicker and should be fine.
It might also be interesting to perhaps allow for 120 fps for the low
resolutions (below 720p).
Regards,
Hans
>
> I'm happy to prepare an alternative patch for that, too.
>
>
>
> Max
>
next prev parent reply other threads:[~2023-04-11 7:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 6:33 Max Staudt
2023-04-10 9:23 ` Mauro Carvalho Chehab
2023-04-11 6:51 ` Max Staudt
2023-04-11 7:26 ` Hans Verkuil
2023-04-11 7:31 ` Max Staudt
2023-04-11 7:45 ` Hans Verkuil [this message]
2023-04-11 11:34 ` Max Staudt
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=5649adcd-3afe-e413-2eac-a92c78427dc9@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mstaudt@chromium.org \
--cc=ribalda@chromium.org \
--cc=tfiga@chromium.org \
--cc=yunkec@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®