From: Thierry Reding <thierry.reding@gmail.com>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: "Jonathan Hunter" <jonathanh@nvidia.com>,
"Rob Herring" <robh+dt@kernel.org>,
"Andreas Färber" <afaerber@suse.de>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Enable Video Decoder on Tegra30
Date: Thu, 8 Mar 2018 15:00:10 +0100 [thread overview]
Message-ID: <20180308140010.GG3529@ulmo> (raw)
In-Reply-To: <cover.1518981147.git.digetx@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Sun, Feb 18, 2018 at 10:46:54PM +0300, Dmitry Osipenko wrote:
> VDE on Terga30 is compatible with VDE on Tegra20, hence the 'tegra-vde'
> driver works fine on Terga30. Let's add missing DT nodes to expose Video
> Decoder Engine on Terga30.
>
> Changelog:
>
> V2:
> 1) Appended unit address to the name of VDE pool node to fix
> DTC warning as per Andreas's Färber suggestion.
>
> 2) Correctly placed IRAM DT node in the address-ascending order.
>
> Dmitry Osipenko (2):
> ARM: dts: tegra30: Add IRAM node
> ARM: dts: tegra30: Add video decoder node
>
> arch/arm/boot/dts/tegra30.dtsi | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
Applied, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-03-08 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 19:46 [PATCH v2 0/2] Enable Video Decoder on Tegra30 Dmitry Osipenko
2018-02-18 19:46 ` [PATCH v2 1/2] ARM: dts: tegra30: Add IRAM node Dmitry Osipenko
2018-02-18 19:46 ` [PATCH v2 2/2] ARM: dts: tegra30: Add video decoder node Dmitry Osipenko
2018-03-08 14:00 ` Thierry Reding [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=20180308140010.GG3529@ulmo \
--to=thierry.reding@gmail.com \
--cc=afaerber@suse.de \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
/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).