From: Alexandre Courbot <acourbot@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>,
Stephen Warren <swarren@wwwdotorg.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
gnurou@gmail.com, Alexandre Courbot <acourbot@nvidia.com>
Subject: [PATCH 0/4] ARM: tegra: enable Nouveau for Jetson TK1 and Venice 2
Date: Wed, 1 Jul 2015 18:13:44 +0900 [thread overview]
Message-ID: <1435742028-8237-1-git-send-email-acourbot@nvidia.com> (raw)
With all essential kernel driver and user-space patches merged, GK20A can now
be enabled safely on Tegra124 devices. This series makes small device tree
and configuration adjustments to allow this.
It leaves the GK20A nodes ready to be used, but still disabled. Enabling the
nodes is the work of the bootloader, after it has configured VPR properly.
U-boot patches that do this are in the work. In the meantime, it is safe to
merge this kernel support.
Alexandre Courbot (3):
ARM: tegra: Add IOMMU node to GK20A
ARM: tegra: jetson-tk1: Add GK20A GPU DT node
ARM: tegra: Enable Nouveau in defconfig
Thierry Reding (1):
ARM: tegra: venice2: Add GK20A GPU DT node
arch/arm/boot/dts/tegra124-jetson-tk1.dts | 10 +++++++++-
arch/arm/boot/dts/tegra124-venice2.dts | 10 +++++++++-
arch/arm/boot/dts/tegra124.dtsi | 3 +++
arch/arm/configs/tegra_defconfig | 3 +++
4 files changed, 24 insertions(+), 2 deletions(-)
--
2.4.4
next reply other threads:[~2015-07-01 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 9:13 Alexandre Courbot [this message]
2015-07-01 9:13 ` [PATCH 1/4] ARM: tegra: Add IOMMU node to GK20A Alexandre Courbot
2015-07-01 9:13 ` [PATCH 2/4] ARM: tegra: venice2: Add GK20A GPU DT node Alexandre Courbot
2015-07-01 9:13 ` [PATCH 3/4] ARM: tegra: jetson-tk1: " Alexandre Courbot
2015-07-01 9:13 ` [PATCH 4/4] ARM: tegra: Enable Nouveau in defconfig Alexandre Courbot
2015-07-17 8:03 ` [PATCH 0/4] ARM: tegra: enable Nouveau for Jetson TK1 and Venice 2 Thierry Reding
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=1435742028-8237-1-git-send-email-acourbot@nvidia.com \
--to=acourbot@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.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