From: Dmitry Osipenko <digetx@gmail.com>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] ARM: dts: tegra30: Add video decoder node
Date: Sun, 18 Feb 2018 21:29:15 +0300 [thread overview]
Message-ID: <94cb9746-2421-aece-3767-dc42435d4bd3@gmail.com> (raw)
In-Reply-To: <4cf77dcd-0921-dec2-e5cd-ed8b5dc2fb7c@suse.de>
On 18.02.2018 21:03, Andreas Färber wrote:
> Am 18.02.2018 um 18:01 schrieb Dmitry Osipenko:
>> Add device tree node for the Video Decoder Engine found on Tegra30 SoC's.
>>
>> Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
>> ---
>> arch/arm/boot/dts/tegra30.dtsi | 27 +++++++++++++++++++++++++++
>> 1 file changed, 27 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/tegra30.dtsi b/arch/arm/boot/dts/tegra30.dtsi
>> index 1fb0c421a9d8..8ae72ffe0048 100644
>> --- a/arch/arm/boot/dts/tegra30.dtsi
>> +++ b/arch/arm/boot/dts/tegra30.dtsi
>> @@ -17,6 +17,11 @@
>> #address-cells = <1>;
>> #size-cells = <1>;
>> ranges = <0 0x40000000 0x40000>;
>> +
>> + vde_pool: vde {
>> + reg = <0x400 0x3fc00>;
>
> vde@400 then, to avoid dtc warnings.
Indeed by default kernels DTC silences such warnings, thank you for the suggestion.
prev parent reply other threads:[~2018-02-18 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 17:01 [PATCH v1 0/2] Enable Video Decoder on Tegra30 Dmitry Osipenko
2018-02-18 17:01 ` [PATCH v1 1/2] ARM: dts: tegra30: Add IRAM node Dmitry Osipenko
2018-02-18 17:01 ` [PATCH v1 2/2] ARM: dts: tegra30: Add video decoder node Dmitry Osipenko
2018-02-18 18:03 ` Andreas Färber
2018-02-18 18:29 ` Dmitry Osipenko [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=94cb9746-2421-aece-3767-dc42435d4bd3@gmail.com \
--to=digetx@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@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
Powered by JetHome