Linux Media Controller development
 help / color / mirror / Atom feed
From: Steve Longerbeam <slongerbeam@gmail.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Tim Harvey <tharvey@gateworks.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH] media: imx.rst: Update the imx6-sabreauto ADV7180 instructions
Date: Wed, 16 Oct 2019 10:31:23 -0700	[thread overview]
Message-ID: <8b2f0c05-8e4f-72d9-d37f-c41936fcfd07@gmail.com> (raw)
In-Reply-To: <CAOMZO5BAsNzngLF2=1h38j0KYdvGLankQwzZ8tpG68sKSvaboQ@mail.gmail.com>



On 10/16/19 6:04 AM, Fabio Estevam wrote:
> Hi Steve,
>
> On Tue, Oct 15, 2019 at 10:18 PM Steve Longerbeam <slongerbeam@gmail.com> wrote:
>
>> Here's a quick example that uses the end-of-frame method to measure fi's
>> (all other FIM controls are left at the default values):
>>
>> v4l2-ctl -d0 --set-ctrl=fim_enable=1
>> # disable input capture method
>> v4l2-ctl -d0 --set-ctrl=fim_input_capture_edge=0
>> v4l2-ctl -d0 --stream-mmap
> What needs to be done for 'fim_enable' to be available?
>
> I am using a mx6dl-sabreauto, and this is what I get:
>
> # v4l2-ctl -d2 --set-ctrl=fim_enable=1
> unknown control 'fim_enable'

If /dev/video2 is the "ipu1_ic_prpvf capture" node, it's because FIM is 
not yet available on those nodes. The FIM is only available on the 
"ipuX_csiY capture" nodes. It's on my plate to fix that.

But also remember that the FIM controls are inherited from the ipuX_csiY 
subdevices when the link from ipuX_csiY is enabled, so while the 
controls are always available on ipuX_csiY, they become available on 
"ipuX_csiY capture" nodes when the link is enabled.

Steve


  reply	other threads:[~2019-10-16 17:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 15:44 [PATCH] media: imx.rst: Update the imx6-sabreauto ADV7180 instructions Fabio Estevam
2019-10-12 20:14 ` Steve Longerbeam
2019-10-12 20:24   ` Steve Longerbeam
2019-10-12 21:19     ` Fabio Estevam
2019-10-15 15:49       ` Tim Harvey
2019-10-15 15:53         ` Fabio Estevam
2019-10-15 16:07           ` Tim Harvey
2019-10-15 16:16             ` Fabio Estevam
2019-10-15 16:33               ` Tim Harvey
2019-10-15 16:42                 ` Fabio Estevam
2019-10-15 18:19                   ` Steve Longerbeam
2019-10-15 19:11                     ` Fabio Estevam
2019-10-16  1:17                       ` Steve Longerbeam
2019-10-16  1:32                         ` Fabio Estevam
2019-10-16 13:04                         ` Fabio Estevam
2019-10-16 17:31                           ` Steve Longerbeam [this message]
2019-10-16 18:54                             ` Fabio Estevam
2019-10-16 19:11                               ` Steve Longerbeam
2019-10-16 19:51                                 ` Fabio Estevam
2020-06-25 10:53                                   ` Hans Verkuil
2020-06-25 11:38                                     ` Fabio Estevam

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=8b2f0c05-8e4f-72d9-d37f-c41936fcfd07@gmail.com \
    --to=slongerbeam@gmail.com \
    --cc=festevam@gmail.com \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --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