public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>,
	Hans Verkuil <hverkuil@xs4all.nl>, <thierry.reding@gmail.com>,
	<jonathanh@nvidia.com>, <frankc@nvidia.com>,
	<sakari.ailus@iki.fi>, <helen.koike@collabora.com>
Cc: <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: [RFC PATCH v10 6/9] media: tegra: Add Tegra210 Video input driver
Date: Sat, 25 Apr 2020 17:41:44 -0700	[thread overview]
Message-ID: <658c4232-94d9-3051-8c93-bff7046cf5f2@nvidia.com> (raw)
In-Reply-To: <50fd1016-ca8b-ec5d-e5a8-f257138b152e@gmail.com>


On 4/25/20 5:36 PM, Dmitry Osipenko wrote:
> External email: Use caution opening links or attachments
>
>
> 25.04.2020 12:36, Hans Verkuil пишет:
> ...
>>> The media/tegra/ sounds a bit too generic, the media/tegra-vi/ path
>>> should better reflect the driver, IMO.
>>>
>>> It also should be better to name the compiled kernel module as tegra-vi,
>>> IMO.
>>>
>> The driver name and the directory should be in sync, so either tegra-video
>> or tegra-vi for both. I have no preference myself, as long as they are the
>> same.
>>
>> This can be done as a follow-up patch.
> Given that this driver isn't going to be reused by older pre-Tegra210
> SoCs, perhaps it will also be worthwhile to name it as tegra210-vi or
> tegra210-video.

Can you explain what do you meant by can't be reused for pre-tegra210 or 
for tegra186/194?

support for other tegra's can be added to same tegra-video driver. 
tegra-video host1x driver can be updated to add other tegra's vi and csi 
compatibles to host1x subdevs and vi and csi driver can be updated to 
add other tegra soc data and need to add coresponding tegra186/194/xxx.c 
file with tegra specific prog sequence


  reply	other threads:[~2020-04-26  0:42 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24  3:55 [RFC PATCH v10 0/9] Add Tegra driver for video capture Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 1/9] arm64: tegra: Fix sor powergate clocks and reset Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 2/9] arm64: tegra: Add reset-cells to mc Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 3/9] dt-bindings: clock: tegra: Add clk id for CSI TPG clock Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 4/9] clk: tegra: Add Tegra210 CSI TPG clock gate Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 5/9] dt-binding: tegra: Add VI and CSI bindings Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 7/9] MAINTAINERS: Add Tegra Video driver section Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 8/9] dt-bindings: reset: Add ID for Tegra210 VI reset Sowjanya Komatineni
2020-04-24  3:55 ` [RFC PATCH v10 9/9] arm64: tegra: Add Tegra VI CSI support in device tree Sowjanya Komatineni
     [not found] ` <1587700513-28449-7-git-send-email-skomatineni@nvidia.com>
2020-04-24 15:07   ` [RFC PATCH v10 6/9] media: tegra: Add Tegra210 Video input driver Dmitry Osipenko
2020-04-24 22:00     ` Sowjanya Komatineni
2020-04-25 22:08       ` Dmitry Osipenko
2020-04-25 22:11         ` Sowjanya Komatineni
2020-04-25 23:40           ` Dmitry Osipenko
2020-04-25 23:44             ` Sowjanya Komatineni
2020-04-26  0:19               ` Dmitry Osipenko
2020-04-26  0:24                 ` Sowjanya Komatineni
2020-04-26  0:38                   ` Dmitry Osipenko
2020-04-26  8:07                 ` Hans Verkuil
2020-04-24 15:11   ` Dmitry Osipenko
2020-04-25  9:36     ` Hans Verkuil
2020-04-26  0:36       ` Dmitry Osipenko
2020-04-26  0:41         ` Sowjanya Komatineni [this message]
2020-04-26  1:08           ` Sowjanya Komatineni
2020-04-26  1:26             ` Dmitry Osipenko
2020-04-26  1:43               ` Sowjanya Komatineni
2020-04-26  2:10                 ` Dmitry Osipenko
2020-04-26  2:19                   ` Sowjanya Komatineni
2020-04-26  2:38                     ` Dmitry Osipenko
2020-04-26  2:48                       ` Sowjanya Komatineni
2020-04-26  3:03                         ` Sowjanya Komatineni
2020-04-26  2:19                   ` Dmitry Osipenko
2020-04-26  4:23                     ` Sowjanya Komatineni
2020-04-26  5:48                       ` Dmitry Osipenko
2020-04-26  4:42                   ` Dmitry Osipenko
2020-04-26  4:47                     ` Sowjanya Komatineni
2020-04-26  5:04                       ` Dmitry Osipenko
2020-04-26  5:51                       ` Dmitry Osipenko
2020-04-26  8:27                         ` Sowjanya Komatineni
2020-04-25 23:13   ` Dmitry Osipenko
2020-04-25 23:19     ` Sowjanya Komatineni
2020-04-25 23:25     ` Dmitry Osipenko
2020-04-25 23:27       ` Sowjanya Komatineni
2020-04-25 23:44         ` Dmitry Osipenko
2020-04-25 23:47           ` Sowjanya Komatineni
2020-04-25 23:29   ` Dmitry Osipenko
2020-04-26  1:04     ` Sowjanya Komatineni

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=658c4232-94d9-3051-8c93-bff7046cf5f2@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