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 3/5] memory: tegra: Changes for v4.16-rc1
Date: Wed, 20 Dec 2017 20:18:58 +0100	[thread overview]
Message-ID: <20171220191900.757-3-thierry.reding@gmail.com> (raw)
In-Reply-To: <20171220191900.757-1-thierry.reding@gmail.com>

Hi ARM SoC maintainers,

The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323:

  Linux 4.15-rc1 (2017-11-26 16:01:47 -0800)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tegra/linux.git tags/tegra-for-4.16-memory

for you to fetch changes up to 83476bfaf6ac1cebf0cc5a3bdcf5031ef875cf42:

  iommu/tegra-smmu: Fix return value check in tegra_smmu_group_get() (2017-12-20 18:32:08 +0100)

Thanks,
Thierry

----------------------------------------------------------------
memory: tegra: Changes for v4.16-rc1

The Tegra memory controller driver will now instruct the SMMU driver to
create groups, which will make it easier for device drivers to share an
IOMMU domain between multiple devices.

Initial Tegra186 support is also added in a separate driver.

----------------------------------------------------------------
Thierry Reding (6):
      dt-bindings: misc: Add Tegra186 MISC registers bindings
      dt-bindings: memory: Add Tegra186 support
      Merge branch 'for-4.16/dt-bindings' into for-4.16/memory
      memory: tegra: Add Tegra186 support
      memory: tegra: Create SMMU display groups
      iommu/tegra: Allow devices to be grouped

Wei Yongjun (1):
      iommu/tegra-smmu: Fix return value check in tegra_smmu_group_get()

 .../memory-controllers/nvidia,tegra30-mc.txt       |   2 +
 .../bindings/misc/nvidia,tegra186-misc.txt         |  12 +
 drivers/iommu/tegra-smmu.c                         | 124 ++++-
 drivers/memory/tegra/Makefile                      |   1 +
 drivers/memory/tegra/tegra114.c                    |  15 +
 drivers/memory/tegra/tegra124.c                    |  17 +
 drivers/memory/tegra/tegra186.c                    | 600 +++++++++++++++++++++
 drivers/memory/tegra/tegra210.c                    |  15 +
 drivers/memory/tegra/tegra30.c                     |  15 +
 include/dt-bindings/memory/tegra186-mc.h           | 111 ++++
 include/soc/tegra/mc.h                             |   9 +
 11 files changed, 917 insertions(+), 4 deletions(-)
 create mode 100644 Documentation/devicetree/bindings/misc/nvidia,tegra186-misc.txt
 create mode 100644 drivers/memory/tegra/tegra186.c
 create mode 100644 include/dt-bindings/memory/tegra186-mc.h

  parent reply	other threads:[~2017-12-20 19:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 19:18 [GIT PULL 1/5] dt-bindings: Updates for v4.16-rc1 Thierry Reding
2017-12-20 19:18 ` [GIT PULL 2/5] soc/tegra: Changes " Thierry Reding
2017-12-20 20:00   ` Dmitry Osipenko
2017-12-21 16:12   ` [GIT PULL v2 " Thierry Reding
2017-12-21 17:04     ` Arnd Bergmann
2017-12-20 19:18 ` Thierry Reding [this message]
2017-12-21 17:07   ` [GIT PULL 3/5] memory: tegra: " Arnd Bergmann
2017-12-20 19:18 ` [GIT PULL 4/5] ARM: tegra: Device tree changes " Thierry Reding
2017-12-21 16:55   ` Arnd Bergmann
2017-12-20 19:19 ` [GIT PULL 5/5] arm64: tegra: Changes " Thierry Reding
2017-12-21 16:56   ` Arnd Bergmann
2017-12-21 16:54 ` [GIT PULL 1/5] dt-bindings: Updates " 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=20171220191900.757-3-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).