From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751313AbdBBATe (ORCPT ); Wed, 1 Feb 2017 19:19:34 -0500 Received: from mail-pg0-f65.google.com ([74.125.83.65]:35169 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751052AbdBBATc (ORCPT ); Wed, 1 Feb 2017 19:19:32 -0500 Subject: Re: [PATCH v3 00/24] i.MX Media Driver To: Philipp Zabel References: <1483755102-24785-1-git-send-email-steve_longerbeam@mentor.com> <1485870854.2932.63.camel@pengutronix.de> <5586b893-bf5c-6133-0789-ccce60626b86@gmail.com> <1485941457.3353.13.camel@pengutronix.de> Cc: robh+dt@kernel.org, mark.rutland@arm.com, shawnguo@kernel.org, kernel@pengutronix.de, fabio.estevam@nxp.com, linux@armlinux.org.uk, mchehab@kernel.org, hverkuil@xs4all.nl, nick@shmanahar.org, markus.heiser@darmarIT.de, laurent.pinchart+renesas@ideasonboard.com, bparrot@ti.com, geert@linux-m68k.org, arnd@arndb.de, sudipm.mukherjee@gmail.com, minghsiu.tsai@mediatek.com, tiffany.lin@mediatek.com, jean-christophe.trotin@st.com, horms+renesas@verge.net.au, niklas.soderlund+renesas@ragnatech.se, robert.jarzmik@free.fr, songjun.wu@microchip.com, andrew-ct.chen@mediatek.com, gregkh@linuxfoundation.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-media@vger.kernel.org, devel@driverdev.osuosl.org, Steve Longerbeam From: Steve Longerbeam Message-ID: <8e577a3f-8d44-9dde-9507-36c3769228b6@gmail.com> Date: Wed, 1 Feb 2017 16:19:27 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0 MIME-Version: 1.0 In-Reply-To: <1485941457.3353.13.camel@pengutronix.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/01/2017 01:30 AM, Philipp Zabel wrote: > On Tue, 2017-01-31 at 17:26 -0800, Steve Longerbeam wrote: > [...] >>> # Set pad formats >>> media-ctl --set-v4l2 "'tc358743 1-000f':0[fmt:UYVY/1920x1080]" >>> media-ctl --set-v4l2 "'imx6-mipi-csi2':1[fmt:UYVY2X8/1920x1080]" >>> media-ctl --set-v4l2 "'ipu1_csi0_mux':2[fmt:UYVY2X8/1920x1080]" >>> media-ctl --set-v4l2 "'ipu1_csi0':2[fmt:AYUV32/1920x1080]" >>> >>> v4l2-ctl -d /dev/video4 -V >>> # This still is configured to 640x480, which is inconsistent with >>> # the 'ipu1_csi0':2 pad format. The pad set_fmt above should >>> # have set this, too. >> Because you've only configured the source pads, >> and not the sink pads. The ipu_csi source format is >> dependent on the sink format - output crop window is >> limited by max input sensor frame, and since sink pad is >> still at 640x480, output is reduced to that. > No, it is set (see below). What happens is that capture_g_fmt_vid_cap > just returns the capture devices' priv->vdev.fmt, even if it is > incompatible with the connected csi subdevice's output pad format. > > priv->vdev.fmt was never changed from the default set in > imx_media_capture_device_register, because capture_s/try_fmt_vid_cap > were not called yet. Ah, yep, this is a bug. Need to modify the capture device's width/height at .set_fmt() in the subdev's device-node source pad (csi and prpenc/vf). >> Maybe I'm missing something, is it expected behavior that >> a source format should be automatically propagated to >> the sink? > media-ctl propagates the output pad format to all remote subdevices' > input pads for all enabled links: > > https://git.linuxtv.org/v4l-utils.git/tree/utils/media-ctl/libv4l2subdev.c#n693 Ah cool, I wasn't aware media-ctl did this, but it makes sense and makes it easier on the user. Steve > >>> v4l2-ctl --list-formats -d /dev/video4 >>> # This lists all the RGB formats, which it shouldn't. There is >>> # no CSC in this pipeline, so we should be limited to YUV formats >>> # only. >> right, need to fix that. Probably by poking the attached >> source subdev (csi or prpenc/vf) for its supported formats. > You are right, in bayer/raw mode only one specific format should be > listed, depending on the CSI output pad format. > > regards > Philipp >