From: Dmitry Osipenko <digetx@gmail.com>
To: Sowjanya Komatineni <skomatineni@nvidia.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: Sun, 26 Apr 2020 05:38:35 +0300 [thread overview]
Message-ID: <a7407ed7-f35e-b3e9-ad26-3e83f0ed462b@gmail.com> (raw)
In-Reply-To: <3a9707b5-b260-6137-f475-fc88d271010f@nvidia.com>
26.04.2020 05:19, Sowjanya Komatineni пишет:
>
> On 4/25/20 7:10 PM, Dmitry Osipenko wrote:
>> External email: Use caution opening links or attachments
>>
>>
>> 26.04.2020 04:43, Sowjanya Komatineni пишет:
>> ...
>>>> It looks to me that at least all those hardcoded HW format IDs do not
>>>> match the older SoCs.
>>> TPG hard coded formats are supported on prior Tegra.
>>>
>>> Other supported formats are SoC dependent and part of soc data in the
>>> driver already.
>> But I don't see where that SoC-dependent definition is made in
>> terga210.c. That tegra_image_format enum looks T210-specific, isn't it?
>>
>> ...
>
> Video formats which are SoC variants are made soc specific in driver
> already tegra_vi_soc structure member video_formats
>
> tegra_image_format enum is same for T210 and T186
>
> For T194, enums will be diff and will have diff TEGRA194_VIDEO_FORMAT
> using corresponding Tegra194 video format enums
But it is also not the same for older SoCs, correct? All the
T210-specific things should be separated better, unique parts shouldn't
be kept in the common code.
Hence the tegra_image_format should be renamed to tegra210_image_format
and moved out to t210.h, since it's not common. But then you'll probably
need to rename all TEGRA_ defines to TEGRA210_ to make t210.h reusable
by T186.
Also, in the end it may not worth the effort to share anything at all,
it could be cleaner to have a bit of duplication. Although, I have no
idea how T186 code will look like and what other parts of T210 could be
reused by T186. All this needs to be taken into account in order to
avoid struggling with the code's reshuffling in the future.
next prev parent reply other threads:[~2020-04-26 2:38 UTC|newest]
Thread overview: 48+ 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 6/9] media: tegra: Add Tegra210 Video input driver Sowjanya Komatineni
2020-04-24 15:07 ` 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
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 [this message]
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
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
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=a7407ed7-f35e-b3e9-ad26-3e83f0ed462b@gmail.com \
--to=digetx@gmail.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=sakari.ailus@iki.fi \
--cc=sboyd@kernel.org \
--cc=skomatineni@nvidia.com \
--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).