linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
	Hans Verkuil <hverkuil@xs4all.nl>
Cc: <jonathanh@nvidia.com>, <frankc@nvidia.com>,
	<sakari.ailus@iki.fi>, <helen.koike@collabora.com>,
	<digetx@gmail.com>, <sboyd@kernel.org>,
	<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: Re: [RFC PATCH v8 0/9] Add Tegra driver for video capture
Date: Tue, 21 Apr 2020 21:12:47 -0700	[thread overview]
Message-ID: <cfbd9954-6a89-3973-55f5-920b7a807774@nvidia.com> (raw)
In-Reply-To: <20200421205032.GD3233341@ulmo>


On 4/21/20 1:50 PM, Thierry Reding wrote:
> On Tue, Apr 21, 2020 at 01:09:50PM +0200, Hans Verkuil wrote:
>> Hi Sowjanya,
>>
>> On 21/04/2020 02:11, Sowjanya Komatineni wrote:
>>> This series adds Tegra210 VI and CSI driver for built-in test pattern
>>> generator (TPG) capture.
>>>
>>> Tegra210 supports max 6 channels on VI and 6 ports on CSI where each
>>> CSI port is one-to-one mapped to VI channel for video capture.
>>>
>>> This series has TPG support only where it creates hard media links
>>> between CSI subdevice and VI video device without device graphs.
>>>
>>> v4l2-compliance results are available below the patch diff.
>> I'm ready to merge this v8. Looking at the series I should only merge
>> patches 6 and 7, all other patches go through different subsystems, right?
> You could also pick up patch 5 because it adds the bindings that are
> implemented by the driver in patch 6. But I can also pick that up into
> the Tegra tree. In fact, I do have a set of patches to convert some
> Tegra bindings to the new json-schema format and the host1x file is
> among them. If I do get around to finish those up for v5.8 it might be
> better for me to pick up patch 5 so that I can base my conversion patch
> on top of that.
>
> Either way is fine with me, so I've acked the three patches. Take which
> ones you want and I'll pick up the rest.
>
> Thanks again for your guidance on this patch set!
>
> Thierry

Hi Hans,

Would like to add a small fix to the driver for explicit check for vi 
and csi availability before TPG setup and cleanup in case if video 
driver is enabled without device tree support where vi and csi drivers 
does not register.

Although we are not enabling driver by default now, would be good to 
have this in this series itself.

Will send out the updated version, please pick v9.

Thanks

Sowjanya



  reply	other threads:[~2020-04-22  4:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21  0:11 [RFC PATCH v8 0/9] Add Tegra driver for video capture Sowjanya Komatineni
2020-04-21  0:11 ` [RFC PATCH v8 1/9] arm64: tegra: Fix sor powergate clocks and reset Sowjanya Komatineni
2020-04-21  0:11 ` [RFC PATCH v8 2/9] arm64: tegra: Add reset-cells to mc Sowjanya Komatineni
2020-04-21  0:11 ` [RFC PATCH v8 3/9] dt-bindings: clock: tegra: Add clk id for CSI TPG clock Sowjanya Komatineni
2020-04-21  0:11 ` [RFC PATCH v8 4/9] clk: tegra: Add Tegra210 CSI TPG clock gate Sowjanya Komatineni
2020-04-21  0:11 ` [RFC PATCH v8 5/9] dt-binding: tegra: Add VI and CSI bindings Sowjanya Komatineni
2020-04-21 20:46   ` Thierry Reding
2020-04-21  0:11 ` [RFC PATCH v8 6/9] media: tegra: Add Tegra210 Video input driver Sowjanya Komatineni
2020-04-21 20:47   ` Thierry Reding
2020-04-21  0:11 ` [RFC PATCH v8 7/9] MAINTAINERS: Add Tegra Video driver section Sowjanya Komatineni
2020-04-21 20:47   ` Thierry Reding
2020-04-21  0:11 ` [RFC PATCH v8 8/9] dt-bindings: reset: Add ID for Tegra210 VI reset Sowjanya Komatineni
2020-04-21  0:11 ` [RFC PATCH v8 9/9] arm64: tegra: Add Tegra VI CSI support in device tree Sowjanya Komatineni
2020-04-21 11:09 ` [RFC PATCH v8 0/9] Add Tegra driver for video capture Hans Verkuil
2020-04-21 20:50   ` Thierry Reding
2020-04-22  4:12     ` Sowjanya Komatineni [this message]
2020-04-22  6:23       ` Sowjanya Komatineni
2020-04-24 12:02     ` 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=cfbd9954-6a89-3973-55f5-920b7a807774@nvidia.com \
    --to=skomatineni@nvidia.com \
    --cc=devicetree@vger.kernel.org \
    --cc=digetx@gmail.com \
    --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=sakari.ailus@iki.fi \
    --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).