linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Hans Verkuil <hverkuil@xs4all.nl>, <thierry.reding@gmail.com>,
	<jonathanh@nvidia.com>, <frankc@nvidia.com>,
	<helen.koike@collabora.com>, <sboyd@kernel.org>
Cc: <linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<linux-clk@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v3 4/6] media: tegra: Add Tegra210 Video input driver
Date: Tue, 25 Feb 2020 21:50:18 -0800	[thread overview]
Message-ID: <33d21639-6a61-3870-a160-53482614bd66@nvidia.com> (raw)
In-Reply-To: <821f0878-56da-9b51-425a-9d6fb65d2e0c@nvidia.com>


On 2/25/20 8:49 PM, Sowjanya Komatineni wrote:
>
> On 2/20/20 4:44 AM, Hans Verkuil wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> Hi Sowjanya,
>>
>> Some code review comments below:
>>
>> On 2/14/20 7:23 PM, Sowjanya Komatineni wrote:
>>> Tegra210 contains a powerful Video Input (VI) hardware controller
>>> which can support up to 6 MIPI CSI camera sensors.
>>>
>>> Each Tegra CSI port can be one-to-one mapped to VI channel and can
>>> capture from an external camera sensor connected to CSI or from
>>> built-in test pattern generator.
>>>
>>> Tegra210 supports built-in test pattern generator from CSI to VI.
>>>
>>> This patch adds a V4L2 media controller and capture driver support
>>> for Tegra210 built-in CSI to VI test pattern generator.
>>>
>>> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
>>> ---
>>>   drivers/staging/media/Kconfig              |    2 +
>>>   drivers/staging/media/Makefile             |    1 +
>>>   drivers/staging/media/tegra/Kconfig        |   10 +
>>>   drivers/staging/media/tegra/Makefile       |    8 +
>>>   drivers/staging/media/tegra/TODO           |   10 +
>>>   drivers/staging/media/tegra/tegra-common.h |  239 +++++++
>>>   drivers/staging/media/tegra/tegra-csi.c    |  374 ++++++++++
>>>   drivers/staging/media/tegra/tegra-csi.h    |  115 ++++
>>>   drivers/staging/media/tegra/tegra-vi.c     | 1019 
>>> ++++++++++++++++++++++++++++
>>>   drivers/staging/media/tegra/tegra-vi.h     |   79 +++
>>>   drivers/staging/media/tegra/tegra-video.c  |  118 ++++
>>>   drivers/staging/media/tegra/tegra-video.h  |   32 +
>>>   drivers/staging/media/tegra/tegra210.c     |  767 
>>> +++++++++++++++++++++
>>>   drivers/staging/media/tegra/tegra210.h     |  190 ++++++
>>>   14 files changed, 2964 insertions(+)
>>>   create mode 100644 drivers/staging/media/tegra/Kconfig
>>>   create mode 100644 drivers/staging/media/tegra/Makefile
>>>   create mode 100644 drivers/staging/media/tegra/TODO
>>>   create mode 100644 drivers/staging/media/tegra/tegra-common.h
>>>   create mode 100644 drivers/staging/media/tegra/tegra-csi.c
>>>   create mode 100644 drivers/staging/media/tegra/tegra-csi.h
>>>   create mode 100644 drivers/staging/media/tegra/tegra-vi.c
>>>   create mode 100644 drivers/staging/media/tegra/tegra-vi.h
>>>   create mode 100644 drivers/staging/media/tegra/tegra-video.c
>>>   create mode 100644 drivers/staging/media/tegra/tegra-video.h
>>>   create mode 100644 drivers/staging/media/tegra/tegra210.c
>>>   create mode 100644 drivers/staging/media/tegra/tegra210.h
>>>
>
>>> +static int chan_capture_kthread_done(void *data)
>>> +{
>>> +     struct tegra_vi_channel *chan = data;
>>> +     struct tegra_channel_buffer *buf;
>>> +
>>> +     set_freezable();
>>> +
>>> +     while (1) {
>>> +             try_to_freeze();
>>> +
>>> +             wait_event_interruptible(chan->done_wait,
>>> + !list_empty(&chan->done) ||
>>> +                                      kthread_should_stop());
>>> +
>>> +             if (kthread_should_stop())
>>> +                     break;
>> I think it makes more sense if this test is moved to the end...
>>
>>> +
>>> +             buf = dequeue_buf_done(chan);
>>> +             if (!buf)
>>> +                     continue;
>> ... and this becomes:
>>
>>                  if (buf)
>>> + tegra_channel_capture_done(chan, buf);
>> This change simplifies stop_streaming (see below).
>
> With kthread_should_stop check at end, I see sometimes outstanding 
> buffer in done queue by the time threads are stopped during stream stop.
>
> When I run compliance stream io tests continuously in loop, depending 
> on time of stream stop request capture thread terminated after 
> initiating frame capture and moving buffer to done queue while done 
> thread was still in wait for previous MW_ACK and on seeing 
> kthread_should_stop done thread terminated with last buffer left in 
> done queue.
>
> So looks like we need to keep checking for outstanding buffer and 
> handle it during stop streaming like in v3.
>
Will change in v4 to handle all pending done queue buffers before 
terminating thread.
>
>>> +     }
>>> +
>>> +     return 0;
>>> +}
>>> +
>>> +int tegra210_vi_start_streaming(struct vb2_queue *vq, u32 count)
>>> +{
>>> +     struct tegra_vi_channel *chan = vb2_get_drv_priv(vq);
>>> +     struct media_pipeline *pipe = &chan->video.pipe;
>>> +     int ret = 0;
>>> +
>>> +     tegra_vi_write(chan, TEGRA_VI_CFG_CG_CTRL, VI_CG_2ND_LEVEL_EN);
>>> +
>>> +     /* clear errors */
>>> +     vi_csi_write(chan, TEGRA_VI_CSI_ERROR_STATUS, 0xFFFFFFFF);
>>> +
>>> +     /*
>>> +      * Sync point FIFO full stalls the host interface.
>>> +      * Setting NO_STALL will drop INCR_SYNCPT methods when fifos are
>>> +      * full and the corresponding condition bits in INCR_SYNCPT_ERROR
>>> +      * register will be set.
>>> +      * This allows SW to process error recovery.
>>> +      */
>>> +     tegra_vi_write(chan, TEGRA_VI_CFG_VI_INCR_SYNCPT_CNTRL,
>>> +                    TEGRA_VI_CFG_VI_INCR_SYNCPT_NO_STALL);
>>> +
>>> +     /* start the pipeline */
>>> +     ret = media_pipeline_start(&chan->video.entity, pipe);
>>> +     if (ret < 0)
>>> +             goto error_pipeline_start;
>>> +
>>> +     /* program VI registers after TPG, sensors and CSI streaming */
>>> +     ret = tegra_channel_set_stream(chan, true);
>>> +     if (ret < 0)
>>> +             goto error_set_stream;
>>> +
>>> +     tegra_channel_capture_setup(chan);
>>> +
>>> +     chan->sequence = 0;
>>> +
>>> +     /* start kthreads to capture data to buffer and return them */
>>> +     chan->kthread_capture_done = 
>>> kthread_run(chan_capture_kthread_done,
>>> +                                              chan, "%s:1",
>>> + chan->video.name);
>>> +     if (IS_ERR(chan->kthread_capture_done)) {
>>> +             ret = PTR_ERR(chan->kthread_capture_done);
>>> +             chan->kthread_capture_done = NULL;
>>> +             dev_err(&chan->video.dev,
>>> +                     "failed capture done kthread: %d\n", ret);
>>> +             goto error_kthread_done;
>>> +     }
>>> +
>>> +     chan->kthread_capture_start = 
>>> kthread_run(chan_capture_kthread_start,
>>> +                                               chan, "%s:0",
>>> + chan->video.name);
>>> +     if (IS_ERR(chan->kthread_capture_start)) {
>>> +             ret = PTR_ERR(chan->kthread_capture_start);
>>> +             chan->kthread_capture_start = NULL;
>>> +             dev_err(&chan->video.dev,
>>> +                     "failed capture start kthread: %d\n", ret);
>>> +             goto error_kthread_start;
>>> +     }
>>> +
>>> +     return 0;
>>> +
>>> +error_kthread_start:
>>> +     kthread_stop(chan->kthread_capture_done);
>>> +error_kthread_done:
>>> +     tegra_channel_set_stream(chan, false);
>>> +error_set_stream:
>>> +     media_pipeline_stop(&chan->video.entity);
>>> +error_pipeline_start:
>>> +     vq->start_streaming_called = 0;
>>> +     tegra_channel_release_queued_buffers(chan, VB2_BUF_STATE_QUEUED);
>>> +     return ret;
>>> +}
>>> +
>>> +void tegra210_vi_stop_streaming(struct vb2_queue *vq)
>>> +{
>>> +     struct tegra_vi_channel *chan = vb2_get_drv_priv(vq);
>>> +     struct tegra_channel_buffer *buf;
>>> +
>>> +     if (!chan->kthread_capture_start || !chan->kthread_capture_done)
>>> +             return;
>>> +
>>> +     kthread_stop(chan->kthread_capture_start);
>>> +     chan->kthread_capture_start = NULL;
>>> +     kthread_stop(chan->kthread_capture_done);
>>> +     chan->kthread_capture_done = NULL;
>>> +
>> With the change in chan_capture_kthread_done() as described above you 
>> can
>> drop the next 4 lines since that's guaranteed to be done by the thread.
>>
>>> +     /* wait for last frame MW_ACK_DONE */
>>> +     buf = dequeue_buf_done(chan);
>>> +     if (buf)
>>> +             tegra_channel_capture_done(chan, buf);
>>> +
>>> +     tegra_channel_release_queued_buffers(chan, VB2_BUF_STATE_ERROR);
>>> +
>>> +     tegra_channel_set_stream(chan, false);
>>> +
>>> +     /* disable clock gating to enable continuous clock */
>>> +     tegra_vi_write(chan, TEGRA_VI_CFG_CG_CTRL, 0);
>>> +
>>> +     /* reset VI MCIF, PF, SENSORCTL, and SHADOW logic */
>>> +     vi_csi_write(chan, TEGRA_VI_CSI_SW_RESET, 0xF);
>>> +     vi_csi_write(chan, TEGRA_VI_CSI_SW_RESET, 0x0);
>>> +     vi_csi_write(chan, TEGRA_VI_CSI_IMAGE_DEF, 0);
>>> +
>>> +     /* enable clock gating so VI can be clock gated if necessary */
>>> +     tegra_vi_write(chan, TEGRA_VI_CFG_CG_CTRL, VI_CG_2ND_LEVEL_EN);
>>> +     vi_csi_write(chan, TEGRA_VI_CSI_ERROR_STATUS, 0xFFFFFFFF);
>>> +
>>> +     media_pipeline_stop(&chan->video.entity);
>>> +}
>>> +
>>> +void tegra210_csi_error_recover(struct tegra_csi_channel *csi_chan)
>>
>> Regards,
>>
>>          Hans

  reply	other threads:[~2020-02-26  5:50 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 18:23 [RFC PATCH v3 0/6] Add Tegra driver for video capture Sowjanya Komatineni
2020-02-14 18:23 ` [RFC PATCH v3 1/6] dt-bindings: clock: tegra: Add clk id for CSI TPG clock Sowjanya Komatineni
2020-02-14 18:23 ` [RFC PATCH v3 2/6] clk: tegra: Add Tegra210 CSI TPG clock gate Sowjanya Komatineni
2020-02-14 18:23 ` [RFC PATCH v3 3/6] dt-binding: tegra: Add VI and CSI bindings Sowjanya Komatineni
2020-02-18 23:15   ` Rob Herring
2020-02-19  3:28     ` Sowjanya Komatineni
2020-02-20 19:45       ` Rob Herring
2020-02-20 20:39         ` Sowjanya Komatineni
2020-02-14 18:23 ` [RFC PATCH v3 4/6] media: tegra: Add Tegra210 Video input driver Sowjanya Komatineni
2020-02-16 11:03   ` Hans Verkuil
2020-02-16 19:54     ` Sowjanya Komatineni
2020-02-16 20:11       ` Sowjanya Komatineni
2020-02-16 20:22         ` Sowjanya Komatineni
2020-02-17  8:04           ` Hans Verkuil
2020-02-18  0:59             ` Sowjanya Komatineni
2020-02-18  1:04               ` Sowjanya Komatineni
2020-02-18  3:19                 ` Sowjanya Komatineni
2020-02-19 15:08                   ` Hans Verkuil
2020-02-19 16:22                     ` Sowjanya Komatineni
2020-02-20  0:09                       ` Sowjanya Komatineni
2020-02-20  9:29                         ` Hans Verkuil
2020-02-20 16:21                           ` Sowjanya Komatineni
2020-02-20 12:44   ` Hans Verkuil
2020-02-20 13:33     ` Hans Verkuil
2020-02-20 17:29       ` Sowjanya Komatineni
2020-02-20 19:11       ` Sowjanya Komatineni
2020-02-24  4:45         ` Sowjanya Komatineni
2020-03-18 11:48           ` Hans Verkuil
2020-03-18 16:14             ` Sowjanya Komatineni
2020-03-18 16:25               ` Sowjanya Komatineni
2020-03-18 17:17                 ` Sowjanya Komatineni
2020-03-19 14:29                   ` Hans Verkuil
2020-03-19 18:49                     ` Sowjanya Komatineni
2020-02-26  4:49     ` Sowjanya Komatineni
2020-02-26  5:50       ` Sowjanya Komatineni [this message]
2020-02-14 18:23 ` [RFC PATCH v3 5/6] MAINTAINERS: Add Tegra Video driver section Sowjanya Komatineni
2020-02-14 18:23 ` [RFC PATCH v3 6/6] arm64: tegra: Add Tegra VI CSI support in device tree Sowjanya Komatineni
2020-02-17 14:26 ` [RFC PATCH v3 0/6] Add Tegra driver for video capture Hans Verkuil

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=33d21639-6a61-3870-a160-53482614bd66@nvidia.com \
    --to=skomatineni@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=frankc@nvidia.com \
    --cc=helen.koike@collabora.com \
    --cc=hverkuil@xs4all.nl \
    --cc=jonathanh@nvidia.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=thierry.reding@gmail.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).