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: <ace047fe-8a1a-666a-b91b-9d63b1d68567@nvidia.com>
Date:   Fri, 31 Jul 2020 09:29:00 -0700
From:   Sowjanya Komatineni <skomatineni@...dia.com>
To:     Dmitry Osipenko <digetx@...il.com>, <thierry.reding@...il.com>,
        <jonathanh@...dia.com>, <frankc@...dia.com>, <hverkuil@...all.nl>,
        <sakari.ailus@....fi>, <robh+dt@...nel.org>,
        <helen.koike@...labora.com>
CC:     <sboyd@...nel.org>, <gregkh@...uxfoundation.org>,
        <linux-media@...r.kernel.org>, <devicetree@...r.kernel.org>,
        <linux-tegra@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <linux-i2c@...r.kernel.org>
Subject: Re: [RFC PATCH v6 09/10] media: tegra-video: Add CSI MIPI pads
 calibration


On 7/31/20 9:14 AM, Dmitry Osipenko wrote:
> 31.07.2020 18:46, Sowjanya Komatineni пишет:
>> On 7/31/20 4:39 AM, Dmitry Osipenko wrote:
>>> 31.07.2020 12:02, Sowjanya Komatineni пишет:
>>> ...
>>>> @@ -249,13 +249,47 @@ static int tegra_csi_enable_stream(struct
>>>> v4l2_subdev *subdev)
>>>>            return ret;
>>>>        }
>>>>    +    if (csi_chan->mipi) {
>>>> +        ret = tegra_mipi_enable(csi_chan->mipi);
>>>> +        if (ret < 0) {
>>>> +            dev_err(csi->dev,
>>>> +                "failed to enable MIPI pads: %d\n", ret);
>>>> +            goto rpm_put;
>>>> +        }
>>>> +
>>>> +        /*
>>>> +         * CSI MIPI pads PULLUP, PULLDN and TERM impedances need to
>>>> +         * be calibrated after power on.
>>>> +         * So, trigger the calibration start here and results will
>>>> +         * be latched and applied to the pads when link is in LP11
>>>> +         * state during start of sensor streaming.
>>>> +         */
>>>> +        ret = tegra_mipi_start_calibration(csi_chan->mipi);
>>>> +        if (ret < 0) {
>>>> +            dev_err(csi->dev,
>>>> +                "failed to start MIPI calibration: %d\n", ret);
>>>> +            goto disable_mipi;
>>>> +        }
>>> What would happen if CSI stream is enabled and then immediately disabled
>>> without enabling camera sensor?
>> Nothing will happen as during stream enable csi receiver is kept ready.
>>
>> But actual capture will not happen during that point.
> Could you please show how the full call chain looks like? It's not clear
> to me what keeps CSI stream "ready".

VI is the main video input (video device) and on streaming it starts 
stream of CSI subdev prior to stream of Sensor.

HW path, sensor stream (CSI TX) -> CSI stream (RX)

During CSI stream on, CSI PHY receiver is enabled to start receiving the 
data but internally capture assembled to active state will happen only 
when Tegra VI single shot is issues where VI thru pixel parser gets 
captures data into the memory


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ