From: digetx@gmail.com (Dmitry Osipenko)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/2] Enable Video Decoder on Tegra30
Date: Sun, 18 Feb 2018 20:01:44 +0300 [thread overview]
Message-ID: <cover.1518973069.git.digetx@gmail.com> (raw)
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.
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(+)
--
2.16.1
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Osipenko <digetx@gmail.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/2] Enable Video Decoder on Tegra30
Date: Sun, 18 Feb 2018 20:01:44 +0300 [thread overview]
Message-ID: <cover.1518973069.git.digetx@gmail.com> (raw)
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.
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(+)
--
2.16.1
next reply other threads:[~2018-02-18 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-18 17:01 Dmitry Osipenko [this message]
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 ` Dmitry Osipenko
2018-02-18 17:01 ` [PATCH v1 2/2] ARM: dts: tegra30: Add video decoder node Dmitry Osipenko
2018-02-18 17:01 ` Dmitry Osipenko
2018-02-18 18:03 ` Andreas Färber
2018-02-18 18:03 ` Andreas Färber
2018-02-18 18:03 ` Andreas Färber
2018-02-18 18:29 ` Dmitry Osipenko
2018-02-18 18:29 ` Dmitry Osipenko
2018-02-18 18:29 ` Dmitry Osipenko
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=cover.1518973069.git.digetx@gmail.com \
--to=digetx@gmail.com \
--cc=linux-arm-kernel@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.