From: Sowjanya Komatineni <skomatineni@nvidia.com>
To: Dmitry Osipenko <digetx@gmail.com>, <thierry.reding@gmail.com>,
<jonathanh@nvidia.com>, <frankc@nvidia.com>, <hverkuil@xs4all.nl>,
<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 v4 8/8] arm64: tegra: Add Tegra VI CSI support in device tree
Date: Sun, 15 Mar 2020 15:21:36 -0700 [thread overview]
Message-ID: <80805c85-a6b0-62c4-877c-6af3831bce1d@nvidia.com> (raw)
In-Reply-To: <b4bbcc1d-d38c-14c5-7205-2f7657ab8712@gmail.com>
On 3/15/20 5:54 AM, Dmitry Osipenko wrote:
> External email: Use caution opening links or attachments
>
>
> 15.03.2020 04:46, Sowjanya Komatineni пишет:
>> Tegra210 contains VI controller for video input capture from MIPI
>> CSI camera sensors and also supports built-in test pattern generator.
>>
>> CSI ports can be one-to-one mapped to VI channels for capturing from
>> an external sensor or from built-in test pattern generator.
>>
>> This patch adds support for VI and CSI and enables them in Tegra210
>> device tree.
>>
>> Signed-off-by: Sowjanya Komatineni <skomatineni@nvidia.com>
>> ---
> Hello Sowjanya,
>
> ...
>> +
>> + pd_venc: venc {
>> + clocks = <&tegra_car TEGRA210_CLK_VI>,
>> + <&tegra_car TEGRA210_CLK_CSI>;
>> + resets = <&tegra_car 20>,
> What is the clock #20?
Hi Dmitry,
20 is VI_RST not defined in include/dt-bindings/reset/tegra210-car.h
Will add define and will fix to use it.
>> + <&tegra_car TEGRA210_CLK_CSI>,
>> + <&mc TEGRA210_MC_RESET_VI>;
> Does this order means that memory controller will be reset *after*
> resetting the CSI/VI hardware? This is incorrect reset sequence.
>
> The memory controller reset should be kept asserted during of the time
> of the hardware resetting procedure.
>
> The correct sequence should be as follows:
>
> 1. Assert MC
> 2. Reset VI
> 3. Deassert MC
Right, will fix order. Thanks
prev parent reply other threads:[~2020-03-15 22:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1584236766-24819-1-git-send-email-skomatineni@nvidia.com>
2020-03-15 1:45 ` [RFC PATCH v4 1/8] arm64: tegra: Fix sor powergate clocks and reset Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 2/8] arm64: tegra: Add reset-cells to mc Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 3/8] dt-bindings: clock: tegra: Add clk id for CSI TPG clock Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 4/8] clk: tegra: Add Tegra210 CSI TPG clock gate Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 5/8] dt-binding: tegra: Add VI and CSI bindings Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 6/8] media: tegra: Add Tegra210 Video input driver Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 7/8] MAINTAINERS: Add Tegra Video driver section Sowjanya Komatineni
2020-03-15 1:46 ` [RFC PATCH v4 8/8] arm64: tegra: Add Tegra VI CSI support in device tree Sowjanya Komatineni
2020-03-15 12:54 ` Dmitry Osipenko
2020-03-15 22:21 ` Sowjanya Komatineni [this message]
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=80805c85-a6b0-62c4-877c-6af3831bce1d@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=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