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 12:11:05 -0700 [thread overview]
Message-ID: <7431d1dc-10fc-0880-01ed-cf75b5ace704@gmail.com> (raw)
In-Reply-To: <CAOMZO5D4R+ta6By2Th5WF9THKXuzjFV8cLxPw+zyj-Kv4k=7kA@mail.gmail.com>
On 10/16/19 11:54 AM, Fabio Estevam wrote:
> On Wed, Oct 16, 2019 at 2:31 PM Steve Longerbeam <slongerbeam@gmail.com> wrote:
>
>> 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.
> On a 5.3.6 kernel on imx6dl-sabreauto:
>
> # v4l2-ctl --list-devices
> imx-media (platform:imx-media):
> /dev/media0
>
> imx-media-capture (platform:ipu1_csi0):
> /dev/video0
>
> imx-media-capture (platform:ipu1_csi1):
> /dev/video3
FIM is available on the above nodes (/dev/video0 and /dev/video3), after
enabling links to them. So please try:
# media-ctl -l "'ipu1_csi0':2 -> 'ipu1_csi0 capture':0[1]"
# v4l2-ctl -d0 --list-ctrls
# media-ctl -l "'ipu1_csi1':2 -> 'ipu1_csi1 capture':0[1]"
# v4l2-ctl -d3 --list-ctrls
Steve
>
> imx-media-capture (platform:ipu1_ic_prpenc):
> /dev/video1
>
> imx-media-capture (platform:ipu1_ic_prpvf):
> /dev/video2
>
>
> # v4l2-ctl -d0 --list-ctrls
> # v4l2-ctl -d1 --list-ctrls
> # v4l2-ctl -d2 --list-ctrls
>
> User Controls
>
> brightness 0x00980900 (int) : min=-128 max=127 step=1 dr
> contrast 0x00980901 (int) : min=0 max=255 step=1 defar
> saturation 0x00980902 (int) : min=0 max=255 step=1 defar
> hue 0x00980903 (int) : min=-127 max=128 step=1 dr
> horizontal_flip 0x00980914 (bool) : default=0 value=0
> vertical_flip 0x00980915 (bool) : default=0 value=0
> rotate 0x00980922 (int) : min=0 max=270 step=90 deft
> fast_switching 0x00981970 (bool) : default=0 value=0
>
> Image Processing Controls
>
> deinterlacing_mode 0x009f0904 (menu) : min=0 max=3 default=3 val3
> # v4l2-ctl -d3 --list-ctrls
> #
>
> I cannot see the FIM controls appearing in any device here.
>
> Anything I am missing?
>
> Thanks
next prev parent reply other threads:[~2019-10-16 19:11 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
2019-10-16 18:54 ` Fabio Estevam
2019-10-16 19:11 ` Steve Longerbeam [this message]
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=7431d1dc-10fc-0880-01ed-cf75b5ace704@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;
as well as URLs for NNTP newsgroup(s).