From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.6 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 153D4C004D3 for ; Wed, 24 Oct 2018 13:53:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C2C152064A for ; Wed, 24 Oct 2018 13:53:57 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="dnQm9tDr" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C2C152064A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726838AbeJXWWI (ORCPT ); Wed, 24 Oct 2018 18:22:08 -0400 Received: from mail-ed1-f66.google.com ([209.85.208.66]:45659 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726285AbeJXWWI (ORCPT ); Wed, 24 Oct 2018 18:22:08 -0400 Received: by mail-ed1-f66.google.com with SMTP id t10-v6so5117262eds.12; Wed, 24 Oct 2018 06:53:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=hDExxvTKhJ/o1frLwdFq+stcMXreRFG+e9E30ZfmyjU=; b=dnQm9tDroDTVc9evPX72Rqzuezcs9D6OKHrsHB/QyoQY9vxluWY0SSG+4sRZl/w/ZW VHYSouyxU2l7ffLPs08L6BxOz7rjE/akHPg9a8ZGRW3S/NaavomzmsRoW11LRCtg0qrA 9SXrzypANJXKIm3jC4Tt7XyMBH9/BGgx71dOrimkAQcNMt8qABY8hYARCTRn6S7c1ncm J/angYTuRY2njR5dSYGxNsIW6MW4wwLGZLfDXQtBbqnbgOFknDc2Ylpbv/Vbu+G66IdE Jvgrwf9Sw1Zg0/tO85jDhz9SW5dgxM3QIkuvteugjZ9JvTUFGN7bxmO5/YaEbXykX0ij lxZQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=hDExxvTKhJ/o1frLwdFq+stcMXreRFG+e9E30ZfmyjU=; b=rbXP6++qMtVMXHQ9Y70NgWyP6JchRhhUgGpez1nl02IpIvJnyAtwcc2ZLvjsSTKy5o sqMe9a9A/3Xk3HdJ5/szcD9kfwnLJiVJLqs9JF87fGs3vIrexQW7Sc/eAyKG/TZWQtY/ kZy1OPg6x8PjODExE8edp/DEo2Mf8MJqQ2cfC+ZROFMcH8EDxtOErVlhmPLHCwpn3P+W NehBobb79nF2pWwVRXtcsN04ruFkcOVeCjPFn7hovDylhgiCDj6Sq7uznmcVZDPCSPjl 5tMqZhAMKAJqbUsf2fF8XK7gXDMKhqgJiHMyBHDK7xnfcqs03uMwFyFt3WQJkeagQY5M gQpw== X-Gm-Message-State: ABuFfohqBr1ooPILRdVexgtXmLzPYDFJeUSyf2HmI6/pnYgZJ0ioYe40 vR/VjVxdaOCaYVAbf2K+LQEI1Wow8jbvv2UziA8= X-Google-Smtp-Source: ACcGV60WZxGNgtCXRV9Onhkpedvps22B2Mh2WPHrwrNJLPCmFgkEwp+bp26PBqJ5MzxGwHqTt4lUyGkL89ljwo2o600= X-Received: by 2002:a50:afa2:: with SMTP id h31-v6mr20071073edd.169.1540389233387; Wed, 24 Oct 2018 06:53:53 -0700 (PDT) MIME-Version: 1.0 References: <20181022113306.GB2867@w540> <20181023230259.GA3766@w540> In-Reply-To: <20181023230259.GA3766@w540> From: Adam Ford Date: Wed, 24 Oct 2018 08:53:41 -0500 Message-ID: Subject: Re: i.MX6 MIPI-CSI2 OV5640 Camera testing on Mainline Linux To: jacopo@jmondi.org Cc: steve_longerbeam@mentor.com, Fabio Estevam , Jagan Teki , p.zabel@pengutronix.de, Fabio Estevam , gstreamer-devel@lists.freedesktop.org, linux-media@vger.kernel.org, Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Oct 23, 2018 at 6:03 PM jacopo mondi wrote: > > Hi Adam, > > On Tue, Oct 23, 2018 at 12:54:12PM -0500, Adam Ford wrote: > > On Tue, Oct 23, 2018 at 12:39 PM Steve Longerbeam > > wrote: > > > > > > > > > On 10/23/18 10:34 AM, Adam Ford wrote: > > > > On Tue, Oct 23, 2018 at 11:36 AM Steve Longerbeam > > > > wrote: > > > >> Hi Adam, > > > >> > > > >> On 10/23/18 8:19 AM, Adam Ford wrote: > > > >>> On Mon, Oct 22, 2018 at 7:40 AM Fabio Estevam wrote: > > > >>>> Hi Adam, > > > >>>> > > > >>>> On Mon, Oct 22, 2018 at 9:37 AM Adam Ford wrote: > > > >>>> > > > >>>>> Thank you! This tutorial web site is exactly what I need. The > > > >>>>> documentation page in Linux touched on the media-ctl links, but it > > > >>>>> didn't explain the syntax or the mapping. This graphical > > > >>>>> interpretation really helps it make more sense. > > > >>>> Is capturing working well on your i.MX6 board now? > > > >>> Fabio, > > > >>> > > > >>> Unfortunately, no. I built the rootfs based on Jagan's instructions > > > >>> at https://openedev.amarulasolutions.com/display/ODWIKI/i.CoreM6+1.5 > > > >>> > > > >>> I tried building both the 4.15-RC6 kernel, a 4.19 kernel and a 4.14 LTS kernel. > > > >>> > > > >>> Using the suggested method of generating the graphical display of the > > > >>> pipeline options, I am able to enable various pipeline options > > > >>> connecting different /dev/videoX options tot he camera. I have tried > > > >>> both the suggested method above as well as the instructions found in > > > >>> Documentation/media/v4l-drivers/imx.rst for their respective kernels, > > > >>> and I have tried multiple options to capture through > > > >>> ipu1_csi1_capture, ipu2_csi1_capture, and ip1_ic_prepenc capture, and > > > >>> all yield a broken pipe. > > > >>> > > > >>> libv4l2: error turning on stream: Broken pipe > > > >>> ERROR: from element /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: Could > > > >>> not read from resource. > > > >>> Additional debug info: > > > >>> gstv4l2bufferpool.c(1064): gst_v4l2_buffer_pool_poll (): > > > >>> /GstPipeline:pipeline0/GstV4l2Src:v4l2src0: > > > >>> poll error 1: Broken pipe (32) > > > >>> > > > >>> I can hear the camera click when I start gstreamer and click again > > > >>> when it stops trying to stream. > > > >>> > > > >>> dmesg indicates a broken pipe as well.. > > > >>> > > > >>> [ 2419.851502] ipu2_csi1: pipeline start failed with -32 > > > >>> > > > >>> might you have any suggestions? > > > >> > > > >> This -EPIPE error might mean you have a mis-match of resolution, pixel > > > >> format, or field type between one of the source->sink pad links. You can > > > >> find out which pads have a mis-match by enabling dynamic debug in the > > > >> kernel function __media_pipeline_start. > > > > Following Jagan's suggestion, I tried to make sure all the resolution > > > > and pixel formats were set the same between each source and sink. > > > > > > > > media-ctl --set-v4l2 "'ov5640 2-0010':0[fmt:UYVY2X8/640x480 > > > > field:none]" > > > > media-ctl --set-v4l2 "'imx6-mipi-csi2':1[fmt:UYVY2X8/640x480 > > > > field:none]" > > > > media-ctl --set-v4l2 "'ipu1_csi0_mux':2[fmt:UYVY2X8/640x480 > > > > field:none]" > > > > media-ctl --set-v4l2 "'ipu1_csi0':2[fmt:AYUV32/640x480 field:none]" > > > > > > > >> Also make sure you are attempting to stream from the correct /dev/videoN. > > > > I have graphically plotted the pipeline using media-ctl --print-dot > > > > and I can see the proper video is routed, but your dynamic debug > > > > suggestion yielded something: > > > > > > > > imx-media capture-subsystem: link validation failed for 'ov5640 > > > > 2-0010':0 -> 'imx6-mipi-csi2':0, error -32 > > > > > > > > > It's what I expected, you have a format mismatch between those pads. > > > > Is the mismatch something I am doing wrong with: > > > > media-ctl --set-v4l2 "'ov5640 2-0010':0[fmt:UYVY2X8/640x480 field:none]" > > media-ctl --set-v4l2 "'imx6-mipi-csi2':2[fmt:UYVY2X8/640x480 field:none]" > > > > Could you try to verify the actual format configured on the sensor? > (media-ctl --get-v4l2 "'ov5640 2-0010':0"). > > Depending on the driver version you are running, you might be affected > by different regressions. > > > or is there something else I need to do? I just used Jagan's suggestion. > > I suggest you to update the driver version to the last one available > in the media-tree master, or at least try to backport the following > commit: > fb98e29 media: ov5640: fix mode change regression > > If it turns out the format and mode configured on the sensor do not > match the one you want. > > Thanks That got me past one hurdle. Wtih your help, I was able to confirm the mis-match of the modes between the sensor and the csi1 source. I applied the patch as you suggested, but now I get a new error. [ 295.294370] imx6-mipi-csi2: LP-11 timeout, phy_state = 0x00000230 [ 295.300681] ipu1_csi0: pipeline start failed with -110 I am going to go through various patches to the imx framework and ov5640 driver to see if I can find the solution, but if you have suggestions as to which fixes are appropriate, I'll test those. If I can get this working, would it make sense for me to submit some requests with kernel-stable to backport some of these commits to 4.19 and if applicable, 4.14 too? adam > j > > > adam > > > > > > Steve > > > > > > > > > > > > > > I am assume this means the interface between the camera and the csi2 > > > > isn't working. I am going to double check the power rails and the > > > > clocks. i can hear it click when activated and deactivated, so > > > > something is happening. > > > > > > > > adam > > > > > > > >> Steve > > > >>