From: Nikita Yushchenko <nikita.yoush@cogentembedded.com>
To: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Vladimir Barinov <vladimir.barinov@cogentembedded.com>
Subject: Re: [PATCH] media: rcar-vin: add G/S_PARM ioctls
Date: Fri, 24 Sep 2021 16:48:29 +0300 [thread overview]
Message-ID: <c90a960f-4c4d-7e9c-5f85-2931d1530550@cogentembedded.com> (raw)
In-Reply-To: <YU2gSJKfsqP+gUci@oden.dyn.berto.se>
> I would like to ask your use-case for this. I'm trying to make up the
> courage to move Gen2 inline with Gen3, that is move Gen2 to use the
> media graph interface to allow it more complex use-cases, including
> controlling parameters on the subdevice level.
>
> So I'm curious if this solve a particular problem for you or if it's
> done "just" for completeness. If it solves a real problem then I think
> we should move a head with a v2 (with the small comment below fixed) if
> not I would like to try and reduce the non media graph usage of the API
> as much as possible.
I believe parallel camera - such as ov5642 - connected to Kingfisher's parallel interface still has to
be controlled over v4l operations on vin device. And, to control frame rate of such cameras [which is
the usecase we have here at Cogent], the operations that this patch adds are requied.
> Please use &vin->vdev instead of video_devdata(file).
Preparing v2 now.
Nikita
next prev parent reply other threads:[~2021-09-24 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 8:41 [PATCH] media: rcar-vin: add G/S_PARM ioctls Nikita Yushchenko
2021-09-24 9:54 ` Niklas Söderlund
2021-09-24 13:48 ` Nikita Yushchenko [this message]
2021-09-24 13:51 ` [PATCH v2] " Nikita Yushchenko
2021-09-28 0:03 ` Niklas Söderlund
2021-09-28 8:43 ` Jacopo Mondi
2021-10-12 7:33 ` Hans Verkuil
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=c90a960f-4c4d-7e9c-5f85-2931d1530550@cogentembedded.com \
--to=nikita.yoush@cogentembedded.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=niklas.soderlund@ragnatech.se \
--cc=vladimir.barinov@cogentembedded.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;
as well as URLs for NNTP newsgroup(s).