From: Peter Geis <pgwipeout@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Matt Merhar <mattmerhar@protonmail.com>,
Dmitry Osipenko <digetx@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Bob Ham <rah@settrans.net>, Leonardo Bras <leobras.c@gmail.com>,
Michael Brougham <jusplainmike@gmail.com>
Cc: linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Peter Geis <pgwipeout@gmail.com>
Subject: [PATCH 0/3] Support NVIDIA Tegra-based Ouya game console
Date: Wed, 16 Sep 2020 12:22:44 +0000 [thread overview]
Message-ID: <20200916122247.534374-1-pgwipeout@gmail.com> (raw)
Good Day,
This series introduces upstream kernel support for the Ouya game console device. Please review and apply. Thank you in advance.
Peter Geis (3):
ARM: tegra: Add device-tree for Ouya
dt-bindings: Add vendor prefix for Ouya Inc.
dt-bindings: ARM: tegra: Add Ouya game console
.../devicetree/bindings/arm/tegra.yaml | 3 +
.../devicetree/bindings/vendor-prefixes.yaml | 2 +
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/tegra30-ouya.dts | 4498 +++++++++++++++++
4 files changed, 4505 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/tegra30-ouya.dts
--
2.25.1
next reply other threads:[~2020-09-16 18:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 12:22 Peter Geis [this message]
2020-09-16 12:22 ` [PATCH 1/3] ARM: tegra: Add device-tree for Ouya Peter Geis
2020-09-16 14:17 ` Dmitry Osipenko
2020-09-16 14:57 ` Peter Geis
2020-09-16 16:09 ` Dmitry Osipenko
2020-09-23 15:46 ` Rob Herring
2020-09-23 20:30 ` Peter Geis
2020-09-16 12:22 ` [PATCH 2/3] dt-bindings: Add vendor prefix for Ouya Inc Peter Geis
2020-09-23 15:46 ` Rob Herring
2020-09-16 12:22 ` [PATCH 3/3] dt-bindings: ARM: tegra: Add Ouya game console Peter Geis
2020-09-23 15:46 ` Rob Herring
2020-09-16 17:43 ` [PATCH 0/3] Support NVIDIA Tegra-based " Leonardo Bras
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=20200916122247.534374-1-pgwipeout@gmail.com \
--to=pgwipeout@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=jusplainmike@gmail.com \
--cc=leobras.c@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mattmerhar@protonmail.com \
--cc=rah@settrans.net \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.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;
as well as URLs for NNTP newsgroup(s).