linux-kernel - Re: [PATCH v2 13/18] media: ti: Add CSI2RX support for J721E

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20210603124920.5o34klhlhjg5phlj@ti.com>
Date:   Thu, 3 Jun 2021 18:19:22 +0530
From:   Pratyush Yadav <p.yadav@...com>
To:     Tomi Valkeinen <tomi.valkeinen@...asonboard.com>
CC:     Maxime Ripard <mripard@...nel.org>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Rob Herring <robh+dt@...nel.org>,
        Kishon Vijay Abraham I <kishon@...com>,
        Vinod Koul <vkoul@...nel.org>,
        Peter Ujfalusi <peter.ujfalusi@...il.com>,
        Steve Longerbeam <slongerbeam@...il.com>,
        Benoit Parrot <bparrot@...com>, <linux-media@...r.kernel.org>,
        <devicetree@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-phy@...ts.infradead.org>, <dmaengine@...r.kernel.org>,
        Vignesh Raghavendra <vigneshr@...com>,
        Chunfeng Yun <chunfeng.yun@...iatek.com>,
        Laurent Pinchart <laurent.pinchart@...asonboard.com>
Subject: Re: [PATCH v2 13/18] media: ti: Add CSI2RX support for J721E

On 27/05/21 04:29PM, Tomi Valkeinen wrote:
> Hi Pratyush,
> 
> On 26/05/2021 18:23, Pratyush Yadav wrote:
> > TI's J721E uses the Cadence CSI2RX and DPHY peripherals to facilitate
> > capture over a CSI-2 bus.
> > 
> > The Cadence CSI2RX IP acts as a bridge between the TI specific parts and
> > the CSI-2 protocol parts. TI then has a wrapper on top of this bridge
> > called the SHIM layer. It takes in data from stream 0, repacks it, and
> > sends it to memory over PSI-L DMA.
> > 
> > This driver acts as the "front end" to V4L2 client applications. It
> > implements the required ioctls and buffer operations, passes the
> > necessary calls on to the bridge, programs the SHIM layer, and performs
> > DMA via the dmaengine API to finally return the data to a buffer
> > supplied by the application.
> > 
> > Signed-off-by: Pratyush Yadav <p.yadav@...com>
> 
> I noticed that my test app didn't work at all with this, and I also wasn't
> able to use v4l2-ctl to set the format.

I have not used v4l2-ctl, but I can see yavta works fine. What command 
did you use for setting format via v4l2-ctl?

> 
> At least for my test app the problem was that this driver doesn't initialize
> the format at all. My app first calls VIDIOC_G_FMT with v4l2_format.type ==
> V4L2_BUF_TYPE_VIDEO_CAPTURE, then after the call modifies the fields it
> wants to change and calls VIDIOC_S_FMT. This failed, as G_FMT returned
> uninitialized fmt, i.e. type was 0, which my app didn't set again.
> 
> I believe the driver should have an initial format, something that it will
> accept if an app calls G_FMT and then S_FMT.

Right. This is a bug. The question is what should the initial format be? 
It is more or less arbitrary since there is no configuration made yet 
and we don't know what the camera can or will send. So for example, what 
if I use UYVY 640x480? The camera might not support it at all. Is it 
still OK to have it as the default?

-- 
Regards,
Pratyush Yadav
Texas Instruments Inc.