linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: tegra: Enable GM20B GPU on Tegra210
Date: Fri, 29 Apr 2016 18:21:08 +0200	[thread overview]
Message-ID: <1461946869-26124-3-git-send-email-thierry.reding@gmail.com> (raw)

Hi ARM-SoC maintainers,

The following changes since commit f55532a0c0b8bb6148f4e07853b876ef73bc69ca:

  Linux 4.6-rc1 (2016-03-26 16:03:24 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.7-gm20b

for you to fetch changes up to 30f949bc6682d4912dbc74e7e757c66b3e3a6469:

  arm64: tegra: Add IOMMU node to GM20B on Tegra210 (2016-04-26 18:41:43 +0200)

Thanks,
Thierry

----------------------------------------------------------------
arm64: tegra: Enable GM20B GPU on Tegra210

Complement the GM20B GPU device tree node on Tegra210 with missing
properties to make it usable.

----------------------------------------------------------------
Alexandre Courbot (5):
      dt-bindings: gk20a: Fix typo in compatible name
      dt-bindings: gk20a: Document iommus property
      dt-bindings: Add documentation for GM20B GPU
      arm64: tegra: Add reference clock to GM20B on Tegra210
      arm64: tegra: Add IOMMU node to GM20B on Tegra210

 .../devicetree/bindings/gpu/nvidia,gk20a.txt       | 37 +++++++++++++++++++---
 arch/arm64/boot/dts/nvidia/tegra210.dtsi           |  8 +++--
 2 files changed, 38 insertions(+), 7 deletions(-)

             reply	other threads:[~2016-04-29 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-29 16:21 Thierry Reding [this message]
2016-05-10 20:18 ` [GIT PULL] arm64: tegra: Enable GM20B GPU on Tegra210 Arnd Bergmann

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=1461946869-26124-3-git-send-email-thierry.reding@gmail.com \
    --to=thierry.reding@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 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).